Skip to content

DATAMONGO-1453 - Fix GeoJson conversion when coordinates are Integers. #369

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 2 commits into from

Conversation

christophstrobl
Copy link
Member

We now use Number instead of Double for reading "coordinates" from GeoJSON representations.


Should at least be back ported to 1.9.x and 1.8.x.

We now use Number instead of Double for reading "coordinates" from GeoJSON representations.
mp911de pushed a commit that referenced this pull request Jun 24, 2016
We now use Number instead of Double for reading "coordinates" from GeoJSON representations.

Original pull request: #369.
mp911de pushed a commit that referenced this pull request Jun 24, 2016
We now use Number instead of Double for reading "coordinates" from GeoJSON representations.

Original pull request: #369.
mp911de pushed a commit that referenced this pull request Jun 24, 2016
We now use Number instead of Double for reading "coordinates" from GeoJSON representations.

Original pull request: #369.
mp911de pushed a commit that referenced this pull request Jun 24, 2016
We now use Number instead of Double for reading "coordinates" from GeoJSON representations.

Original pull request: #369.
@mp911de
Copy link
Member

mp911de commented Jun 24, 2016

That's merged, backported to 1.8.x, 1.9.x and forward-ported to 2.0 on issue/DATAMONGO-1176.

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.

2 participants