Back to basics: Geolocation data (Part 2/3)
Barney Bruce-Smythe, Senior Associate (London)
![Post feature](/rails/active_storage/representations/proxy/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBb3hLIiwiZXhwIjpudWxsLCJwdXIiOiJibG9iX2lkIn19--622363b85fa8fad4a86469ed78e604bf9ce87ebb/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaDdCem9MWm05eWJXRjBTU0lJY0c1bkJqb0dSVlE2QzNKbGMybDZaVWtpRFRFeU9EQjRPRFV6QmpzR1ZBPT0iLCJleHAiOm51bGwsInB1ciI6InZhcmlhdGlvbiJ9fQ==--4a0ea5eeb6f0e6d47bff3b653fd69e214040023f/photo-1533027052290-2b4ece075c42.jpg)
In the second part of our geolocation data primer, we provide an overview of the technologies and challenges associated with contextualizing raw location data.
Part 1: Location data types
Part 2: POIs and geofencing
Part 3: Regulatory trends
Friendly PSA: the following information is intended as a general primer on location intelligence. If you are already a sophisticated user of this data (or are even just passably familiar with it) then there is a chance that you will not learn anything new here.
In the first part of this series, we introduced the ways in which location information (ideally coordinate-based) is generated and subsequently made available to third parties. However, raw coordinates only start to become useful once we are able to locate them in a real-world setting.
In this article, we are going to use Starbucks as a basic example. The retailer is