kepler.gl
kepler.gl copied to clipboard
Geoserver integration
are there plans to support geoserver out of the box as a data source?
@geoHeil could you describe the use case here, share an example and the technology you are planning to use? If there is any documentation, it would be great if you could share with us.
Not sure what type of geospatial data storage you have at uber (would be interested to learn more about that) in case of an open source setup something like http://www.geomesa.org/ which acts as a geotools datastore provider for geoserver would be my data provider.
Geoserver then publishes a feed - even real time - as wmf / wpf standardized services. I.e. It would be great if consumption of such services would work out of the box.
Also an open source pendant of http://www.ccri.com/case-studies/stealth/ would be great, I.e simply adding CQL capabilities to a layer loaded from geoserver should be mostly sufficient. Ziyi Li [email protected] schrieb am Fr. 15. Juni 2018 um 20:41:
@geoHeil https://github.com/geoHeil could you describe the use case here, share an example and the technology you are planning to use? If there is any documentation, it would be great if you could share with us.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/uber/kepler.gl/issues/85#issuecomment-397708779, or mute the thread https://github.com/notifications/unsubscribe-auth/ABnc9AMVKMPACIlNiYtR9OQcEqsafpt8ks5t8_-WgaJpZM4UXC4M .
Looking for an integration with postgres/postgis but any server side aggregation would be fine. Any advice on how to develop as plugin or wrapper app would be useful
We are gonna look into implementing data connectors along with examples to show their abilities
We can create an example with node, PostgreSQL with RESTful API. There is a (post)[https://blog.logrocket.com/setting-up-a-restful-api-with-node-js-and-postgresql-d96d6fc892d8/] can be referred to
Is there any update on the use case that @geoHeil is proposing? :)
Kepler should be standards compliant. From that perspective it should add support for all OGC standard data types like WMS, WFS, WMTS etc. What @geoHeil is asking is basically an implementation of those specifications. There are different servers like Geoserver, ESRI ArcGIS Server or Mapserver which implement OGC Map service specs
I agree that having full OGC OWS compatibility would be nice. But we could start with a much simpler approach by adding a functionality under "Load Map using URL" to resolve RESTful HTTP queries which generate GeoJSON results, for example. There, you could simply paste a well-defined/standardized WFS GetFeature request which would generate a GeoJSON. This dynamically created aeromap layer extract could serve as an example. Right now I have to call this URL, download the returned result as .json
and upload this file via "Load Files" to kepler.gl. This is a bit cumbersome.
Bonus: Exchanging outputFormat=application/json
to outputFormat=csv
in the above example URL will return a CSV with OGC WKT geometries which could be interesting for testing as well.
Has this any progress?