Skip to content

GeoPoint issue on PostgreSQL #3285

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
vferdiansyah opened this issue Dec 25, 2016 · 5 comments
Closed

GeoPoint issue on PostgreSQL #3285

vferdiansyah opened this issue Dec 25, 2016 · 5 comments

Comments

@vferdiansyah
Copy link

Environment Setup

  • Server

    • parse-server version (Be specific! Don't say 'latest'.) : 2.3.1
    • Operating System: macOS Sierra 10.12.2
    • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): localhost
  • Database

    • PostgreSQL version: 9.6.1
    • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): localhost

I'm using Parse Dashboard (v1.0.22) to enter my data. When I'm inputting a GeoPoint, at first everything looks good (see image below).

screen shot 2016-12-25 at 10 17 52

But after I refreshed my window, it seems like the latitude and longitude was reversed automatically somehow (see image below).

screen shot 2016-12-25 at 10 20 01

I'm using Google Maps in my app so I have to use coordinate.latitude as GMap's longitude and coordinate.longitude as GMap's latitude to make the map works.

Anyone experienced the same issue?

@hramos
Copy link
Contributor

hramos commented Feb 10, 2017

Looks like this should be opened against the parse-dashboard repo instead.

@hramos hramos closed this as completed Feb 10, 2017
@pewh
Copy link

pewh commented Feb 26, 2017

Please reopen this issue. I also get same issue on latest version (2.3.5).

This bug is ony happen when update geopoint via cloud code or parse dashboard. But this bug is not triggered when save new row with geopoint. This bug is blocking me on project.

EDIT: This bug is not triggered when I use MongoDB.

@flovilmart flovilmart reopened this Feb 26, 2017
@vferdiansyah
Copy link
Author

Same as @pewh. My first project that used MongoDB doesn't experience this issue. Only the one that is using PostgreSQL. Still persist on Parse Server 2.3.5 and Parse Dashboard 1.0.25.

@vferdiansyah
Copy link
Author

screen shot 2017-03-23 at 9 49 20

This is what I get when I tried to query using REST API. The value really is reversed.
Any updates on this?

@flovilmart
Copy link
Contributor

@vferdiansyah thanks for the PR, there seems to be some failing tests

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

4 participants