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

Use Feature<TGeometry, TProps> when constructing FeatureCollection? #104

Open
wagich opened this issue Apr 1, 2018 · 1 comment
Open

Comments

@wagich
Copy link

wagich commented Apr 1, 2018

Using the default Feature class, the properties get converted to a Dictionary<string, object> before the class is serialized which makes all the property names identical to their .NET versions and circumvents any JSON serialization conventions.

I thought I could use the generic version Feature<TGeometry, TProps> to get full serialization of my property object, but unfortunately FeatureCollection only accepts the subclass Feature (which is a Feature<TGeometry, Dictionary<string, object>>. Is there a specific reason for this?

@YaroslavKormushyn
Copy link

Implemented by #160.

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

2 participants