Jump to content

Digikam/GSoC2010/ReverseGeocoding: Difference between revisions

From KDE Community Wiki
Gvoicu (talk | contribs)
Gvoicu (talk | contribs)
Line 39: Line 39:
[http://www.geonames.org/ geonames.org]
[http://www.geonames.org/ geonames.org]
* provides both reverse geocoding and elevation information
* provides both reverse geocoding and elevation information
* returned address elements if they exists:
** country
** state
** county
** city
** a list of nearby streets for non-USA
** nearest street for USA only
** distance from the the given coordinate to returned address


== Storing information ==
== Storing information ==

Revision as of 08:20, 15 May 2010

Reverse geocoding will be implemented for the new version of the GPSSync plugin as part of GSOC by Gabriel Voicu, mentored by Michael G. Hansen.

Short description

The idea of reverse geocoding is that when the coordinates on earth of an image are known, the application retrieves the associated human readable location: City, street, country, etc. and stores this information in the image. The location names can be stored in the images as new tags, allowing the user to easily search for all pictures he took in a country, city or even street.

Where is the code?

  • gsoc-geocoding: General place for experiments and small code snippets.
  • GPSSync2: New version of the GPSSync plugin.
  • WorldMapWidget2: Widget to display the location of images on both Google Maps and Marble. Required by GPSSync2.

Backends

Google Maps

Google Maps V3 API

  • provides both reverse geocoding and elevation information
  • for a given coordinate, returns the next address elements if they exists:
    • country
    • state
    • county
    • city
    • district
    • street
    • street number

OpenStreetMap Nominatim

OSM Nominatim

  • Marble already has integration for this service
  • Address elements returned, if they exists:
    • country
    • state
    • state district
    • county
    • city
    • city district
    • street

Geonames.org

geonames.org

  • provides both reverse geocoding and elevation information
  • returned address elements if they exists:
    • country
    • state
    • county
    • city
    • a list of nearby streets for non-USA
    • nearest street for USA only
    • distance from the the given coordinate to returned address

Storing information

The textual location descriptions can be stored as tags and in the dedicated location fields provided by XMP and IPTC. However, there are some competing tags which store the same information.