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

Check wether GeoJSON should be returned as string #8

Open
eFrane opened this issue Jan 19, 2017 · 2 comments
Open

Check wether GeoJSON should be returned as string #8

eFrane opened this issue Jan 19, 2017 · 2 comments
Labels
Milestone

Comments

@eFrane
Copy link
Member

eFrane commented Jan 19, 2017

Currently GeoJSON fields are returned in their native
glib-json representation which can be difficult to use
for programmers accessing liboparl via gobject-introspection
in e.g. python.

We should do some research on wether it would be better
to return the full GeoJSON string and let the user deal
with it however they wish.

@konstin
Copy link
Member

konstin commented Jan 19, 2017

While I haven't looked at the details, I suggest returning json as this is the data type. It might also be reasonable to include a geojson validator in liboparl.

@eFrane
Copy link
Member Author

eFrane commented Jan 19, 2017

@konstin: Do you mean as JSON String or as JSON Object?

@eFrane eFrane added this to the 0.3 milestone Nov 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants