You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This requires a bit of planning but would be a very useful addition.
Location field can be implemented in many ways:
Latitude/Longitude as separate float columns
or, postGIS's POINT type columns
or a human-readable address (useful when collecting via forms etc)
or systems that support flexible precision like Google's Plus Codes
But assuming location is somehow available per-record, it can be rendered as markers or polygons on a mapview (OpenStreatMap or LeafletJS can do this in a royalty-free way, but Google Maps / MapBox etc are other alternatives.
This requires a bit of planning but would be a very useful addition.
Location field can be implemented in many ways:
POINT
type columnsBut assuming location is somehow available per-record, it can be rendered as markers or polygons on a mapview (OpenStreatMap or LeafletJS can do this in a royalty-free way, but Google Maps / MapBox etc are other alternatives.
Airtable supports this with an extension.
The text was updated successfully, but these errors were encountered: