亚马逊Quick Sight支持GeoJSON点线图层

With Amazon Quick Sight layer maps, you can now plot points and routes, like store locations across a city or flights leaving an airport.

Geospatial maps help businesses spot patterns that are tied to location, like how a region is performing or where customers are concentrated. Amazon Quick Sight supports this with multiple map types, including point maps, filled maps, and layer maps.

When layer maps first launched, you could upload a GeoJSON file to draw custom shape layers, such as sales territories or districts, and join those shapes to a dataset.

That handled regions and boundaries well, but it didn’t cover the individual locations inside them or the routes running between them. Layer maps now support two more geometry types from the same GeoJSON workflow: Point and LineString.

Points mark specific locations, such as individual store or facility sites. A LineString traces the route between locations, like a delivery path or a flight between airports.

Amazon Quick Sight, the business intelligence (BI) capability of Amazon Quick, is a unified BI service.

It delivers modern interactive dashboards, natural language querying, pixel-perfect reports, machine learning (ML) insights, and embedded analytics at scale.

Amazon Quick brings together AI agents for business insights, research, and automation in one integrated experience, helping you work smarter and faster while maintaining security and access policies.

In this post, we walk through the dataset and GeoJSON structure that layer maps require. We also explain how points and lines work in a layer map visual and when to choose each.

Finally, we cover advanced techniques for controlling the viewport, layering geometries, and updating GeoJSON files programmatically.

Dataset structure considerations A layer map gets its shapes from a GeoJSON file and its metrics from a Quick Sight dataset, and a shared key joins the two. How you structure each one determines what the map can show.

This section covers what you need before you start and how a GeoJSON file is organized. Prerequisites The following are the prerequisites that you need before creating a layer map in Quick Sight: A GeoJSON file describing your geometry.

A Quick Sight dataset holding the metrics and dimensions. A join key shared between the Quick Sight dataset and the GeoJSON file. The GeoJSON file must be saved in .geojson format, with a maximum supported file size of 100 MB.

Structure of the GeoJSON file GeoJSON is a JSON-based format for describing geographic features such as points and lines.

{ "type": "FeatureCollection", "features": [{ "type": "Feature", "geometry": { "type": "Point", "coordinates": [88.4, 22.6] }, "properties": { "prop0": "value0" } }, { "type": "Feature", "geometry": { "type": "LineString", "coordinates": [ [88.2, 22.4], [88.9, 23.1], [89.5, 22.8], [90.1, 23.6] ] }, "properties": { "prop0": "value0" } }] } The structure of the file is as follows: FeatureCollection is the whole file.

It has a type of FeatureCollection and a features array. Feature is a single map element. It carries a geometry (the shape) and a properties object, which holds the join key. geometry has a type (Point, LineString, or Polygon) and its coordinates.

The coordinates hold a single [longitude, latitude] position for a Point, and an ordered list of positions for a LineString.

Configuring the Quick Sight dataset and its GeoJSON In Quick Sight, when you configure a layer in a layer map visual, there are two primary settings to consider.

The first is the Geometry type to visualize, which sets which geometry from the GeoJSON file renders: Points, Lines, or Polygons.

A layer renders one geometry type at a time, so when a file mixes types like the preceding example, only Features of the selected type appear on the map.

The second is matching the Shape file key field to the Dataset key field, which links each Feature in the GeoJSON to a row in your Quick Sight dataset. The field names don’t need to be identical, but the