Support reverse geocoding

[jsanz]

It would be a great enhancement to support reverse geocoding. Both HERE and Mapzen support this commonly requested operation and we could return a normalized table row so the user can put it all in the same row or on different fields. Something like:

UPDATE mytable t
  SET t.address = g.address, t.postcode = g.postcode, t.city = g.city, t.country = g.country 
FROM ( 
    SELECT address, postcode, city, country 
    FROM CDB_ReverseGeocodePoint(t.the_geom)
) g 

[rafatower]

I'm adding this to the product spreadsheet so that it can be prioritized. Otherwise I don't see much room in the upcoming months to implement such enhancement, though it shouldn't be hard at all.

[jaakla]

Note that Mapzen geocoding gives quite raw data from OSM which is hard (if possible at all) to be used for proper global level reverse geocoder. Sample point: https://search.mapzen.com/v1/reverse?api_key=search-_yiyajI&point.lat=48.858268&point.lon=2.294471 . HERE gives clear data: street address, city, country, just as we need

[ethervoid]

This could be done in the future using DO

[oriolbx]

Is there any update regarding this issue? @alizcano

[ethervoid]

Nope that I'm aware of