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
Our data warehouse is built in postgresql. As we are handling complex spatial it would be great to serve PostGIS geometries directly in Evidence, without the extra step of needing to generate and save geojson files from the database. This way we could serve a dashboard that creates choropleth maps of parcels or cadastral districts more easily.
What problem would this solve?
Native support of PostGIS geometries to remove steps of exporting the data unnecessarily to serve it to evidence.
How should it work?
My SQL query includes the PostGIS geometry column and I can use this column as a base for the spatial data of an AreaMap component
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Our data warehouse is built in postgresql. As we are handling complex spatial it would be great to serve PostGIS geometries directly in Evidence, without the extra step of needing to generate and save geojson files from the database. This way we could serve a dashboard that creates choropleth maps of parcels or cadastral districts more easily.
What problem would this solve?
Native support of PostGIS geometries to remove steps of exporting the data unnecessarily to serve it to evidence.
How should it work?
My SQL query includes the PostGIS geometry column and I can use this column as a base for the spatial data of an AreaMap component
Beta Was this translation helpful? Give feedback.
All reactions