Skip to content
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

Some geocoding requests return wrong lat and lon #6

Open
koldLight opened this issue Dec 4, 2017 · 3 comments
Open

Some geocoding requests return wrong lat and lon #6

koldLight opened this issue Dec 4, 2017 · 3 comments

Comments

@koldLight
Copy link
Member

This issue will list all the observed request that the cartociudad API is returning wrong geocoding results.

  • "cuesta del observatorio 4, 18080 granada", should return 37.190205, -3.5947971. Now is returning 37.18018, -3.5898. Request here

If you observed this behaviour with another address, please add a new comment to this issue with:

  • The exact text in your request
  • The expected result (e.g. when querying the same text to google maps)
@koldLight koldLight changed the title Some geocoding request return wrong lat and lon Some geocoding requests return wrong lat and lon Dec 4, 2017
@fgoerlich
Copy link

I have a lot of these cases. As a sample:

  • “avenida jose solla bouzas 37, soutomaior, Pontevedra, 36690” , should return 42.34897, -8.60646 (Google). Now is returning 42.33488, -8.567259. Request here. But the funny thing is that the server returns "state = 0", not found, but "stateMsg = Resultado exacto de la búsqueda", (see the last line of the request), so what is returning is the centroid of the municipality. It should return "state = 10", "stateMsg = Se devuelve la entidad superior". If I drop "bouzas" from the address, then the server returns the correct coordinates: 42.34096, -8.606041. Request here.

If this is of any help I have a collection of these cases. Too many to list them here.

@cjgb
Copy link
Collaborator

cjgb commented May 15, 2021

Those questions should be addressed to the API providers. Our package is a simple, lightweight interface to it.

@fgoerlich
Copy link

fgoerlich commented May 15, 2021

I have done that already.
Accoding to them I should call the “candidates” service before calling the “find” service. “Candidates” don’t return coordinantes.
I can provide you details if you wish.

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

3 participants