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

Explore ways to handle custom properties #1

Open
JackWink opened this issue May 12, 2018 · 0 comments
Open

Explore ways to handle custom properties #1

JackWink opened this issue May 12, 2018 · 0 comments
Milestone

Comments

@JackWink
Copy link
Contributor

Since go is statically typed, custom properties are not really supported, neither are they part of the GeoJSON spec.

However, geobuf/pygeobuf are dynamically typed and therefor encode extra properties on any of the json objects.

Finding a way to expose or pull out the custom properties would be nice, but non-essential for the initial release (as they aren't part of the spec). However, if I can find a nice way to support it with minimal effort, I'll go for it.

The best way I can think of right now is to support it in decode only, perhaps returning it with type loss or with a provided schema.

@JackWink JackWink added this to the v0.0.1 milestone May 12, 2018
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