Defining source spatial data
Last updated
Last updated
When you add a source, Builder attempts to recognize if there is a spatial definition to render its associated layer. The spatial definition of your source depends on the column storing your spatial data and its specific type. Builder will automatically recognize the spatial data definition when possible. If not, you can manually define your data using the layer panel UI in the data section.
For Builder to automatically recognize the spatial data definition, regardless of whether the source is a table or an SQL query, your source must contain at least one valid spatial column with its related type as follows:
Column storing geometry type: This column should store either point, line, or polygon geometry in a valid format. The column can have any name.
Column storing spatial index ID: To be recognized by default, the spatial column should follow our naming convention:
H3: The column must be named h3
.
Quadbin: The column must be named quadbin
.
If Builder cannot automatically recognize a spatial data definition, you can still load it as a source in the map and use the UI to define your spatial column and type. Once your definition is set, you can click "Apply Selection" and Builder will use that definition to render your layer.
If your source contains multiple spatial columns, you can use the UI to decide which specific spatial column and type you want to use to render the layers associated with your source. For example, you might have a column containing the point geometry and additional columns representing the isochrones from that location.
Note: The spatial data definition is set at the source level; therefore, you must ensure consistency in the definition for all layers linked to that source.
Special considerations
The spatial data definition is set at the source level; therefore, you must ensure consistency in the definition for all layers linked to that source. If you change the definition but there are other layers coming from the same source, a modal will appear notifying you of the components in the map that will be affected if you proceed with the changes.
Note spatial source definition is not supported for pre-generated tilesets.