Geolocate tag can't include XMP:Location?

[mikelee33]

There must be a good reason why writing the Geolocate tag with GPS coordinates can't generate an XMP:Location tag from the Geolocation Subregion information, but I am at a loss to figure out why. It just seems appropriate to also include that information in a standard XMP tag, when GeoNames typically furnishes it.

Phil, what am I missing? I would sure like to see XMP:Location written by default, if at all possible.
Many thanks,
Mike

[Phil Harvey]

I'll have to think about why this is the case.  Note that XMP-iptcCore:Location is a legacy tag, and it is recommended to use the XMP-iptcExt tags instead.

Having said this, you can always use the API Geolocation option and copy the geolocation tags to wherever you want.

- Phil

[StarGeek]

I had typed up a whole response as to why I felt this wasn't a good idea based upon the way the old Geosetter program wrote this. Then I tested exiftool's geolocate on my own GPS coordinates and had to start over.

The XMP-iptcCore:Location,  IPTC:Sub-location, and XMP-iptcExt:LocationShownSublocation are meant to be a subregion of the City. The fourth (first two) and fifth level down in the hierarchy, below the City. Checking some locations using exiftool's geolocate, the GeolocationSubregion would fit in between Province/State and City, which doesn't have a matching tag. Some examples I got were New York County (in between New York the state and New York City), and San Diego County (in between California and San Diego the city).

An example of location would be Miraflores, Westwood, or Hollywood.

Personally, I try to use the "the name of a well known location" definition of the tag, though I am a bit flexible about the "well known" part. If I'm at a convention, I'll use the name of the convention center (Anaheim Convention Center, San Diego Convention Center). If it's a smaller location, then I'll use the best name I can. For example, at a book signing, I'll use the name of the store.

[mikelee33]

Phil and StarGeek, Thank your for your response.

I am somewhat influenced by Adobe in many things, and Lightroom and Bridge still use IPTC Core sublocation in their metadata panels. I have always found that extra bit of location information (typically county for us) useful.

Notably, in all the images I have processed so far with Geolocation, subregion data was present, and represented an official location description (e.g., county, commune, etc.). I am impressed with the consistency in GeoNames database.

Anyway, I can understand not supporting this legacy tag if it is not a good idea. It may just cause compatibility issues with software which doesn't support its display, right?

Thanks again,
Mike

[Phil Harvey]

Hi Mike,

Looking into this further, I think that StarGeek had the answer.  The specification for XMP-iptcCore:Location and IPTC:Sub-Location doesn't fit with the larger-area county or sub-region name returned by ExifTool's GeolocationSubregion.

- Phil