Rapid account: Geocoding

Geocoding / GeocodeSupport

讨论区

16
Title
Created at (Click to sort ascending)
A
1
Hi, both of your examples should be mitigated as of now. We are also working on a general mitigation for this problem to get the boundary relations as geojson, but this will take approx. two weeks until it is fully mitigated. Tue 7:30 20/2/24
A
5
Hello, as the upstream data that is pulled in here is a "living creature" where sometimes the interlinking between city relations and city center nodes may break (and be repaired later on), it's a good idea to use a limit of 2 and check each of the returned results for osm_type=relation (or in geojson format for category=boundary instead of category=place) to be on the happy side and use that one if you need a geojson polygon. You can also send us any reports on cities you'll find at support(at)geocodingapi.net. Mon 1:07 19/2/24
A
5
Hello, as the upstream data that is pulled in here is a "living creature" where sometimes the interlinking between city relations and city center nodes may break (and be repaired later on), it's a good idea to use a limit of 2 and check each of the returned results for osm_type=relation (or in geojson format for category=boundary instead of category=place) to be on the happy side and use that one if you need a geojson polygon. You can also send us any reports on cities you'll find at support(at)geocodingapi.net. Mon 1:07 19/2/24
A
3
We rolled out a mitigation that fixes a wrong http header we currently get from the RapidAPI proxy if a Content-Type is set in a request (which is not needed by the way). We are still in contact with RapidAPI in finding out why they add that header since today that shouldn't be there in the first place and hope that they fix it as well. But with our mitigation you should not see the errors anymore and get results again even while sending a Content-Type header on your GET request. Mon 4:25 11/9/23
A
3
We rolled out a mitigation that fixes a wrong http header we currently get from the RapidAPI proxy if a Content-Type is set in a request (which is not needed by the way). We are still in contact with RapidAPI in finding out why they add that header since today that shouldn't be there in the first place and hope that they fix it as well. But with our mitigation you should not see the errors anymore and get results again even while sending a Content-Type header on your GET request. Mon 4:25 11/9/23
A
1
Hi, this API does not support POST requests nor batch requests, but you may try to set up a postman collection with a csv input while using one of the GET endpoints and run this e.g. via newman cli to save the results into a csv. Please also note while switching from POST to GET in Postman: don't send a Content-Type request header for a GET request. Mon 10:24 11/9/23