Web Map for navPlace Enabled Resources

[thehabes]

Abstract

With navPlace being GeoJSON, almost any underlying web map (Leaflet, OSM, Google Maps, etc.) can render the shapes. The "hard" part is extracting the FeatureCollection(s) and desired metadata from IIIF resources in order to format them for the map. IIIF resources may have embedded or referenced child items and those items may have referenced or embedded FeatureCollection objects and users may desire certain metadata to go along with the FeatureCollection's Features even if not explicitly placed within GeoJSON.properties. The "easy" part is passing those formatted FeatureCollections to the map.

At this time a non-common serverless open source implementation exists at https://map.rerum.io written in HTML + CSS + Javascript deployed through GitHub Pages. The repo is https://github.com/CenterForDigitalHumanities/navplace-viewer. If a commons implementation comes to be, the goal would be to deploy the stand alone common element with matching functionality at https://map.rerum.io.

Primary Considerations

• Can only support Presentation API 3 or later, only JSON-LD 1.1 resources are allowed.
• The element will not receive GeoJSON until after page load. It would look for ?iiif-content= or listen to other HTML elements which would receive a URL or JSON that relates to a IIIF resource.
• There would be a recursive function (with limits to avoid infinite loops) to crawl the resource hierarchy (ex. If a Collection, crawl each Manifest and each Canvas/Range in those Manifests) and collect together every navPlace property's FeatureCollection. This means resolving referenced resources along the way. This means grabbing pertinent metadata and automating it to GeoJSON.properties (think about label and summary, easy check-and-grab)
• There are options to control the behavior in the point above. The user may only want the navPlace property from the top level resource and not the children. The user may only want to process embedded data and ignore referenced data.
• Ideally, this could be coupled with Mirador or UV so as to have the map element as an inset to the IIIF Viewers themselves.
• annotations would not be processed.