Skip to content

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

Closed
wants to merge 7 commits into from

Conversation

zfang
Copy link

@zfang zfang commented Feb 20, 2016

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.

…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.
@facebook-github-bot
Copy link

@zfang updated the pull request.

@facebook-github-bot
Copy link

@zfang updated the pull request.

@facebook-github-bot
Copy link

@zfang updated the pull request.

@facebook-github-bot
Copy link

@zfang updated the pull request.

@aliuy
Copy link

aliuy commented Feb 22, 2016

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?

Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.

Can you help us take a look? What should we do here?

@zfang zfang closed this Feb 22, 2016
@zfang zfang reopened this Feb 22, 2016
@aliuy
Copy link

aliuy commented Feb 23, 2016

Oh sweet, looks like re-running tests by re-opening the PR worked 😄

@drew-gross
Copy link
Contributor

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 :(

@drew-gross drew-gross closed this Feb 23, 2016
@madsb
Copy link
Contributor

madsb commented Jan 2, 2017

Any chance that geojson will be supported seeing that Parse.com will shut down in the near future?

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

Successfully merging this pull request may close these issues.

5 participants