Amazon Quick Sight Adds Map Points and Routes to Business Dashboards
Enterprise AI
Amazon Quick Sight Adds Map Points and Routes to Business Dashboards
AWS Machine LearningOct 26, 2026
Amazon Quick Sight layer maps now render GeoJSON Point and LineString features, joining map geometry to business data through shared keys.
Amazon Quick Sight layer maps now support GeoJSON Point and LineString features, enabling dashboards to show individual locations and paths alongside business data. AWS announced the capability in a technical post dated October 23, 2026. Points can represent sites such as stores or facilities, while LineStrings connect ordered coordinates to depict routes such as flights or deliveries.
A layer map combines geometry from a GeoJSON file with metrics and dimensions from a Quick Sight dataset. A shared key links each GeoJSON feature to a dataset row; the key fields do not need identical names, but their values must match. AWS specifies that the GeoJSON file must use the .geojson format and can be up to 100 MB. A layer displays one geometry type at a time, so a file containing points and lines requires separate layers to show both together.
The new point layers differ from Quick Sight’s native point-map visual. Layer-map points require explicit coordinates and use a uniform marker size, but they allow more precise viewport control and can be combined with other geometry. Native point maps can geocode location names and support dynamic sizing and styles. For routes, users can encode line color from joined dataset fields and adjust width and opacity.
Geometry in a layer map is stored in the GeoJSON file, so refreshing the dataset updates its metrics but does not move points or redraw changed routes. Geometry changes require replacing the file and republishing the dashboard. For automated updates, AWS describes using Amazon S3 and Quick Sight APIs. Dashboards can also combine separate map visuals—for example, route lines with stop markers—by stacking them in a free-form layout with matching map bounds. AWS says each sheet supports up to five layer-map visuals. The feature gives teams a way to place fixed geographic shapes and operational data in the same dashboard, while retaining a separate process for changing the underlying map geometry.
Industry Impact
Richer operational map dashboards
Retail, aviation, logistics, and facilities operations
Overview
Quick Sight users can now combine fixed GeoJSON locations and routes with business metrics, making dashboards more useful for viewing sites, flights, or deliveries in geographic context. Product managers and business leaders can assess whether the new layers fit operational reporting needs, while developers can automate geometry updates through S3 and Quick Sight APIs. A key constraint is that geometry is separate from dataset metrics: changing coordinates or routes requires replacing the GeoJSON file and republishing the dashboard.
Key Impact Points
Teams can link GeoJSON features to dataset rows using shared key values, even when the key fields have different names.
Route lines can be styled using joined dataset fields, while point layers provide explicit locations with uniform marker sizes.
Geometry changes require a separate file replacement and dashboard republication; each sheet supports up to five layer-map visuals.
Opportunities
Operational mapping workflows
Retail, aviation, logistics, and facilities operations
Organizations that already use Quick Sight can build dashboards that pair site or route geometry with operational measures, such as store or facility data and flight or delivery routes. This may help teams examine metrics in geographic context without placing geometry in the dataset itself. For changing routes or locations, teams can use the documented S3 and Quick Sight API approach to automate file and dashboard updates. Implementation planning should account for the 100 MB GeoJSON limit, separate layers for different geometry types, and the need to replace and republish geometry when it changes. The article does not specify a new pricing model or direct revenue stream.
GeoJSON-powered operations dashboards
Problem: Operational metrics may be difficult to interpret without corresponding site locations or route paths.
Solution: Join GeoJSON Point or LineString features to Quick Sight dataset rows through shared key values and display them with business data.
Target Users: Teams monitoring stores, facilities, flights, or deliveries in Quick Sight.
Business Value: Adds geographic context to operational reporting and supports styled route lines using dataset fields.
Revenue Potential: No direct revenue mechanism is specified; potential value is in internal reporting and workflow improvements.
