Do any fields exist to store local Points of Interest: With name and GEO prefera

[colink]

If I have an image relating to a specific location, is there a formal way to store names and Geo for local points of interest eg Museum, Church, Bus Station?

For this to be useful some systems would need to read this data.

I assume I could create custom fields, but then who would read that data?

Thanks ColinK

[Phil Harvey]

Hi Colin,

Take a look at the XMP-iptcExt tags.  Also the XMP-iptcCore tags may have some useful tags.

- Phil

[colink]

Thanks for the prompt reply - as usual Phil

I had looked at those previously and most tags, I do not see anything that specifically relates to Points or Places of Interest or anywhere to add 'nearby' places.

The only thing I can find is a custom tag "GeotatePOI" described here

https://static.bhphotovideo.com/lit_files/87393.pdf

It appears in this image
https://www.controlledvocabulary.com/images/drp2091169-sfw-q60-all-wicc.jpg

with this data
Lincoln Memorial|10|121.0|38.889269|-77.049932, Constitution Gardens|10|138.0|38.890378|-77.047711, Vietnam Veterans Memorial|10|148.0|38.891062|-77.047949, West Potomac Park|12|201.0|38.891685|-77.050688

This appears to be the most appropriate option, however as a search for "GeotatePOI" returns few results, so I am not sure who would ever read this data.

The data is readable by ExifTool and many online meta data viewers.

This appears to be a suitable field to use (along with XMP-Geotate:GeotateGRL XMP-Geotate:GeotateRGCVersion) unless someone has a better solution.

To clarify my intentions. I am keen that wherever an image is found online and where meta data is published alongside the image (like Flickr does) that the proximity of the image subject to local Points of Interest is also published.

Thanks ColinK

[StarGeek]

I had looked at those previously and most tags, I do not see anything that specifically relates to Points or Places of Interest or anywhere to add 'nearby' places.

I would guess that Phil was thinking of the LocationShown structured tag, which can be accessed as the flattened tags: LocationShownSublocation, LocationShownCity, LocationShownProvinceState, LocationShownCountryName, LocationShownCountryCode, LocationShownWorldRegion and a few others, including GPS data.  This structure is also in the example image you linked.  While it technically is for what is in the image, it wouldn't be much of a stretch to add nearby POI.

The only thing I can find is a custom tag "GeotatePOI" described here

Just adding a direct link to page 18, which is where the tag is mentioned
https://static.bhphotovideo.com/lit_files/87393.pdf#page=18

It appears to be a very simple tag, just a string with the values separated by commas.  It should be easy enough to add a User Defined Tag definition if you wanted to write it.

This appears to be the most appropriate option, however as a search for "GeotatePOI" returns few results, so I am not sure who would ever read this data.

Probably not much beyond exiftool and similar programs (exiv2?). 

The data is readable by ExifTool and many online meta data viewers.

Which often run exiftool on the backend

This appears to be a suitable field to use (along with XMP-Geotate:GeotateGRL XMP-Geotate:GeotateRGCVersion) unless someone has a better solution.

Myself, I would probably use HierarchicalSubject, but that's because that's my favorite tag to dump random bits of data.  It's a common enough tag and can be viewed in most modern programs.  In this case you could use a simple "Nearby Points of Interest|Lincoln Memorial" to add the data, even extending it if you wanted to add the other bits of data, like "Nearby Points of Interest|Vietnam Veterans Memorial|Distance 148.0", etc.  (Though that does beg the question what unit of measurement is the distance?)

Even adding it to something basic like Description would be fine.  Just add the data to the end of the tag.  So the example you linked would become:

This statue of the 16th President of the United States depicts a 19 foot high seated Abraham Lincoln in contemplation inside the Lincoln Memorial. It was carved of Georgia white marble by the Piccirilli Brothers under the supervision of the sculptor, Daniel Chester French and took four years to create, and completed in 1920.

Nearby Points of Interest
Lincoln Memorial
Category 10
Distance 121.0
Latitude 38.889269
Longitude -77.049932
Constitution Gardens
Category 10
Distance 138.0
Latitude 38.890378
Longitude -77.047711
Vietnam Veterans Memorial
Category 10
Distance 148.0
Latitude 38.891062
Longitude -77.047949
West Potomac Park
Category 12
Distance 201.0
Latitude 38.891685
Longitude -77.050688

That would make it more easily visible to anyone who looks at the metadata.

To clarify my intentions. I am keen that wherever an image is found online and where meta data is published alongside the image (like Flickr does) that the proximity of the image subject to local Points of Interest is also published.

Flickr does use exiftool on the back end which is why you can see the GeotatePOI tag at that site but I don't think you would see the data in the GeotatePOI in very many other places.

And to be honest, I would think that showing this data would not be high priority for most people.  Though I'm all for adding any data you can easily add to an image.  Once it's in the file, it's usually possible to move it to a different place later using exiftool if you so desire.  But unless you can get this data into the file in a fairly automated way (as it seems to be with the program for the device you linked), it seems like it would be more trouble than it's worth.

[colink]

@StarGeek

I really appreciate your detailed reply. It has clarified some things.

I am not quite ready to implement this, but will come back to this thread if I need help.

=====
If there are any useful examples of how to include HierarchicalSubject, in a CSV file if would be helpful.

Thanks ColinK