You would like to see your IIIF Presentation API 3 Manifest represented as a polygon on open source world map based user interfaces such as Leaflet or Google Maps. This could mean simply displaying a geometric shape on a map, but may include more data from the resource in connection with the geometric shape to facilitate robust functionality within the MapUI.
This Manifest extends the Manifest used in the simple image service recipe. See that recipe for more information about the Manifest.
The third party GeoJSON-LD context is included alongside the IIIF Presentation 3 context. This supplies the vocabulary terms for the GeoJSON-LD Annotation bodies since the IIIF Presentation 3 context does not describe those terms. The field
@context can be an array, and when it is the IIIF Presentation API 3.0 context must be the last item in the array.
Applications that strictly follow Linked Data practices will find that nested GeoJSON coordinate arrays are incompatible with the processing model of JSON-LD 1.0. The JSON-LD 1.1 processing model does not have this restriction. Be aware if you plan to serialize JSON-LD into other semantic data formats or markup languages such as RDF.
The Manifest contains one Annotation Page with one Annotation. The Annotation body is GeoJSON-LD, which is supported by a number of open source mapping systems. A client can parse out the Annotation from the Manifest and pass the Annotation body into MapUI systems resulting in rendered geometric shapes on a world map. Often, data from the resource such as an image URL, label or description is connected with those shapes via
properties in GeoJSON. You can see the coordinates in the body of the Annotation on the Manifest render in a Leaflet viewer. You can also see a serialization of these coordinates into
<feature>s render in a MapML implementation – NOT YET –.
- [Geolocate Manifest to Multiple Polygons][TBD]
- [Geolocate Manifest to a Point][TBD]
- [Tagging Annotation]