Closed NicoJuicy closed 8 years ago
Hi NicoJuicy, First if you're gonna add breaking changes it would be great to have a flag like "useDbGeography". Then I don't completely understand what you want. Does your example means that you want properties that are instances of DbGeography serialized properly? Or do you want to be able to query against DbGeography properties?
Actually, i'm starting a project that will have the CRUD of DbGeography ( probably querying also). I'll probably won't add the entire DbGeography functionality immediatly ( don't know what it all does right now). But add it once a need it.
Fyi: And i meant that, one record in the database POINT (51.015574 2.725285) returns to
"GeographyPoint": {"type": "Point","coordinates":[142.1,64.1]}
So right now, i'm kinda wondering where to start. That's all. But it would probably be better just to dive into it and see where i come out :p
If you have any clues on what i might consider or some edge-cases i'll run into. I'm happy to hear about it. Otherwhise, you can just close this question :)
For future reference use:
I would add DbGeography to your library ( odata v4), any thoughts before i begin? I don't see something similar to it in odataValue:
Example below:
Danger is, i need to fork the library to use the "odata" .Net version, based on : http://www.odata.org/blog/geospatial-data-support-in-odata/ . There seem to be some differences with my example code above.
Or should i add the standard and add a wrapper arround the .Net DbGeography type and release a nuget package, so it becomes the standard as described on the odata website?