Ed Freyfogle

commenting as someone who often has people ask about this kind of thing the main thing people seem to be interested in - is attribution required? - can the data...

yes, do you have any test cases we could start trying to work with? Unfortunately I don't see a simple solution here as all we have to work with is...

Will also do a blog post on the OpenCage blog whenever you are ready. Could be a general announcement or if you prefer an interview with one of you. Just...

Hi, Google is great, but the lack of openness of the data, and thus limitations on what is possible with it, are a major turn off. One alternative is the...

Just to update this issue, the address-formatting repo has moved to https://github.com/OpenCageData/address-formatting we now have 100% coverage and 86% of territories have at least one test. Slowly I am adding...

thanks, yes, this should be fixed on our end. Looking now

ok fix is now live, `offset_string` should not always be a string ``` "timezone": { "name": "UTC", "now_in_dst": 0, "offset_sec": 0, "offset_string": "+0000", "short_name": "UTC" }, ```

I think this issue can be closed, [the blog post](https://blog.opencagedata.com/post/new-r-packages-for-accessing-the-opencage-geocoding-api) was published almost 18 months ago 😀

fantastic, but ideally the response would return the name AND the address, not just the address. Both are relevant, they are just split across two OSM objects

Hi @boxed I'm one of the people running the [OpenCage geocoder](https://geocoder.opencagedata.com/), we use nominatim (and other geocoders), and have fairly large volume of queries per day. We could definitely supply...