Version Released What's New

View the detailed DataStore Api Documentation
as generated from the OpenAPI Specification 2.0 JSON Document. 2018.01.30
New read-only operations. The following Reference sub-properties can be accessed individually. 2016.06.27
Added endpoints for obtaining an FGDC-1998 compliant metadata representation of a Geospatial Reference.
See Download FGDC Documentation.
If the Reference was created from an FGDC metadata xml source, this method will attempt to return the original metadata merged with a subset of the latest attributes as managed in the web application itself.
If an updated metadata xml file has been linked to the Reference after its initial creation, the latest such xml document will be used as the source for the merge operation.
Finally, if no metadata xml document was used to create the Reference, a best attempt will be made to generate a new, simple metadata representation.
The /rest/MetadataDownload/{referenceCode} endpoint will return the generated metadata as an xml file.
The /rest/MetadataContent/{referenceCode} endpoint will return the generated metadata in the response. The default format is xml, but a json formatted response is also supported. 2016.06.06
Added endpoints for downloading files (holdings) linked to a Reference.
See Download File Documentation.
A http HEAD request can be submitted to get header information about the file, before downloading it.
A simple GET request will download the file itself. However, the endpoint supports range requests, which can be used to download the file in parts. This supports clients that offer pause/continue or parallel download.
Note how pre-conditions are also supported
  • If-Modified-Since (use Last-Modified header value)
  • If-Unmodified-Since (use Last-Modified header value)
  • If-Match (use ETag header value)
  • If-None-Match (use ETag header value)
  • If-Range (use ETag or Last-Modified header value; only when requesting a Range) 2016.04.15
Please note that the 'Children', 'Products', and 'ProjectAndRelatedProducts' of the Reference Profile are now 'ReferenceComposite' rows instead of 'ReferenceRow'. That means each row will have a potential sub-collection of Linked Resources and/or Units. Since this simply adds a nested collection to the previous model, it should not break any existing json or xml based object parsing. 2016.03.17
Our initial release of the new v4 read-only api.
In addition to simple 'GET' requests, several endpoints now support 'POST' for submitting complex search criteria or value lists that exceed url limits.
Endpoints supporting 'POST' include These endpoints, and a few others, also support the request to add any linked Units or Holdings to each item returned in the response set.
The additional data is requested using the alternate 'Composite' endpoints: