Add OpenStreetMaps to reverse geo lookup

Location data can be checked from OpenStreetMaps too
This commit is contained in:
2018-02-26 13:51:45 +09:00
parent 8bc346f28c
commit 05bc66e57d
2 changed files with 180 additions and 60 deletions

View File

@@ -27,7 +27,7 @@ reverse_geolocate.py [-h] -x
[XMP SOURCE FOLDER [XMP SOURCE FOLDER ...]]
[-l LIGHTROOM FOLDER] [-s]
[-f <overwrite, location, city, state, country, countrycode>]
[-g GOOGLE API KEY] [-n] [-v] [--debug] [--test]
[-g GOOGLE API KEY] [-o] [-n] [-v] [--debug] [--test]
### Arguments
@@ -38,6 +38,7 @@ Argument | Argument Value | Description
-s, --strict | | Do strict check for Lightroom files and include the path into the check
-f, --field | Keyword: overwrite, location, city, state, country, countrycode | In the default no data is overwritten if it is already set. With the 'overwrite' flag all data is set new from the Google Maps location data. Other arguments are each of the location fields and if set only this field will be set. This can be combined with the 'overwrite' flag to overwrite already set data
-n, --nobackup | | Do not create a backup of XMP sidecar file when it is changed
-o, --openstreetmap | | Use OpenStreetMap instead of the default google maps
-g, --google | Google Maps API Key | If available, to avoid the access limitations to the reverse location lookup
-v, --verbose | | More verbose output. Currently not used
--debug | | Full detailed debug output. Will print out alot of data
@@ -75,6 +76,23 @@ order | type | target set
6 | sublocality_level_2 | Location
7 | route | Location
### OpenStreetMap data priority
order | type | target set
--- | --- | ---
1 | country_code | CountryCode
2 | country | Country
3 | state | State
4 | city | City
5 | city_district | City
6 | state_district | City
7 | county | Location
8 | town | Location
9 | suburb | Location
10 | hamlet | Location
11 | neighbourhood | Location
12 | raod | Location
### Script stats and errors on update
After the script is done the following overview will be printed