GeoDB Cities

FREEMIUM
Verified
By Michael Mogley | Updated 5 days ago | Data
Popularity

9.9 / 10

Latency

88ms

Service Level

100%

Health Check

100%

Back to All Discussions

Bad Request error

Rapid account: Mzerbinatti
mzerbinatti
6 years ago

Hi,

Something has changed in this API?

Because I was usually using it and today I’m receiving “Bad Request” error.

Could you verify, please?

Thank you!

Rapid account: Wirefreethought
wirefreethought Commented 6 years ago

Glad it’s working for you. And great suggestion about the search normalization regarding accent marks and such. I will look into that.

Rapid account: Mzerbinatti
mzerbinatti Commented 6 years ago

Oh, and I have updated my code, and now it is working with the new parameters (radius and distanceUnit)

Rapid account: Mzerbinatti
mzerbinatti Commented 6 years ago

]

Oh, one suggestion !!

When we find cities, they are one returned when we type their name corretly, with accent mark, for example:

  • São Paulo (the cities are returned)

But if I type:

  • Sao Paulo (without accent mark at “a”)

The cities are not returned…

It would be better if the cities are returned with both (São Paulo and Sao Paulo), desconsidering de accents marks of the names of cities,

Thank you!!

Rapid account: Wirefreethought
wirefreethought Commented 6 years ago

My pleasure! Let me know once things are working so I can close this ticket.

Please feel free to also write about any suggested improvements or desired features.

Thanks for your valued support!

Rapid account: Mzerbinatti
mzerbinatti Commented 6 years ago

Oh ok, I have read theses changes now…

I will update my code to solve it!!

Thank you for your fast answser !!

Rapid account: Wirefreethought
wirefreethought Commented 6 years ago

Yes, unfortunately, your call was affected by those changes. I had tried to send out a message to existing users asking if they may be affected and didn’t hear anything back, so assumed no one was using those parameters. In the future, any such potentially breaking changes will be scoped by an API version, so your existing code will continue to work. Sorry about that.

To summarize, the changes are:

  • nearLocationRadius -> radius
  • nearLocationRadiusUnit -> distanceUnit

See updated API docs here:

https://wirefreethought.github.io/geodb-cities-api-docs/#operation–v1-geo-cities–cityId–nearbyCities-get

Sorry again.

Rapid account: Wirefreethought
wirefreethought Commented 6 years ago

The only recent change happened on March 18. See this blog entry: http://geodb-cities-api.wirefreethought.com/entries/feature/sort-cities-get-the-user-s-current-city–and-more. Nothing has changed since then.

Can you paste the specific request you’re making? I’ll have a look shortly.

Join in the discussion - add comment below:

Login / Signup to post new comments