Most times, a small change to the query or an additional parameter in your API request should get you a result. A list of support query parameters is available here
For forward geocoding, this might indicate our geocoder was not able to find an address match. Human input addresses are challenging to decode and require a bit of data cleansing. Please make sure input addresses are formatted well and there aren't any spelling mistakes, descriptive addresses, abbreviations. Examples:
- Addresses with spelling errors: Elephant and Castle, London SE1 6SB, Lobndon, SE1 6SB
- Descriptive addresses: Opposite to Starbucks, Cerrito 836, piso 10, C1010AAR Buenos Aires, Argentina
- Incorrectly formatted addresses: Cerrito 836, Argentina, Buenos Aires, piso 10, C1010AAR, Argentina
- Incorrect spacing: 12015 CloverlandCourt, Baton Rouge, 70809
Our geocoder prefers addresses formatted as below:
- <House number>, <street>, <neighbourhood>, <city>, <state>, <country>, <postcode>
For reverse geocoding, this indicates either the coordinates are incorrect or in the ocean
Please write to us via our contact page or email us at hello@locationiq.com with sample request logs and we'll be happy to help you debug this.