Skip to content
Syntax Encoding Scheme · DCMI classes and encoding schemes

dcterms:Box: how the DCT Box syntax encodes a region, with examples

Published Formatory editorial team
http://purl.org/dc/terms/Box

The set of regions in space defined by their geographic coordinates according to the DCMI Box Encoding Scheme.

A map sheet, an aerial photograph or a climate dataset is usually about a piece of ground with edges. dcterms:Box is the DCMI answer to recording those edges in a form a machine can parse. It is a syntax encoding scheme, formally an rdfs:Datatype, and it tells a consuming system that the string in front of it follows the DCMI Box rules: labeled coordinate limits separated by semicolons.

Anatomy of a Box value

A Box value is a list of name=value pairs. The specification defines ten components:

Component Holds
northlimit, southlimit latitude (or northing) of the top and bottom edges
eastlimit, westlimit longitude (or easting) of the right and left edges
uplimit, downlimit vertical extent, for volumes such as an airspace or an ocean layer
units, zunits the unit of the horizontal and vertical values
projection, name the coordinate system, and a human label for the region

In practice most records only need the four horizontal limits, a units statement and, if there is one, a name. The name component is plain text and does not have to match a gazetteer entry, although it is more useful when it does.

When units is left out, readers tend to assume signed decimal degrees on WGS 84, which is also the safest choice for new records. Stating it explicitly costs a few characters and removes the guesswork for anyone who harvests the record later. Southern latitudes and western longitudes take a minus sign, so the box for a stretch of coast near Sydney has negative north and south limits and positive east and west limits.

Where the scheme is attached

dcterms:Box describes the value, so it sits on the literal of dcterms:spatial (or its parent dcterms:coverage). In Turtle that means a typed literal, as in the example on this page. In RDF/XML the same thing is written with rdf:datatype="http://purl.org/dc/terms/Box" on the dcterms:spatial element. Older XML application profiles used an xsi:type="dcterms:Box" attribute for the same purpose, and many harvested records still carry that form.

A place name such as “Western Australia” is not a Box. If the record should also carry a named place, add a second dcterms:spatial statement with the name or a gazetteer URI, and if it is a country, a code from dcterms:ISO3166 is often the cleanest option.

Mistakes that break bounding boxes

Swapped edges are the most frequent problem: a northlimit smaller than the southlimit produces an empty or inverted rectangle that most spatial indexes silently drop. Mixed units are the second: projected metres from a national grid pasted next to units=signed decimal degrees will place a Swiss survey somewhere in the Atlantic.

Watch for these as well:

  • Commas instead of semicolons between components, which a strict parser reads as one long, broken value.
  • Degrees, minutes and seconds (33°52'S) in fields meant for decimals.
  • A point recorded as a box with identical north and south and identical east and west limits; dcterms:Point exists for that.
  • Spurious precision. Six decimal places imply centimetre accuracy that a scanned 1950s map sheet does not have.

Box, Point and other spatial descriptions

DCMI defines Box and Point as a pair, both from the same period of work on spatial metadata in the early 2000s. Point carries east, north and optional elevation; Box carries limits. Neither scheme does polygons, which is why projects that need real outlines tend to add GeoJSON or WKT in a separate field while keeping a Box for simple discovery.

Catalogers working from printed maps can usually take the four limits straight from the neatline coordinates printed in the corners of the sheet, converting them to decimal degrees once and recording the projection named in the map’s margin.

Example in RDF

@prefix dcterms: <http://purl.org/dc/terms/> .

<https://example.org/maps/coastal-survey-1998.tif>
    dcterms:title "Coastal survey sheet 14" ;
    dcterms:spatial "name=Survey area 14; northlimit=-33.80; southlimit=-34.15; westlimit=150.95; eastlimit=151.35; units=signed decimal degrees"^^dcterms:Box .

Questions about dcterms:Box

What is dcterms:Box used for?

It is the syntax encoding scheme for a bounding box: a rectangle (optionally with height limits) given as coordinates. It is typed onto a value of dcterms:spatial so software knows the string can be parsed into north, south, east and west limits instead of being read as free text.

Which components does a DCMI Box value contain?

The defined components are name, northlimit, eastlimit, southlimit, westlimit, uplimit, downlimit, units, zunits and projection. Each is written as name=value and the pairs are separated by semicolons. Only the four horizontal limits are needed for a usable box.

What is the difference between dcterms:Box and dcterms:Point?

Point records a single location (east, north and optional elevation), which suits a building, a station or a find spot. Box records an area with four edges, which suits a map sheet, a survey region or a dataset that covers territory.

Does the order of the components matter?

The DCMI Box specification does not require a fixed order, because every value carries its own label. Keeping one consistent order across a collection still helps, since it makes values easier to compare by eye and to validate with simple scripts.

How do I record a box that crosses the 180th meridian?

Write the westlimit as the western edge and the eastlimit as the eastern edge even when the western number is larger, for example westlimit=170 and eastlimit=-170. Check that the software consuming the record handles that case, because some map viewers assume west is always smaller.

More from DCMI classes and encoding schemes

All 10 in this group