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

support GeoCSV #427

Open
joostschouppe opened this issue Feb 1, 2017 · 0 comments
Open

support GeoCSV #427

joostschouppe opened this issue Feb 1, 2017 · 0 comments

Comments

@joostschouppe
Copy link

Hi,
I'm sorry if this is implemented already, and just not updated towards opendata.antwerpen.be ...

Anyway, our current CSV outputs return a geometry column, which in the case of polygons is filled with an embedded GeoJSON. That's quite unexpected.

A better option would be to fill this column according to the GeoCSV standard, and fill the geometry column with WKT, a very basic way to define geometries.

Default projection is WKT seems to be WGS84, but most Belgian governments will give you their data in Lambert72. There seems to be a way to define projection in WKT, but I don't really understand that part myself. Maybe offering a .prj file with the description of the used projection is an easier option. Or convincing governments to offer their data in WGS84 of course (though most classical local geodata consumers will be expecting Lambert72 anyway). These two projections are VERY hard to confuse, so one might just ignore the problem too and leave it to consumer discretion...

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

No branches or pull requests

1 participant