Chapter 20. Spatial objects

Table of Contents

Importing spatial object metadata
Embedding maps in the templates
Spatial searching
Accessing spatial data programmatically
Via the HTTP API
Via the PHP API

CONTENTdm® does not have a provision for spatial browsing, searching, or visualization. Spatial boundary coordinates may be encoded in a qualified Dublin Core "Coverage-Spatial" field per commonly accepted best practice, but these are often encoded in different ways across sites, and often not machine-readable. Without being able to intuitively search or visualize it, the utility of this metadata is therefore negligible.

This is where UNLVSpatial comes in. UNLVSpatial enables import, storage, browsing, searching, and cartographic visualization of spatial object metadata. It provides:

UNLVSpatial works especially well for cartographic materials, but it can work with any other kind of object that can be described geographically. It uses the Google Maps v3 API.

Importing spatial object metadata

Spatial metadata must reside in DCSV-encoded DCMI Box or DCMI Point format inside a "Coverage" element of an object's metadata record.

Because CONTENTdm® does not support querying of spatial data, UNLVSpatial requires that any spatial data for spatial searching be stored in the dmBridge data store. To get it there requires importing it, which is done in the "Spatial Objects" section of the Control Panel. Spatial metadata that is not to be used with spatial searching does not need to be imported, as it will be parsed out of the "Coverage" element on-the-fly.

Spatial metadata is associated with individual CONTENTdm® objects. The current version of UNLVSpatial supports both rectangular and point data. Polar-projection and other non-Cartesian maps are not supported. UNLVSpatial supports only decimal degree coordinates. One CONTENTdm® object supports one point or boundary rectangle.