Recommendation: basic properties for the index map as a whole

[kgjenkins]

Define some (optional) properties that would appear at the top level of the geojson object and describe the index map as a whole. For example, author, publisher, date (or date range).

I think Tom had an example of this in his Geo4LibCamp 2018 slides.

[kgjenkins]

• title
• publisher
• date
• scale
• content of the individual tiles (if not obvious from the title), for example topo maps vs aerial photos.
• metadataUrl

[kgjenkins]

I think this still needs to be addressed under the "Set- and Flight-level metadata" section in the new version doc.

[tbrittnacher]

Yes, I'm in favor of starting to leverage the ability to embed human-readable metadata into a GeoJSON header, and hopefully tools will be developed to help users read and write metadata in that area.

[kgjenkins]

We've been discussing this a bit during the GBL sprint. Briefly, we came up with three possibilities, which are not necessarily exclusive:

A. Add simple properties (title, publisher, scale, etc.) to the top level of the OIM document.
B. Include a link to a webpage with more details, or a link to the corresponding Aardvark json for the map series
C. Embed the full Aardvark json into the top level of the OIM document, as the value of an "aardvark" or other-named property

GBL wouldn't necessarily need to do anything with any of this.