# Amazon Location Service concepts With Amazon Location Service, you can securely add location data to your application. Explore some of the capabilities by using the [visual and interactive tool](https://console.aws.amazon.com/location/explore/home), available on the Amazon Location console. Using the explore tool, you can manipulate a default map, search for points of interest, draw geofences around areas of interest, and simulate sending device locations to a tracker. ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/Amazon-Location-Service_product-page-diagram@2x.png) When you are ready to build, create your resources and choose from a variety of map styles and data providers. Then you can install the SDK that matches your development environment, and use the Amazon Location APIs using the instructions in this guide. Additionally, you can integrate monitoring by using Amazon CloudWatch and AWS CloudTrail. The topics in this section provide you an overview of the Amazon Location core concepts and prepare you to start working with location in your own applications. **Topics** + [Overview](overview.md) + [Learn about Maps resources](map-concepts.md) + [Learn about Places search](places-concepts.md) + [Learn about routing](route-concepts.md) + [Learn about geofences and trackers](geofence-tracker-concepts.md) + [Common use cases](common-usecases.md) + [Data providers](what-is-data-provider.md) # Amazon Location overview Amazon Location Service provides access to location-based functionality and data providers through AWS resources. Amazon Location offers five types of AWS resources, depending on the type of functionality you need. Use the different resources together to create a full location-based application. You can create one or more of these resources by using the Amazon Location console, the Amazon Location APIs, or the SDKs. ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/how-it-works.PNG) Each resource defines the underlying [data provider](what-is-data-provider.md) to be used (where applicable), and gives access to functionality related to its type. For example: + [Amazon Location Service Maps](map-concepts.md) lets you choose a map from a map provider to use on your mobile or web application. + [Amazon Location Service Places](places-concepts.md) lets you choose a data provider for searching for points of interest, completing partial text, geocoding, and reverse geocoding. + [Amazon Location Service Routes](route-concepts.md) lets you choose a data provider and find routes and estimate travel time based on up-to-date roadway and live traffic information. + [Amazon Location Service Geofences](geofence-tracker-concepts.md) let you define areas of interest as a virtual boundary. You can then evaluate locations against them and get notifications of entry and exit events. + [Amazon Location Service Trackers](geofence-tracker-concepts.md) receive location updates from your devices. You can link trackers to geofence collections so that all position updates are automatically evaluated against your geofences. You can use IAM policies to manage and authorize access to your Amazon Location resources. You can also organize your resources into resource groups to manage and automate tasks as your resource numbers grow. For more information about managing AWS resources, see [What are AWS Resource Groups?](https://docs.aws.amazon.com/ARG/latest/userguide/welcome.html) In the *AWS Resource Groups User Guide*. Location is defined by using latitude and longitude coordinates that follow the [World Geodetic System (WGS 84)](https://earth-info.nga.mil/index.php?dir=wgs84&action=wgs84), commonly used as the standard coordinate reference system for Global Positioning System (GPS) services. The following sections describe how the components of Amazon Location work. # Learn about Maps resources in Amazon Location Service **Note** We released a new version of the Maps API, see the updated [Maps Developer Guide](https://docs.aws.amazon.com//location/latest/developerguide/maps.html) for revised information. The Amazon Location Service *Map* resource gives you access to the underlying basemap data for a map. You use the Map resource with a map rendering library to add an interactive map to your application. You can add other functionality to your map, such as markers (or pins), routes, and polygon areas, as needed for your application. **Note** For information about how to use map resources in practice, see [Using Amazon Location Maps in your application](using-maps.md). The following is an overview of how to create and use map resources: ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/illustration-maps.PNG) 1. You create a map resource in your AWS account by selecting a map style from a data provider. 1. You can then select and install the SDK that matches your development environment and applications. For more information about available options, see the topic about [Accessing Amazon Location](how-to-access.md). 1. To display a map in your application, combine a map resource with a rendering library, such as Amplify, MapLibre, or Tangram. For more information. see [Using maps](using-maps.md) in this guide. 1. You can then integrate monitoring by using services, such as Amazon CloudWatch and AWS CloudTrail with Amazon Location. For more information see, [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). ## Map styles When you create a map resource, you must choose a map style for that resource. Map styles define the look of the rendered map. For example, the following image shows the same data provider with two different styles from different map resources in Amazon Location. One style is a typical road style, based on the vector data in the map. The other includes raster data showing satellite imagery. The style may change as you zoom in or out on the map, but typically styles have a consistent theme. It's possible to override parts or all of the style information before passing it to the map rendering library. ![\[An image showing the same area of the world, drawn with two different styles: a road style and a satellite imagery style.\]](http://docs.aws.amazon.com/location/previous/developerguide/images/map-styles-concepts.png) ## Political views Certain maps styles in Amazon Location Service support additional political views. **Note** The political view must be used in compliance with applicable laws, including those laws about mapping of the country or region where the maps, images, and other data and third-party content which you access through Amazon Location Service is made available. The following map styles support an India (IND) political view. + [Esri map styles](esri.md#esri-map-styles): + Esri Navigation + Esri Light + Esri Street Map + Esri Dark Gray Canvas + Esri Light Gray Canvas + [Open Data map styles](open-data.md#open-data-map-styles): + Open Data Standard Light + Open Data Standard Dark + Open Data Visualization Light + Open Data Visualization Dark In the Amazon Location Service console, you can filter the styles shown to just show the styles that support the India political view. ## Custom Layers A custom layer is an additional layer you can enable for a map style. Currently only the VectorEsriNavigation map style supports the `POI` custom layer. When you enable the `POI` custom layer it adds a richer set of places, such as shops, services, restaurants, attractions, and other points of interest to your map. By default, the custom layer is `unset`. For more information see, [MapConfiguration](https://docs.aws.amazon.com//location/previous/APIReference/API_MapConfiguration.html) in the Location API reference. ## Map rendering To render a map in your application, you will typically use a map rendering library. There are several common options for libraries to use: + **MapLibre** – MapLibre is an open source library specifically for rendering interactive maps, and is the preferred method of rendering maps from Amazon Location Service. MapLibre includes the ability to render raster and vector data from a data source (such as an Amazon Location map resource). You can extend MapLibre to draw your own data on the map. + **Amplify** – Amplify is an open source framework for building applications for the web, iOS, Android, and more. If your application uses Amplify, then you can extend it to include Amazon Location functionality. Amplify includes libraries specifically for creating Amazon Location based applications, including rendering maps. Amplify uses MapLibre to render the map, but provides additional functionality that is specific to Amazon Location Service to make it more efficient to use, and also adding search and other functionality. + **Tangram** – Tangram is an alternative open source library that renders interactive maps, similar to MapLibre. The map rendering library pulls data from Amazon Location Service at runtime, rendering the map data based on the map resource you select. The map resource defines the data provider and map style that will be used. The following image shows how the map resource is used in Amazon Location Service along with a map rendering library to create the final map. ![\[An image showing a user creating a map resource in Amazon Location Service and an app using that resource to get map data and render a map.\]](http://docs.aws.amazon.com/location/previous/developerguide/images/RenderMapInApp.png) 1. You create a map resource in Amazon Location Service, using the AWS Management Console or AWS CLI. This defines the data provider and the map style that you want to use. 1. Your application includes a map rendering library. You give the map rendering library the name of the map resource to use. The map rendering library pulls data and style information for that map resource from Amazon Location and renders the map on screen. ## Maps terminology **Map resource** Allows you to access map data from a selected provider. Use the map resource to fetch map tiles that contain map data and a style descriptor to specify how features render on a map. **Basemap** Provides geographic context to your map, which is stored as vector tile layers. Tile layers include geographical context such as street names, buildings, and land use for visual reference. **Vector** Vector data is shape data made up of points, lines, and polygons. It is often used to store and display roads, locations, and areas on a map. A vector shape can also be used as icons for markers on a map. **Raster** Raster data is image data, made up of a grid, usually of colors. It is often used to store and display a representation of continuous data on maps, such as terrain, satellite imagery, or heat maps. Raster images can also be used as images or icons. **Map Style** Vector data does not inherently include information about how to draw the layers of data to create the final map. A map style defines color and other style information for the data to define how it will look when rendered. Map resources include style information for the map. Amazon Location Service provides styles following the [Mapbox GL style specification](https://docs.mapbox.com/mapbox-gl-js/style-spec/). **Vector tile ** A tile format that stores map data using vector shapes. This data results in a map that can adjust to the display resolution, and selectively render features in a number of ways, while maintaining a small file size for optimal performance. Supported vector file format: Mapbox Vector Tiles (MVT). **Glyph file** A binary file containing encoded Unicode characters. Used by a map renderer to display labels. **Sprite file** A Portable Network Graphic (PNG) image file that contains small raster images, with location descriptions in a JSON file. Used by a map renderer to render icons or textures on a map. # Learn about Places search in Amazon Location Service **Note** We released a new version of the Places API, see the updated [Places Developer Guide](https://docs.aws.amazon.com//location/latest/developerguide/places.html) for revised information. A key function of Amazon Location Service is the ability to search the geolocation information. Amazon Location provides this functionality via the *Place index* resource. **Note** For information about how to use place index resources to search in practice, see [Searching place and geolocation data using Amazon Location](searching-for-places.md). You can use the place index APIs to search for: + Points of interest, such as restaurants and landmarks. Search by name, and optional location to search around, and receive a list of options ordered by relevance. + A street address, receiving a latitude and longitude for that address. This is known as *geocoding*. + A latitude and longitude position, receiving the associated street address or other information about the location. This is known as *reverse geocoding*. + A partial or misspelled free-form text query, typically as a user types. This is known as *autocomplete*, autosuggest, or fuzzy matching. The place index includes which data provider to use for the search. **Note** Map data and other geolocation information, including exact locations, can vary across data providers. As a best practice, use the same data provider for your place index, map, and other Amazon Location resources. For example, if the places returned by your place index do not match the location of the same places provided by your map resource, you can place a marker in what appears to be the wrong location on the map. The following shows you how to create and use place index resources: ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/illustration-places.PNG) 1. First, you create a place index resource in your AWS account by selecting a data provider. 1. You can then select and install the SDK that matches your development environment and applications. For more information about available options, see the topic about [Accessing Amazon Location](https://docs.aws.amazon.com/location/previous/developerguide/how-to-access.html). 1. Start using the Amazon Location Places APIs . For more information, see the topic about using [Places search](searching-for-places.md). 1. You can then integrate monitoring using services such as Amazon CloudWatch and AWS CloudTrail. For more information see, [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). ## Geocoding concepts An Amazon Location place index provides an action called [https://docs.aws.amazon.com/location-places/latest/APIReference/API_SearchPlaceIndexForText.html](https://docs.aws.amazon.com/location-places/latest/APIReference/API_SearchPlaceIndexForText.html) that allows you to specify text to search. For example, you can search for: + **Places** – a search for **Paris** could return the location of the city in France. + **Businesses** – a search for **coffee shop** could return a list of coffee shops, including their names and locations. You can also specify a location to search around or a bounding box to search within, to make the results more relevant. In this case, providing a location in downtown Seattle, Washington, would return coffee shops in that area. + **Addresses** – a search for **1600 Pennsylvania Ave, Washington D.C.** could return the location of the White House in the United States (which is at that address). Searching for text in this way is generally referred to as **geocoding**, which involves finding a geographic location for the address or place. Amazon Location Service also provides a **reverse geocoding** action called [https://docs.aws.amazon.com/location-places/latest/APIReference/API_SearchPlaceIndexForPosition.html](https://docs.aws.amazon.com/location-places/latest/APIReference/API_SearchPlaceIndexForPosition.html). This takes a geographic location and returns the address, business, or other information about what is at that location. ## Search results When you make a successful search request in Amazon Location Service, one or more results are returned. Each result includes a label, which is the name or description of the result. For example, a search for **coffee shop**, might return a result with the label `Hometown Cafe`, telling you that a coffee shop called "Hometown Cafe" was found. The search result will also typically include a structured address (with properties such as the address number, unit, street, and postal code). Depending on the data provider, it will include other meta data, as well, such as the country and time zone. For a search on a business name or category (such as **coffee shop**), you might want to show all returned results on a map. For an address search, you might want to just use the first result automatically. See the next topic for information about relevance. ## Multiple results and relevance When searching by text, Amazon Location Service will often find more than a single result. For example, a search for **Paris** may return the city in France, but also the city in Texas. The results are sorted by the relevance, as determined by the data provider. **Note** Results are returned in relevance order from all providers. If you choose Esri or Grab as your data provider, the results include a relevance value that you can use to understand the relative relevance between the results of a single request. Specifying additional information, such as a country name, or a location to search around, can change the order of results, reduce the number of results, or even change the set of results returned. For example, a search for **Paris** with a location in Texas to search around is more likely to return `Paris, Texas` as the first result than `Paris, France`. In an interactive application, you can use relevance to help decide whether to accept the top result, or to ask a user to disambiguate between multiple returned results. If the first result has a high relevance, you might just accept it as the correct answer. If there are multiple high relevance results, or no high relevance results, you might want to list the results and let the user select the best result. ## Address results You can search for addresses with Amazon Location Service using the same [https://docs.aws.amazon.com/location-places/latest/APIReference/API_SearchPlaceIndexForText.html](https://docs.aws.amazon.com/location-places/latest/APIReference/API_SearchPlaceIndexForText.html) action. The more information that you provide, the more likely the address returned will match the one given. For example, **123 Main St** is less likely to find a correct result than **123 Main St, Anytown, California, 90210**. Addresses have multiple attributes, such as the street number, street, city, region, and postal code, etc. Those attributes are used to find an address in the place index that matches as many aspects as possible. The more attributes found, the more relevant the match is considered, and the more likely it will be returned. **Note** The relevance for address results is based on how closely the result matches the input. This could be the number of the attributes that matched, but also how closely the results match the input. For example, an input of **123 Main St** would have a higher relevance when `Main St` is found in the data, than if `Maine St` is the only result. `Maine St` will still be returned, but likely with a lower relevance value. The search results include a label for the full address (`123 Main St, Anytown, California, 90210`), but also the individual structured attributes of the returned address. This is helpful, because you can use that, for example, to populate address fields in a database, or to examine the results and find the city, region, or postal code of the found location. **Interpolation** Addresses in the place index data includes exact address matches. For example, suppose that there is a street, `9th street` and one block has 2 houses, `220` and `240`, as in the following image. ![\[A map of a single block with two existing houses, and one new house added between them.\]](http://docs.aws.amazon.com/location/previous/developerguide/images/address-inference.png) The data provider creates the geolocation data with those two known addresses. You can search for those two addresses, and they are found. After the data provider creates the map data, let's suppose that a new house is added, between the first two addresses. This new house is given the address `230`. If you search for **230 S 9th St**, the data provider will still find a result. Instead of using a known address, it will interpolate between the already known addresses, and estimate the position of the new address from those. In this case, it might assume that 230 is halfway between 220 and 240 (and on the same side of the street), and return an approximate location based on that. **Note** Data providers periodically update their geolocation data with new addresses. In this case, `230 S 9th St` would get added to the data provider data, but there will typically be a period when a new address has been created but is not yet added to the data. In this case, the data provider can't tell whether the new address exists in the world, as it is not yet in the data, but provides the best answer it can from the information it has. This result is called *interpolated*, and can be returned by the data provider in the results. If `interpolated` returns `false`, it is a known address. If it returns `true`, it's an approximated address. If it's not returned, then the data provider did not provide the information about whether the result came from interpolation. **Important** The data provider may also return interpolated results for addresses that don't exist at all. For example in this case, if you entered **232 S 9th St**, the provider would find this nonexistent address, and return a location close to 230, but on the 240 side. Interpolated addresses are useful for getting you to the right location, but it is good to keep in mind that they are not known addresses. ## Storing geocode results When you create a place index resource, you must specify a **Data storage option** (called `IntendedUse` in the API). That can set to be either *single use* or *stored results*. This is asking about your intended use of the results. If you are going to store the results (even for caching purposes), you must choose the *storage* option, not the *single use* option. **Note** When you chose the stored option (labeled as **Yes, results will be stored** in the console, or choosing `storage` in the `CreatePlaceIndex` API), Amazon Location Service does not store the results for you. This is an indication that you are planning to store the results. When looking at how you are going to use the results of your queries to Amazon Location Service, you should always be aware of the [AWS Service Terms](https://aws.amazon.com/service-terms/) that apply. ## Places terminology **Place index resource** Allows you to choose a data source to support search queries. For example, you can search for points of interest, addresses, or coordinates. When a search query is sent to a place index resource, it's fulfilled using the resource's configured data source. **Geocoding** Geocoding is the process of taking a text input, searching for it in the place index, and returning results with position. **Reverse geocoding** Reverse geocoding is the process of taking a position and returning information about that position from within the place index, such as the address, city, or business at that location. **Relevance** Relevance is how closely a result matches the input. It is not a measure of correctness. **Interpolation** Interpolation is the process of finding unknown addresses by using known address locations as guide points. **ISO 3166 country codes ** Amazon Location Service Places uses [the International Organization for Standardization (ISO) 3166 ](https://www.iso.org/iso-3166-country-codes.html) country codes to refer to countries or regions. To find the code for a specific country or region, use the[ ISO Online Browsing Platform](https://www.iso.org/obp/ui/#search). # Learn about routing in Amazon Location Service **Note** We released a new version of the Routes API, see the updated [Routes Developer Guide](https://docs.aws.amazon.com//location/latest/developerguide/routes.html) for revised information. This section provides an overview of the concepts around routing using Amazon Location Service. **Note** For information about how to use route resources in practice, see [Calculating routes using Amazon Location Service](calculating-routes.md). ## Route calculator resources Route calculator resources allow you to find routes and estimate travel time based on up-to-date road network and live traffic information from your chosen data provider. You can use the Routes APIs to build features that allow your application to request the travel time, distance, and geometry of the route between any two locations. You can also use the Routes API to request travel time and distance between a set of departures and destinations in a single request to calculate a matrix. The following shows you how to create and use a route calculator resource: ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/illustration-route.PNG) 1. First, you create a route calculator resource in your AWS account by selecting a data provider. 1. You can then select and install the SDK that matches your development environment and applications. 1. Start using the Amazon Location Routes APIs . For more information about how to use the routing APIs, see the topic on [Calculating routes using Amazon Location Service](calculating-routes.md). 1. You can then integrate monitoring using services such as Amazon CloudWatch and AWS CloudTrail. For more information see, [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). ## Calculating a route An Amazon Location route calculator resource provides an action called `CalculateRoute` that you can use to create a route between two geographic locations (the *departure* and the *destination*). The calculated route includes the geometry for drawing the route on a map, plus the overall time and distance of the route. **Using waypoints** When you are creating your route request, you can add additional waypoints to the route. These are points between the departure and the destination that act as stops along the route. The route will be calculated through each of the waypoints specified. The route from one point in the request to the next is called a `Leg`. Each leg includes a distance, time, and the geometry for that part of the route. **Note** The waypoints are routed in the order given in the request. They are not re-ordered for the shortest path. See the [Planning routes](#route-concepts-plan-routes)section for information on finding the shortest path. You can include up to 25 waypoints in a single request to calculate a route. **Traffic and departure time** The Amazon Location Service takes traffic into account when calculating a route. The trafffic that it considers is based on the time that you specify. You can specify to depart now, or you can provide a specific time that you want to leave, which will affect the route result by adjusting for traffic at the specified time. **Note** You can calculate the arrival time using the departure time and route response time, to estimate the arrival of a driver, for example. If you want Amazon Location to not take traffic into account, then do not specify a departure time and do not specify depart now. This will calculate a route that assumes the best traffic conditions for the route. **Travel mode options** You can set the travel mode when calculating a route using Amazon Location Service. The default travel mode is *car*, but you can alternately select either *truck* or *walking*. If you specify either car or truck mode, you can specific additional options, as well. For **car mode**, you can specify that you wish to avoid toll roads or ferries. This will attempt to avoid ferries and toll roads, but will still route along them, if they are the only way to get to the destination. For **truck mode**, you can also avoid ferries and toll roads, but additionally, you can specify the size and weight of the truck, to avoid routes that will not accommodate the truck. ## Planning routes You can use Amazon Location Service to create inputs to your route planning and optimization software. You can create route results, including travel time and travel distance, for routes between a set of departure positions and a set of destination positions. This is called creating a route *matrix*. **Note** There are many varying scenarios that route planning and optimization software can solve. For example, planning software can use the set of times and distances between points to calculate the shortest path that stops at each point, providing an efficient route for a single driver. Alternatively, planning software can be used to split stops between multiple trucks, providing efficiencies across a fleet, or to make sure that each customer is visited within the time frame that they require. Amazon Location provides the routing functions in an efficient way to allow the planning software to complete it's task. For example, given departure positions A and B, and destination positions X and Y, Amazon Location Service will return travel time and travel distance for routes from A to X, A to Y, B to X, and B to Y. As with calculating a single route, you can calculate the routes with different modes of transportation, avoidances, and traffic conditions. For example, you can specify that the vehicle is a truck that is 35 feet long, and the route calculated will use those restrictions to determine the travel time and travel distance. You can't include waypoints in a route matrix calculation. The number of results returned (and routes calculated) is the number of departure positions multiplied by the number of destination positions. You are charged for each route calculated, not each request to the service, so a route matrix with 10 departures and 10 destinations will be billed as 100 routes. ## Route terminology **Route calculator resource** An AWS resource that enables you to estimate travel time, distance, and plot routes on a map with traffic and road network data sourced from your chosen data provider. Using route calculator resources, you calculate routes for different modes of transportation, detours, and traffic conditions. **Route** A route contains details used when traveling along a path from the departure position, waypoint positions, and destination position. Examples of details in a route include: + The distance from one position to another position. + The time it takes to travel from one position to the next position. + The LineString geometry representing the path of the route. For more information about routes, see the [response syntax for the CalculateRoute operation](https://docs.aws.amazon.com/location-routes/latest/APIReference/API_CalculateRoute.html) in the *Amazon Location Service Routes API reference*. **Route matrix** A list of routes, from a set of departure positions to a set of destination positions. Useful as inputs into route planning or optimization software. For more information about calculating a route matrix, see the [syntax for the CalculateRouteMatrix operation](https://docs.aws.amazon.com/location-routes/latest/APIReference/API_CalculateRouteMatrix.html) in the *Amazon Location Service Routes API reference*. **`LineString` geometry** An Amazon Location route consists of one or more legs (a route from one waypoint to another within the overall route). The geometry of each leg is a polyline represented as a `LineString`. A `LineString` is an ordered array of positions that can be used to plot a route on a map. The following is an example of a `LineString` with three points: ``` [ [-122.7565,49.0021], [-122.3394,47.6159], [-122.1082,45.8371] ] ``` **Waypoint** Waypoints are intermediate positions that act as stops along a route between the departure position and destination position. The stopover order on the route follows the order that you provide the waypoint positions in the request. **Leg** A single leg is the journey from one position to another position. If the positions aren't located on a road, they're moved to the nearest road. The number of legs in a route is one less than the total number of positions. A route with no waypoints consists of a single leg, from the departure position to the destination. A route with 1 waypoint consists of 2 legs, from the departure position to the waypoint, and then from the waypoint to the destination. **Step** A step is a subsection of a leg. Each step provides summary information for that step in the leg. # Learn about geofences and trackers in Amazon Location Service This section provides and overview of the concepts of working with Amazon Location Service geofences and trackers. Geofences are polygon boundaries that you can use to be notified when devices or positions move in and out of the areas. Tracker resources are used to store and update positions for devices as they move. **Note** For information about how to use geofences and trackers in practice, see [Geofencing an area of interest using Amazon Location](geofence-an-area.md). **Topics** + [Learn about geofences in Amazon Location Service](geofence-overview.md) + [Learn about trackers in Amazon Location Service](tracking-overview.md) # Learn about geofences in Amazon Location Service Geofence collection resources allow you to store and manage geofences—virtual boundaries on a map. You can evaluate locations against a geofence collection resource and get notifications when the location update crosses the boundary of any of the geofences in the geofence collection. The following shows you how to create and use geofence collection resources: ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/illustration-geofence.PNG) 1. Create a geofence collection resource in your AWS account. 1. Add geofences to that collection. You can do so by either using the geofence upload tool on the Amazon Location console, or by using the Amazon Location Geofences API. For more information about available options, see [Accessing Amazon Location](https://docs.aws.amazon.com/location/previous/developerguide/how-to-access.html). Geofences can either be defined by a polygon or by a circle. Use a polygon to find when a device enters a specific area. Use a circle to find when a device comes within a certain distance (radius) of a point. 1. You can start evaluating locations against all your geofences. When a location update crosses the boundaries of one or more geofences, your geofence collection resource emits one of the following geofence event types on Amazon EventBridge: + ****ENTER**** – One event is generated for each geofence where the location update crosses its boundary by entering it. + ****EXIT**** – One event is generated for each geofence where the location update crosses its boundary by exiting it. For more information, see [Reacting to Amazon Location Service events with Amazon EventBridge](location-events.md). You can also integrate monitoring using services such as Amazon CloudWatch and AWS CloudTrail. For more information see, [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). For example, if you are tracking a fleet of trucks, and you want to get notified when a truck comes within a certain area of any of your warehouses. You can create a geofence for the area around each warehouse. Then, when the trucks send you updated locations, you can use Amazon Location Service to evaluate those positions and see if a truck has entered (or exited) one of the geofence areas. **Note** Your are billed by the number of geofence collections you evaluate against. Your bill is not affected by the number of geofences in each collection. Since each geofence collection may contain up to 50,000 geofences, you may want to combine your geofences into fewer collections, where possible, to reduce your cost of geofence evaluations. The events generated will include the ID of the individual geofence in the collection, as well as the ID of the collection. ## Geofence events Locations for positions you are monitoring are referenced by an ID called a `DeviceId` (and the positions are referred to as device positions). You can send a list of device positions to evaluate directly to the geofence collection resource, or you can use a tracker. See the next section for more information on trackers. You receive events (via Amazon EventBridge) only when a device enters or exits a geofence, not for every position change. This means that you will typically receive events and have to respond to them much less frequently than every device position update. **Note** For the first location evaluation for a specific `DeviceID`, it is assumed that the device was previously not in any geofences. So the first update will generate an `ENTER` event, if inside a geofence in the collection, and no event if not. In order to calculate whether a device has entered or exited a geofence, Amazon Location Service must keep previous position state for the device. This position state is stored for 30 days. After 30 days without an update for a device, a new location update will be treated as the first position update. ## Geofence terminology **Geofence Collection** Contains zero or more geofences. It is capable of geofence monitoring by emitting Entry and Exit events, when requested, to evaluate a device position against its geofences. **Geofence** A polygon or circle geometry that defines a virtual boundary on a map. **Polygon geometry** An Amazon Location geofence is a virtual boundary for a geographical area and is represented as a polygon geometry or as a circle. A circle is a point with a distance around it. Use a circle when you want to be notified if a device is within a certain distance of a location. A polygon is an array composed of 1 or more linear rings. Use a polygon when you want to define a specific boundary for device notifications. A linear ring is an array of four or more vertices, where the first and last vertex are the same to form a closed boundary. Each vertex is a 2-dimensional point of the form *[longitude, latitude]*, where the units of longitude and latitude are degrees. The vertices must be listed in counter-clockwise order around the polygon. Amazon Location Service doesn't support polygons with more than one ring. This includes holes, islands or multipolygons. Amazon Location also doesn't support polygons that are wound clockwise, or that cross the antimeridian. The following is an example of a single linear external ring: ``` [ [ [-5.716667, -15.933333], [-14.416667, -7.933333], [-12.316667, -37.066667], [-5.716667, -15.933333] ] ] ``` # Learn about trackers in Amazon Location Service A tracker stores position updates for a collection of devices. The tracker can be used to query the devices' current location or location history. It stores the updates, but reduces storage space and visual noise by filtering the locations before storing them. Each position update stored in your tracker resources can include a measure of position accuracy and up to 3 fields of metadata about the position or device that you want to store. The metadata is stored as key-value pairs, and can store information such as speed, direction, tire pressure, or engine temperature. **Note** Tracker storage is encrypted with AWS owned keys automatically. You can add another layer of encryption using KMS keys that you manage, to ensure that only you can access your data. For more information, see [Data encryption at rest for Amazon Location Service](encryption-at-rest.md). Tracker position filtering and storage are useful on their own, but trackers are especially useful when paired with geofences. You can link trackers to one or more of your geofence collection resources, and position updates are evaluated automatically against the geofences in those collections. Proper use of filtering can greatly reduce the costs of your geofence evaluations, as well. The following diagram shows you how to create and use tracker resources: ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/illustration-trackers.PNG) 1. First, you create a tracker resource in your AWS account. 1. Next, decide how you send location updates to your tracker resources. Use [AWS SDKs](location-actions.md) to integrate tracking capabilities into your mobile applications. Alternately, you can use MQTT by following step-by-step directions in [tracking using MQTT](tracking-using-mqtt.md). 1. You can now use your tracker resource to record location history and visualize it on a map. 1. You can also link your tracker resource to one or more geofence collections so that every position update sent to your tracker resource is automatically evaluated against all the geofence in all the linked geofence collections. You can link resource on the tracker resource details page of the Amazon Location console or by using the Amazon Location Trackers API. 1. You can then integrate monitoring using services such as Amazon CloudWatch and AWS CloudTrail. For more information see, [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). ## Using trackers with geofences Trackers provide additional functionality when paired with geofences. You associate a tracker with a geofence collection, either through the Amazon Location console or the API, to automatically evaluate tracker locations. Each time the tracker receives an updated location, that location will be evaluated against each geofence in the collection, and the appropriate `ENTER` and `EXIT` events are generated in Amazon EventBridge. You can also apply filtering to the tracker, and, depending on the filtering, you can reduce the costs for geofence evaluations by only evaluating meaningful location updates. If you associate the tracker with a geofence collection after it has already received some position updates, the first position update after association is treated as an initial update for the geofence evaluations. If it is within a geofence, you will receive an `ENTER` event. If it is not within any geofences you will not receive an `EXIT` event, regardless of the previous state. ## Position filtering Trackers can automatically filter the positions that are sent to them. There are several reasons why you might want to filter out some of your device location updates. If you have a system that only sends reports every minute or so, you might want to filter devices by time, storing and evaluating positions only every 30 seconds. Even if you are monitoring more frequently, you might want to filter position updates to clean up the noisiness of GPS hardware. GPS position locations are inherently noisy. Their accuracy is not 100% perfect, so even a device that is stationary appears to be moving around slightly. At low speeds, this *jitter* causes visual clutter and can cause false entry and exit events if the device is near the edge of a geofence. The position filtering works as position updates are received by a tracker, reducing visual noise in your device paths (jitter), reducing the number of false geofence entry and exit events, and helping manage costs by reducing the number of position updates stored and geofence evaluations triggered. Trackers offer three position filtering options to help manage costs and reduce jitter in your location updates. + **Accuracy-based** – *Use with any device that provides an accuracy measurement. Most GPS and mobile devices provide this information.* The accuracy of each position measurement is affected by many environmental factors, including GPS satellite reception, landscape, and the proximity of wifi and bluetooth devices. Most devices, including most mobile devices, can provide an estimate of the accuracy of the measurement along with the measurement. With `AccuracyBased` filtering, Amazon Location ignores location updates if the device moved less than the measured accuracy. For example, if two consecutive updates from a device have an accuracy range of 5 m and 10 m, Amazon Location ignores the second update if the device has moved less than 15 m. Amazon Location neither evaluates ignored updates against geofences, nor stores them. When accuracy is not provided, it is treated as zero, and the measurement is considered perfectly accurate, and no filtering will be applied to the updates. **Note** You can use accuracy-based filtering to remove all filtering. If you select accuracy-based filtering, but override all accuracy data to zero, or omit the accuracy entirely, then Amazon Location will not filter out any updates. In most scenarios, accuracy-based filtering is a good choice for filtering position updates, providing a balance of tracking location while filtering out unneeded updates, thereby reducing costs. + **Distance-based** – *Use when your devices do not provide an accuracy measurement, but you still want to take advantage of filtering to reduce jitter and manage costs.* `DistanceBased` filtering ignores location updates in which devices have moved less than 30 m (98.4 ft). When you use `DistanceBased` position filtering, Amazon Location neither evaluates these ignored updates against geofences nor stores the updates. The accuracy of most mobile devices, including the average accuracy of iOS and Android devices, is within 15 m. In most applications, `DistanceBased` filtering can reduce the effect of location inaccuracies when displaying device trajectory on a map, and the bouncing effect of multiple consecutive entry and exit events when devices are near the border of a geofence. It can also help reduce the cost of your application, by making fewer calls to evaluate against linked geofences or retrieve device positions. Distance-based filtering is useful if you want to filter, but your device doesn't provide accuracy measurements, or you want to filter out a larger number of updates than with accuracy-based. + **Time-based** – (default) *Use when your devices send position updates very frequently (more than once every 30 seconds), and you want to achieve near real-time geofence evaluations without storing every update. *In `TimeBased` filtering, every location update is evaluated against linked geofence collections, but not every location update is stored. If your update frequency is more often than 30 seconds, only one update per 30 seconds is stored for each unique device ID. Time-based filtering is particularly useful when you want to store fewer positions, but want every position update to be evaluated against the associated geofence collections. **Note** Be mindful of the costs of your tracking application when deciding your filtering method and the frequency of position updates. You are billed for every location update and once for evaluating the position update against each linked geofence collection. For example, when using time-based filtering, if your tracker is linked to two geofence collections, every position update will count as one location update request and two geofence collection evaluations. If you are reporting position updates every 5 seconds for your devices and using time-based filtering, you will be billed for 720 location updates and 1,440 geofence evaluations per hour for each device. ## Tracker terminology **Tracker resource** An AWS resource that receives location updates from devices. The tracker resource provides support for location queries, such as current and historic device location. Linking a tracker resource to a geofence collection evaluates location updates against all geofences in the linked geofence collection automatically. **Position data tracked** A tracker resource stores information about your devices over time. The information includes a series of position updates, where each update includes location, time, and optional metadata. The metadata can include a position's accuracy, and up to three key-value pairs to help you track key information about each position, such as speed, direction, tire pressure, remaining fuel, or engine temperature of the vehicle you are tracking. Trackers maintain device location history for 30 days. **Position filtering** Position filtering can help you control costs and improve the quality of your tracking application by filtering out position updates that don't provide valuable information before the updates are stored or evaluated against geofences. You can choose `AccuracyBased`, `DistanceBased`, or `TimeBased` filtering. By default, position filtering is set to `TimeBased`. You can configure position filtering when you create or update tracker resources. **RFC 3339 timestamp format ** Amazon Location Service Trackers uses the [RFC 3339](https://tools.ietf.org/html/rfc3339) format, which follows the [International Organization for Standardization (ISO) 8601](https://www.iso.org/iso-8601-date-and-time-format.html) format for dates and time. The format is “YYYY-MM-DDThh:mm:ss.sssZ\$100:00”: + `YYYY-MM-DD` — Represents the date format. + `T` — Indicates that the time values will follow. + `hh:mm:ss.sss` — Represents the time in 24-hour format. + `Z` — Indicates that the time zone used is UTC, which can be followed with deviations from the UTC time zone. + `+00:00` — Optionally indicate deviations from the UTC time zone. For example, \$101:00 indicates UTC \$1 1 hour. **Example** For July 2, 2020, at 12:15:20 in the afternoon, with an adjustment of an additional 1 hour to the UTC time zone. ``` 2020-07-02T12:15:20.000Z+01:00 ``` # Common use cases for using Amazon Location Service Amazon Location Service lets you build a range of applications, from asset tracking to location-based marketing. The following are common use cases: **User engagement and geomarketing ** Use location data to build solutions that improve user engagement with marketing to target customers. For example, Amazon Location can trigger an event that prompts a notification when a customer who ordered a coffee on their mobile app is nearby. Additionally, you can build geotargeting features so that retailers can send discount codes or digital flyers to customers who are near target stores. **Asset tracking ** Build asset tracking features to help businesses understand the current and historical locations of their products, personnel, and infrastructure. With asset tracking features, you can build a number of solutions that optimize remote staffing, secure shipment en-route, and maximize dispatch efficacy. **Delivery ** Integrate location features into delivery applications to store, track, and coordinate the departure location, delivery vehicles, and their destination. For example, a food delivery application with Amazon Location features built-in has location tracking and geofencing capabilities that can automatically notify a restaurant when a delivery driver is nearby. This reduces the wait time and helps maintain the quality of the food delivered. This topic provides you an overview of the architecture and steps for applications you can build with Amazon Location. **Topics** + [User engagement and geomarketing applications](user-engagement-geomarketing.md) + [Asset tracking applications](asset-tracking.md) + [Delivery applications](delivery.md) # User engagement and geomarketing applications The following is an illustration of a user engagement and geomarketing application architecture using Amazon Location: With this architecture, you can: + Initiate events based on the proximity of a target so that you can send offers to nearby customers or engage those who recently left your establishment (called *geotargeting*). + Visualize customer device locations on a map to monitor trends over time. + Store customer device locations that you can analyze over time. + Analyze location history to identify trends and opportunities for optimization. ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/geomarketing.PNG) The following is an overview of the steps required to build a user engagement and geomarketing application: 1. Create your geofences in Geofence Collections and link Trackers to them. For more information, see [Geofencing an area of interest using Amazon Location](geofence-an-area.md). 1. Configure Amazon EventBridge to send a notification to customers who enter or exit a geofenced area of interest. For more information, see [Reacting to Amazon Location Service events with Amazon EventBridge](location-events.md). 1. Display customer locations and geofences on a map. For more information, see [Using maps](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html). 1. Save location data to long-term storage for further analysis. 1. Once you have built your application, you can use Amazon CloudWatch and AWS CloudTrail to manage your application. For more information, see [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). # Asset tracking applications The following is an illustration of an asset tracking application architecture using Amazon Location: With this architecture, you can: + Display asset locations on a map to illustrate the big picture. For example, showing a heat map using historical locations or events to help an operations or planning team. + Initiate events based on asset proximity to provide notice to a receiving department to prepare for a shipment arrival and reduce processing time. + Store asset locations to initiate actions in your backend applications or to analyze data over time. + Analyze location history to identify trends and opportunities for optimization. ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/asset-tracking.PNG) The following provides an overview of the steps required to build an asset tracking application: 1. Create your geofences in Geofence Collections and link Trackers to them. For more information, see [Geofencing an area of interest using Amazon Location](geofence-an-area.md). 1. Configure Amazon EventBridge to send a notification or initiate a process. For more information, see [Reacting to Amazon Location Service events with Amazon EventBridge](location-events.md). 1. Display your tracked assets and your active geofences on a map. For more information, see [Using maps](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html). 1. Save location data in long-term storage for further analysis. 1. Once you have built your application, you can use Amazon CloudWatch and AWS CloudTrail to manage your application. For more information, see [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). # Delivery applications The following is an illustration of a delivery application architecture using Amazon Location. With this architecture, you can: + Initiate events based on proximity of delivery agents so that pickups are ready in time and customers can be notified when their delivery is arriving. + Display driver locations, as well as pick-up and drop-off locations in near-real time on a map to show dispatch teams the big picture. + Store the locations of delivery agents so that you can act on them in your backend application or analyze them over time. + Analyze location history to identify trends and opportunities for optimization. ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/delivery.PNG) The following is an overview of the steps required to build a delivery application: 1. Create your geofence collections and link tracked devices to the collection. For more information see, [Geofencing an area of interest using Amazon Location](geofence-an-area.md). 1. Create an AWS Lambda function to automatically add and remove geofences as your orders are booked. 1. Configure Amazon EventBridge to send notifications or initiate a processes. For more information, see [Reacting to Amazon Location Service events with Amazon EventBridge](location-events.md). 1. Display tracked assets and active geofences on a map. For more information, see [Using maps](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html). 1. Save location data to long-term storage for further analysis. 1. Once you have built your application, you can use Amazon CloudWatch and AWS CloudTrail to manage your application. For more information, see [Monitor Amazon Location Service with Amazon CloudWatch](monitoring-using-cloudwatch.md) and [Log and monitor with AWS CloudTrail](logging-using-cloudtrail.md). # What is a data provider? Use Amazon Location Service to access geolocation resources from multiple data providers through your AWS account without requiring third-party contracts or integrations. This can help you focus on building your application, without having to manage third-party accounts, credentials, licenses, and billing. The following Amazon Location services use data providers. + ****Maps**** – Choose styles from different map providers when you [create a map resource](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html). You can use map resources to build an interactive map to visualize data. + ****Places**** – Choose a data provider when you [create a place index resource](https://docs.aws.amazon.com/location/previous/developerguide/places-prerequisites.html#create-place-index-resource) to support queries for geocoding, reverse geocoding, and searches. + ****Routes**** – Choose a data provider to support queries for route calculations in different geographies and applications when you [create a route calculator resource](https://docs.aws.amazon.com/location/previous/developerguide/routes-prerequisites.html#create-route-calculator-resource). With your chosen data provider, Amazon Location Service enables you to calculate routes based on up-to-date road network data, live traffic data, planned closures, and historic traffic patterns. Each provider gathers and curates their data using different means. They may also have varying expertise in different regions of the world. This section provides details about our data providers. You may select any data provider based on your preference. Make sure you read the terms of conditions when using Amazon Location Service data providers. For more information, see the [AWS Service Terms](https://aws.amazon.com/service-terms/). Also see the [Data privacy](data-privacy.md) section for more information about how Amazon Location protects your privacy. ## Map styles Each data provider provides a set of map styles to render the map data that they provide. For example a style might include satellite imagery, or might be optimized to show the roads for navigation. You can find the list and examples of the styles for each provider in the following topics. + [Esri map styles](esri.md#esri-map-styles) + [Grab map styles](grab.md#grab-map-styles) + [HERE map styles](HERE.md#HERE-map-styles) + [Open Data map styles](open-data.md#open-data-map-styles) ## More information about each data provider The following links provide more information about each data provider. + [Esri](esri.md) + [GrabMaps](grab.md) + [HERE Technologies](HERE.md) + [Open Data](open-data.md) # Features by data provider This section describes the features available in Amazon Location Service, categorized by data provider. The following table provides a high-level overview of the features. | Data provider | Geographical coverage | Feature coverage | AWS Region | | --- | --- | --- | --- | | Esri | Global | Maps, Places, Routes | [All Regions](location-regions.md#available-regions) where Amazon Location is available. | | Grab | [Southeast Asia](grab.md#grab-coverage-area) | Maps, Places, Routes | Asia Pacific (Singapore), ap-southeast-1, only. | | HERE | Global | Maps, Places, Routes | [All Regions](location-regions.md#available-regions) where Amazon Location is available. | | Open Data | Global | Maps | [All Regions](location-regions.md#available-regions) where Amazon Location is available. | The following tabs show details within each feature area. ------ #### [ Map Features ] The following table shows the map features by data provider. For more information about map concepts, see [Learn about Maps resources in Amazon Location Service](map-concepts.md). | Data provider | Supported map types | Vector zoom levels | Raster zoom levels | | --- | --- | --- | --- | | Esri | Vector Raster (imagery) For more information, see [Esri map styles](esri.md#esri-map-styles). | 0-15 | 0-23 | | Grab | Vector ([Southeast Asia](grab.md#grab-coverage-area) only) For more information, see [Grab map styles](grab.md#grab-map-styles). | 0-14 | none | | HERE | Vector Raster (imagery) Hybrid For more information, see [HERE map styles](HERE.md#HERE-map-styles). | 1-17 | 0-19 | | Open Data | Vector For more information, see [Open Data map styles](open-data.md#open-data-map-styles). | 0-15 | none | **Note** Zoom levels represent the maximum and minimum settings, as defined in each provider's APIs. Different areas of the map may have different maximums; for example, ocean tiles may have fewer detailed zoom levels than areas in major cities. MapLibre (and other map rendering engines) allow you to set minimum and maximum zoom levels, and will also honor the data provider zoom levels in an area, so you do not have to write code to handle these discrepancies. ------ #### [ Places and Search ] The following table shows the place and search features by data provider. For more information about place concepts, see [Learn about Places search in Amazon Location Service](places-concepts.md). | Data provider | Geocoding | Reverse Geocoding | Autocomplete | GetPlace | | --- | --- | --- | --- | --- | | Esri | All features, except: *   PlaceId* | All features, except: *   TimeZone* *   PlaceId* | All features | All features | | Grab | All features, except: *   unit type *    Categories not supported | All features | All features | All features, except: *   unit type* *   SubMunicipality* | | HERE | All features, except: *   unit number* *   unit type* *   relevance*    Additional [limitations on filtering](category-filtering.md#filter-limitations) | All features | All features | All features, except: *   unit number* *   unit type* *   SubMunicipality* | | Open Data | Not supported | Not supported | Not supported | Only supports: *   SubMunicipality* | ------ #### [ Route features ] The following table shows the route features by data provider. For more information about route concepts, see [Learn about routing in Amazon Location Service](route-concepts.md). For more detailed descriptions of route matrix limitations, see [Restrictions on departure and destination positions](calculate-route-matrix.md#matrix-routing-position-limits). | Data provider | Travel modes | Calculate route | Route matrix | | --- | --- | --- | --- | | Esri | Car, Truck, Walking | Departure and destination must be within 400 km of each other. The total travel time can't be more than 400 minutes. ArrivalTime is not supported. | Up to 10 departure and destination positions. Not supported in Korea. All departure and destination pairs must be within 400 km of each other. | | Grab | Car, Motorcycle. Walking and Bicycle in [selected cities](grab.md#grab-travel-mode-routes). | No distance limits. | Up to 350 departure and destination positions. | | HERE | Car, Truck, Walking | No distance limit. Routes that go more than 10 km outside a circle around the departure and destination positions will not be calculated. | Up to 350 departure and destination positions. All departure and destination positions must fall with a 180 km circle. Longer routes are supported, with [additional restrictions](calculate-route-matrix.md#matrix-routing-longer-routes). | | Open Data | Not supported | Not supported | Not supported | ------ Each data provider gathers and produces data in different ways. You can learn more about their coverage areas in the following topics: + [Coverage: Esri](esri.md#esri-places-coverage) + [Coverage: Grab](grab.md#grab-places-coverage) + [Coverage: HERE](HERE.md#HERE-places-coverage) + [Coverage: Open Data](open-data.md#open-data-places-coverage) If you encounter a problem with the data and want to report an error to the data provider, see the following topics: + [Error reporting to Esri](esri.md#esri-support) + [Error reporting for GrabMaps data](grab.md#grab-support) + [Error reporting to HERE](HERE.md#HERE-support) + [Error reporting and contributing to Open Data](open-data.md#open-data-support) # Esri Amazon Location Service uses Esri's location services to help AWS customers to use maps, geocode, and calculate routes effectively. Esri’s location services are built with high-quality, authoritative, and ready-to-use location data, curated by expert teams of cartographers, geographers, and demographers. For additional capability information, see [Esri](https://aws.amazon.com/location/data-providers/esri/) on *Amazon Location Service data providers*. **Topics** + [Esri map styles](#esri-map-styles) + [Coverage: Esri](#esri-places-coverage) + [Terms of use and data attribution: Esri](#esri-terms) + [Error reporting to Esri](#esri-support) ## Esri map styles Amazon Location Service supports the following Esri map styles when [creating a map resource](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html). **Note** Esri map styles that are not listed in this section are not supported. The Esri vector styles support alternate [Political views](map-concepts.md#political-views). ------ #### [ Esri Navigation ] **Esri Navigation** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/EsriNav.png) **Map style name**: `VectorEsriNavigation` This map provides a detailed basemap for the world symbolized with a custom navigation map style that's designed for use during the day in mobile devices. This comprehensive street map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. The vector tile layer in this map is built using the same data sources used for the World Street Map and other Esri basemaps. Enable the `POI` layer by setting it in [CustomLayers](https://docs.aws.amazon.com//location/previous/APIReference/API_MapConfiguration.html) to leverage the additional places data. For more information, see [Esri World Navigation](https://www.arcgis.com/home/item.html?id=63c47b7177f946b49902c24129b87252) on the Esri website. **Note** The`VectorEsriNavigation` map pictured above has the `POI` layer enabled. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Arial Italic + Arial Regular + Arial Bold + Arial Unicode MS Bold + Arial Unicode MS Regular ------ #### [ Esri Imagery ] **Esri Imagery** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/EsriImagery.png) **Map style name**: `RasterEsriImagery` This map provides one meter or better satellite and aerial imagery in many parts of the world and lower resolution satellite imagery worldwide. The map includes 15m imagery at small and mid-scales (\$11:591M down to \$11:72k) and 2.5m SPOT Imagery (\$11:288k to \$11:72k) for the world. The map features 0.5m resolution imagery in the continental United States and parts of Western Europe from Maxar. This map features additional Maxar submeter imagery in many parts of the world. In other parts of the world, the GIS User Community has contributed imagery at different resolutions. In select communities, very high-resolution imagery (down to 0.03m) is available down to \$11:280 scale. For more information, see [Esri World Imagery](https://www.arcgis.com/home/item.html?id=10df2279f9684e4a9f6a7f08febac2a9) on the Esri website. ------ #### [ Esri Light ] **Esri Light** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/EsriWorldTopo.png) **Map style name**: `VectorEsriTopographic` This provides a detailed basemap for the world symbolized with a classic Esri map style. This includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. This basemap is compiled from a variety of authoritative sources from several data providers, including the US Geological Survey (USGS), US Environmental Protection Agency (EPA), US National Park Service (NPS), Food and Agriculture Organization of the United Nations (FAO), Department of Natural Resources Canada (NRCAN), HERE, and Esri. Data for select areas is sourced from OpenStreetMap contributors. Additionally, data is provided by the GIS community. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Noto Sans Italic + Noto Sans Regular + Noto Sans Bold + Noto Serif Regular + Roboto Condensed Light Italic ------ #### [ Esri Light Gray Canvas ] **Esri Light Gray Canvas** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/EsriLightGray.png) **Map style name**: `VectorEsriLightGrayCanvas` This map provides a detailed basemap for the world symbolized with a light gray, neutral background style with minimal colors, labels, and features that's designed to draw attention to your thematic content. This vector tile layer is built using the same data sources used for the Light Gray Canvas and other Esri basemaps. The map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. For more information, see [Esri Light Gray Canvas](https://www.arcgis.com/home/item.html?id=c7e86d018d2945799cdc8e3dfbe30b43) on the Esri website. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Ubuntu Italic + Ubuntu Regular + Ubuntu Light + Ubuntu Bold ------ #### [ Esri Street Map ] **Esri Street Map** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/EsriStreet.png) **Map style name**: `VectorEsriStreets` This map provides a detailed basemap for the world symbolized with a custom navigation map style that's designed for use during the day in mobile devices. This comprehensive street map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. It also includes a richer set of places, such as shops, services, restaurants, attractions, and other points of interest. The vector tile layer in this map is built using the same data sources used for the World Street Map and other Esri basemaps. For more information, see [Esri World Street](https://www.arcgis.com/home/item.html?id=de26a3cf4cc9451298ea173c4b324736) on the Esri website. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Arial Italic + Arial Regular + Arial Bold + Arial Unicode MS Bold + Arial Unicode MS Regular ------ #### [ Esri Dark Gray Canvas ] **Esri Dark Gray Canvas** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/EsriDarkGray.png) **Map style name**: `VectorEsriDarkGrayCanvas` This map provides a detailed vector basemap for the world symbolized with a dark gray, neutral background style with minimal colors, labels, and features that's designed to draw attention to your thematic content. This map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. The vector tile layers in this map are built using the same data sources used for the Dark Gray Canvas raster map and other Esri basemaps. For more information, see [ Esri Dark Gray Canvas](https://www.arcgis.com/home/item.html?id=94521475e86b48f1ad2a21b2ea272d7a) on the Esri website. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Ubuntu Medium Italic + Ubuntu Medium + Ubuntu Italic + Ubuntu Regular + Ubuntu Bold ------ ## Coverage: Esri You can use Esri as a data provider to support queries for geocoding, reverse geocoding, and searches when you [create a place index resource](https://docs.aws.amazon.com/location/previous/developerguide/places-prerequisites.html#create-place-index-resource), or to support queries to calculate a route when you [create a route calculator resource](https://docs.aws.amazon.com/location/previous/developerguide/routes-prerequisites.html#create-route-calculator-resource). Esri provides different levels of data quality in different regions of the world. For additional information about coverage in your region of interest, see: + [Esri details on geocoding coverage](https://developers.arcgis.com/rest/geocode/api-reference/geocode-coverage.htm) + [Esri details on street networks and traffic coverage](https://doc.arcgis.com/en/arcgis-online/reference/network-coverage.htm) ## Terms of use and data attribution: Esri Before you use Esri's data, be sure you can comply with all applicable legal requirements, including license terms applicable to Esri and AWS. For more information about the AWS requirements, see [AWS Service Terms](https://aws.amazon.com/service-terms/). For information about Esri's attribution guidelines, see Esri's [Data Attributions and Terms of Use](https://www.esri.com/en-us/legal/terms/data-attributions). ## Error reporting to Esri If you encounter a problem with the data and want to report errors and discrepancies to Esri, follow Esri's technical support article for [How to: Provide feedback on basemaps and geocoding](https://support.esri.com/en/technical-article/000011831). # GrabMaps Grab is the largest delivery organization in Southeast Asia, with millions of driver partners and customers. Their subsidiary, [GrabMaps](https://www.grab.com/sg/business/maps/), creates up-to-date mapping data in those countries/regions for their own use, and others. Amazon Location Service uses GrabMaps' location services to help AWS customers use maps, geocode, and calculate routes effectively. GrabMaps' location services are built to provide high-quality, authoritative, and ready-to-use location data, specifically for southeast Asian countries. For information about additional capability, see [GrabMaps](https://aws.amazon.com/location/data-providers/grabmaps/) on *Amazon Location Service data providers*. **Important** Grab provides maps only for southeast Asia, and is available only in the Asia Pacific (Singapore) Region (ap-southeast-1). For more information, see [Countries/regions and area covered](#grab-coverage-area). **Topics** + [Grab map styles](#grab-map-styles) + [Coverage: Grab](#grab-places-coverage) + [Countries/regions and area covered](#grab-coverage-area) + [Terms of use and data attribution: Grab](#grab-terms) + [Error reporting for GrabMaps data](#grab-support) ## Grab map styles Amazon Location Service supports the following Grab map styles when [creating a map resource](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html): **Note** Grab map styles that are not listed in this section are currently not supported. ------ #### [ Grab Standard Light Map ] **Grab Standard Light Map** ![\[An image of Grab's standard light map style.\]](http://docs.aws.amazon.com/location/previous/developerguide/images/VectorGrabMonoStreet.png) **Map style name**: `VectorGrabStandardLight` Grab's standard basemap with detailed land use coloring, area names, roads, landmarks, and points of interest covering Southeast Asia. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Noto Sans Regular + Noto Sans Medium + Noto Sans Bold ------ #### [ Grab Standard Dark Map ] **Grab Standard Dark Map** ![\[An image of Grab's standard dark map style.\]](http://docs.aws.amazon.com/location/previous/developerguide/images/VectorGrabDarkStreet.png) **Map style name**: `VectorGrabStandardDark` Grab's dark variation of their standard basemap, with detailed land use coloring, area names, roads, landmarks, and points of interest covering Southeast Asia. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Noto Sans Regular + Noto Sans Medium + Noto Sans Bold ------ ## Coverage: Grab You can use Grab as a data provider to support queries for geocoding, reverse geocoding, and searches when you [create a place index resource](https://docs.aws.amazon.com/location/previous/developerguide/places-prerequisites.html#create-place-index-resource), or to support queries to calculate a route when you [create a route calculator resource](https://docs.aws.amazon.com/location/previous/developerguide/routes-prerequisites.html#create-route-calculator-resource). ## Countries/regions and area covered Grab provides maps only for southeast Asia, and is only available in the Asia Pacific (Singapore) Region (`ap-southeast-1`). Grab provides detailed data for the following countries/regions: + Malaysia + Philippines + Thailand + Singapore + Vietnam + Indonesia + Myanmar + Cambodia **Note** Outside of these areas, the Amazon Location Service resources created with Grab as a data provider will not provide any results. This includes search results or routes. The maps from Grab are within the following boundaries: + **South** – Latitude -21.943045533438166 + **West** – Longitude 90.0 + **North** – Latitude 31.952162238024968 + **East** – Longitude 146.25 For zoom levels 1–4, Grab includes global coverage. For zoom levels 5 and below, map tiles are provided only within this bounded box. **Note** Outside of this bounded box, the Amazon Location Service map resources created with Grab as a data provider will not return map tiles. To avoid seeing 404 errors in your application, you can limit the map with a bounding box, as described in [Setting extents for a map using MapLibre](setting-map-extents.md). ### Grab routing travel modes For routing, Grab provides **car** and **motorcycle** routing for all of the previously listed countries/regions. Grab does not support **truck** routing. For **bicycle** and **walking** routes, Grab supports the following cities:. + Singapore + Jakarta + Manila + Klang Valley + Bangkok + Ho Chi Minh City + Hanoi ## Terms of use and data attribution: Grab When using Grab's data, you must comply with all applicable legal requirements, including license terms applicable to Grab and AWS. For more information about the AWS requirements, see [AWS Service Terms](https://aws.amazon.com/service-terms/). For information about GrabMaps' attribution guidelines, see Section 9.23 of Grab's [Data Attributions and Terms of Use](https://www.grab.com/sg/terms-policies/transport-delivery-logistics/). ## Error reporting for GrabMaps data If you encounter a problem with the data from GrabMaps, and want to report errors or discrepancies, [contact AWS technical support](https://support.console.aws.amazon.com/support/home#/case/create?issueType=customer-service). # HERE Technologies Amazon Location Service uses HERE Technologies’ location services to help AWS customers use maps, geocode, and calculate routes effectively. HERE's location data offers a location-centric platform that's open, secure, and private. By selecting HERE location data, you are selecting accurate, fresh, and robust data that's deployed natively on the AWS Cloud. For additional capability information, see [HERE](https://aws.amazon.com/location/data-providers/here-technologies/) on *Amazon Location Service data providers*. **Topics** + [HERE map styles](#HERE-map-styles) + [Coverage: HERE](#HERE-places-coverage) + [Terms of use and data attribution: HERE](#HERE-terms) + [Error reporting to HERE](#HERE-support) ## HERE map styles Amazon Location Service supports the following HERE map styles when [creating a map resource](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html): **Note** HERE map styles that are not listed in this section are currently not supported. ------ #### [ HERE Explore ] **HERE Explore** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/StyleVectorHere.png) **Map style name**: `VectorHereExplore` **HERE Explore** A detailed, neutral base map of the world. The street map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. Includes a fully designed map of Japan. Fonts Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Fira GO Italic + Fira GO Regular + Fira GO Bold + Noto Sans CJK JP Light + Noto Sans CJK JP Regular + Noto Sans CJK JP Bold ------ #### [ HERE Imagery ] **HERE Imagery** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/here_satellite_raster.png) **Map style name**: `RasterHereExploreSatellite` **HERE Imagery** HERE Imagery provides high resolution satellite imagery with global coverage. ------ #### [ HERE Hybrid ] **HERE Hybrid** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/here_satellite_hybrid.png) **Map style name**: `HybridHereExploreSatellite` **HERE Hybrid** HERE Hybrid style displays the road network, street names, and city labels over satellite imagery. This style overlays two map tiles: the satellite image (raster tile) in the background and the road network and labels (vector tile) on top. This style will automatically retrieve both the raster and vector tiles required to render the map. **Note** Hybrid styles use both vector and raster tiles when rendering the map that you see. This means that more tiles are retrieved than when using either vector or raster tiles alone. Your charges will include all tiles retrieved. Fonts Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Fira GO Italic + Fira GO Regular + Fira GO Bold + Noto Sans CJK JP Light + Noto Sans CJK JP Regular + Noto Sans CJK JP Bold ------ #### [ HERE Contrast (Berlin) ] **HERE Contrast (Berlin)** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/HERE_contrast_2000x1200.png) **Map style name**: `VectorHereContrast` **HERE Contrast (Berlin)** A detailed base map of the world that blends 3D and 2D rendering. The high contrast street map includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. Fonts Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Fira GO Regular + Fira GO Bold **Note** This style was renamed from `VectorHereBerlin` (HERE Berlin maps). `VectorHereBerlin` is deprecated, but will continue to work in applications that use it. ------ #### [ HERE Explore Truck ] **HERE Explore Truck** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/StyleVectorHereTruck.png) **Map style name**: `VectorHereExploreTruck` **HERE Explore Truck** A detailed, neutral base map of the world. The street map builds on top of the HERE Explore style, and highlights track restrictions and attributes (including width, height, and HAZMAT) with symbols and icons, to support use cases within transport and logistics. Fonts Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Fira GO Italic + Fira GO Regular + Fira GO Bold + Noto Sans CJK JP Light + Noto Sans CJK JP Regular + Noto Sans CJK JP Bold ------ For additional information about map data quality in different regions of the world, see [HERE map coverage](https://developer.here.com/documentation/map-tile/dev_guide/topics/coverage-information.html). ## Coverage: HERE You can use HERE as a data provider to support queries for geocoding, reverse geocoding, and searches when you [create a place index resource](https://docs.aws.amazon.com/location/previous/developerguide/places-prerequisites.html#create-place-index-resource), or to support queries to calculate a route when you [create a route calculator resource](https://docs.aws.amazon.com/location/previous/developerguide/routes-prerequisites.html#create-route-calculator-resource). HERE provides different levels of data quality in different regions of the world. For additional information about coverage in your region of interest, see the following: + [HERE geocoding coverage](https://developer.here.com/documentation/geocoder/dev_guide/topics/coverage-geocoder.html) + [HERE car routing coverage](https://www.here.com/docs/bundle/routing-api-developer-guide-v8/page/topics/coverage/car-routing.html) + [HERE truck routing coverage](https://www.here.com/docs/bundle/routing-api-developer-guide-v8/page/topics/coverage/truck-routing.html) ## Terms of use and data attribution: HERE Before you use HERE data, be sure you can comply with all applicable legal requirements, including license terms applicable to HERE and AWS. Because of licensing limitations, you may not use HERE to store geocoding results for locations in Japan. For information about the AWS requirements, see [AWS Service Terms](https://aws.amazon.com/service-terms/). For additional information about HERE's attribution guidelines, see Section 2 of HERE Technologies' [Supplier Terms Applicable to Location and Other Content](https://legal.here.com/en-gb/terms/general-content-supplier-terms-and-notices). ## Error reporting to HERE To report map errors and discrepancies to HERE, go to [https://www.here.com/contact](https://www.here.com/contact) and choose **Report a map error**. # Open Data Amazon Location Service provides access to open source map data via the Open Data provider. Open Data provides global basemaps built from the [Daylight map distribution](https://daylightmap.org) of [OpenStreetMap (OSM)](https://www.openstreetmap.org/), [Natural Earth](https://www.naturalearthdata.com/), and other open data sources. The maps provided are designed to support different applications and use cases, including logistics and delivery, and data visualization in web and mobile environments. With over a million map makers, the OSM community updates hundreds of thousands of features per day. Amazon Location Service regularly incorporates these edits. For additional capability information, see [Open Data](https://aws.amazon.com/location/data-providers/open-data/) on *Amazon Location Service data providers*. **Topics** + [Open Data map styles](#open-data-map-styles) + [Coverage: Open Data](#open-data-places-coverage) + [Terms of use and data attribution: Open Data](#open-data-terms) + [Error reporting and contributing to Open Data](#open-data-support) ## Open Data map styles Amazon Location Service supports the following map styles when [creating a map resource](https://docs.aws.amazon.com/location/previous/developerguide/using-maps.html): Open Data map styles support alternate [Political views](map-concepts.md#political-views). ------ #### [ Open Data Standard Light ] **Open Data Standard Light** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/VectorOpenDataStandardLight.png) **Map style name**: `VectorOpenDataStandardLight` This provides a detailed basemap for the world in a light map style, suitable for website and mobile application use. This includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. This basemap is based on the OSM [Daylight map distribution](https://daylightmap.org) compiled from OpenStreetMap (OSM) contributors. The OSM community includes over 1.8 million contributors who update more than 500,000 features daily. Amazon Location Service incorporates these edits on a regular basis. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Amazon Ember Bold,Noto Sans Bold + Amazon Ember Condensed RC Bold,Noto Sans Bold + Amazon Ember Condensed RC Regular,Noto Sans Regular + Amazon Ember Medium,Noto Sans Medium + Amazon Ember Regular Italic,Noto Sans Italic + Amazon Ember Regular,Noto Sans Regular + Amazon Ember Regular,Noto Sans Regular,Noto Sans Arabic Regular + Amazon Ember Condensed RC Bold,Noto Sans Bold,Noto Sans Arabic Condensed Bold + Amazon Ember Bold,Noto Sans Bold,Noto Sans Arabic Bold + Amazon Ember Regular Italic,Noto Sans Italic,Noto Sans Arabic Regular + Amazon Ember Condensed RC Regular,Noto Sans Regular,Noto Sans Arabic Condensed Regular + Amazon Ember Medium,Noto Sans Medium,Noto Sans Arabic Medium **Note** The fonts used by `VectorOpenDataStandardLight` are combined fonts that use `Amazon Ember` for most glyphs but `Noto Sans` for glyphs unsupported by `Amazon Ember`. ------ #### [ Open Data Standard Dark ] **Open Data Standard Dark** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/VectorOpenDataStandardDark.png) **Map style name**: `VectorOpenDataStandardDark` This is a dark-themed map style that provides a detailed basemap for the world, suitable for website and mobile application use. This includes highways, major roads, minor roads, railways, water features, cities, parks, landmarks, building footprints, and administrative boundaries. This basemap is based on the OSM [Daylight map distribution](https://daylightmap.org) compiled from OpenStreetMap (OSM) contributors. The OSM community includes over 1.8 million contributors who update more than 500,000 features daily. Amazon Location Service incorporates these edits on a regular basis. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Amazon Ember Bold,Noto Sans Bold + Amazon Ember Condensed RC Bold,Noto Sans Bold + Amazon Ember Condensed RC Regular,Noto Sans Regular + Amazon Ember Medium,Noto Sans Medium + Amazon Ember Regular Italic,Noto Sans Italic + Amazon Ember Regular,Noto Sans Regular + Amazon Ember Regular,Noto Sans Regular,Noto Sans Arabic Regular + Amazon Ember Condensed RC Bold,Noto Sans Bold,Noto Sans Arabic Condensed Bold + Amazon Ember Bold,Noto Sans Bold,Noto Sans Arabic Bold + Amazon Ember Regular Italic,Noto Sans Italic,Noto Sans Arabic Regular + Amazon Ember Condensed RC Regular,Noto Sans Regular,Noto Sans Arabic Condensed Regular + Amazon Ember Medium,Noto Sans Medium,Noto Sans Arabic Medium **Note** The fonts used by `VectorOpenDataStandardDark` are combined fonts that use `Amazon Ember` for most glyphs but `Noto Sans` for glyphs unsupported by `Amazon Ember`. ------ #### [ Open Data Visualization Light ] **Open Data Visualization Light** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/VectorOpenDataVisualizationLight.png) **Map style name**: `VectorOpenDataVisualizationLight` This is a light-themed style with muted colors and fewer features that aids in understanding overlaid data. This basemap is based on the OSM [Daylight map distribution](https://daylightmap.org) compiled from OpenStreetMap (OSM) contributors. The OSM community includes over 1.8 million contributors who update more than 500,000 features daily. Amazon Location Service incorporates these edits on a regular basis. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Amazon Ember Bold,Noto Sans Bold + Amazon Ember Condensed RC Bold,Noto Sans Bold + Amazon Ember Condensed RC Regular,Noto Sans Regular + Amazon Ember Medium,Noto Sans Medium + Amazon Ember Regular Italic,Noto Sans Italic + Amazon Ember Regular,Noto Sans Regular + Amazon Ember Regular,Noto Sans Regular,Noto Sans Arabic Regular + Amazon Ember Condensed RC Bold,Noto Sans Bold,Noto Sans Arabic Condensed Bold + Amazon Ember Bold,Noto Sans Bold,Noto Sans Arabic Bold + Amazon Ember Regular Italic,Noto Sans Italic,Noto Sans Arabic Regular + Amazon Ember Condensed RC Regular,Noto Sans Regular,Noto Sans Arabic Condensed Regular + Amazon Ember Medium,Noto Sans Medium,Noto Sans Arabic Medium **Note** The fonts used by `VectorOpenDataVisualizationLight` are combined fonts that use `Amazon Ember` for most glyphs but `Noto Sans` for glyphs unsupported by `Amazon Ember`. ------ #### [ Open Data Visualization Dark ] **Open Data Visualization Dark** ![\[alt text not found\]](http://docs.aws.amazon.com/location/previous/developerguide/images/VectorOpenDataVisualizationDark.png) **Map style name**: `VectorOpenDataVisualizationDark` This is a dark-themed style with muted colors and fewer features that aids in understanding overlaid data. This basemap is based on the OSM [Daylight map distribution](https://daylightmap.org) compiled from OpenStreetMap (OSM) contributors. The OSM community includes over 1.8 million contributors who update more than 500,000 features daily. Amazon Location Service incorporates these edits on a regular basis. **Fonts** Amazon Location serves fonts using `[GetMapGlyphs](https://docs.aws.amazon.com/location-maps/latest/APIReference/API_GetMapGlyphs.html#API_GetMapGlyphs_RequestSyntax)`. The following are available font stacks for this map: + Amazon Ember Bold,Noto Sans Bold + Amazon Ember Condensed RC Bold,Noto Sans Bold + Amazon Ember Condensed RC Regular,Noto Sans Regular + Amazon Ember Medium,Noto Sans Medium + Amazon Ember Regular Italic,Noto Sans Italic + Amazon Ember Regular,Noto Sans Regular + Amazon Ember Regular,Noto Sans Regular,Noto Sans Arabic Regular + Amazon Ember Condensed RC Bold,Noto Sans Bold,Noto Sans Arabic Condensed Bold + Amazon Ember Bold,Noto Sans Bold,Noto Sans Arabic Bold + Amazon Ember Regular Italic,Noto Sans Italic,Noto Sans Arabic Regular + Amazon Ember Condensed RC Regular,Noto Sans Regular,Noto Sans Arabic Condensed Regular + Amazon Ember Medium,Noto Sans Medium,Noto Sans Arabic Medium **Note** The fonts used by `VectorOpenDataVisualizationDark` are combined fonts that use `Amazon Ember` for most glyphs but `Noto Sans` for glyphs unsupported by `Amazon Ember`. ------ ## Coverage: Open Data Open Data includes maps with global coverage for rendering with an [Amazon Location Service map resource](map-concepts.md). **Note** Open Data is for use with Amazon Location Service map resources only. You can't use Open Data as a data provider to support queries for geocoding, reverse geocoding, and searches, or to support queries to calculate a route. ## Terms of use and data attribution: Open Data Before you use Open Data, be sure you can comply with all applicable legal requirements, including license terms applicable to Open Data and AWS. For more information about the AWS requirements, see [AWS Service Terms](https://aws.amazon.com/service-terms/). For information about Open Data attribution guidelines, see OpenStreetMap's [Copyright and License](https://www.openstreetmap.org/copyright) and OpenStreetMap's [Licence/Attribution Guidelines](https://wiki.osmfoundation.org/wiki/Licence/Attribution_Guidelines). ## Error reporting and contributing to Open Data OpenStreetMap (OSM) and Natural Earth are community-driven open data projects. If you encounter a problem with the data, you can report the errors or directly contribute fixes or suggestions. + To report an error or offer a suggestion in OSM, you can create a *note* on the map. This is a comment on the map that assists contributors in making fixes to the map. You create notes through the [OpenStreetMap website](https://openstreetmap.org/). For more information about notes, see [Notes](https://wiki.openstreetmap.org/wiki/Notes) in the *OpenStreetMap wiki*. + For more information about contributing directly to OpenStreetMap, including adding locations and fixing errors, see [Contribute map data](https://wiki.openstreetmap.org/wiki/Contribute_map_data) in the *OpenStreetMap wiki*. + To submit a correction request for data in Natural Earth, you can submit an issue through the [Natural Earth website](https://www.naturalearthdata.com/issues/). **Note** Correcting errors in OpenStreetMap can happen quickly, however, it can take time for corrections to appear in the Daylight map distribution of the OSM data that is used by the Open Data provider. The [Daylight Map Distribution](https://daylightmap.org) website provides more information about the process. Additionally, Amazon Location Service updates the map data used in Amazon Location Service approximately monthly. # Terms of use and data attribution for data providers Before you use a data provider, be sure you can comply with all applicable legal requirements, including license terms applicable to the use of the provider. For more information about the AWS requirements, see [AWS Service Terms](https://aws.amazon.com/service-terms/). When using a data provider with your Amazon Location resources for your application or documentation, be sure to provide attributions for each data provider you use. For more information on compliance and attribution for each data provider, see the following topics. + **Esri** – [Terms of use and data attribution: Esri](esri.md#esri-terms) + **Grab** – [Terms of use and data attribution: Grab](grab.md#grab-terms) + **HERE** – [Terms of use and data attribution: HERE](HERE.md#HERE-terms) + **Open data** – [Terms of use and data attribution: Open Data](open-data.md#open-data-terms)