-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Serialize GeoPoint to GeoJson #524
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
Conversation
…o legacy coordinates. GeoPointCoder can now deserialize both legacy coordinates and GeoJson and legacy coordinates for backward compatibility. In addition, '2dsphere' instead of '2d' is used for spatial indexing so that GeoJson can be indexed.
@zfang updated the pull request. |
@zfang updated the pull request. |
@zfang updated the pull request. |
@zfang updated the pull request. |
Hey @gfosco - we'd like to introduce GeoJSON coordinates to enable compatibility with databases outside MongoDB. We're running in to a test failure... which look transient?
Can you help us take a look? What should we do here? |
Oh sweet, looks like re-running tests by re-opening the PR worked 😄 |
Yep that one is a transient. This is a cool PR but for a significant amount of time we will have Parse.com and Parse Server both accessing the same database, and Parse.com won't understand this new data format. Unfortunately that means we can't accept it :( |
Any chance that geojson will be supported seeing that Parse.com will shut down in the near future? |
This change allows GeoPointCoder to serialize GeoPoint to GeoJson as opposed to legacy coordinates. GeoPointCoder can now deserialize both legacy coordinates and GeoJson and legacy coordinates for backwards compatibility. In addition, '2dsphere' instead of '2d' is used for spatial indexing so that GeoJson can be indexed.