Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geoserver integration #85

Open
geoHeil opened this issue Jun 1, 2018 · 9 comments
Open

Geoserver integration #85

geoHeil opened this issue Jun 1, 2018 · 9 comments

Comments

@geoHeil
Copy link

geoHeil commented Jun 1, 2018

are there plans to support geoserver out of the box as a data source?

@ziyili66
Copy link

@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.

@geoHeil
Copy link
Author

geoHeil commented Jun 17, 2018 via email

@ghirardinicola
Copy link

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

@macrigiuseppe
Copy link
Collaborator

We are gonna look into implementing data connectors along with examples to show their abilities

@heshan0131
Copy link
Contributor

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

@marcusnygren
Copy link

Is there any update on the use case that @geoHeil is proposing? :)

@mapsensedev
Copy link

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

@michikommader
Copy link

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.

bjungs pushed a commit to imec-int/kepler.gl that referenced this issue Nov 14, 2022
…ot-loading

[BUBR-911] fix(package): update kepler fork
@DeepUpRosenthal
Copy link

Has this any progress?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants