OGC API - Maps

A OGC API - Maps based on the current early specification draft, delivering partial functionality:

  • Collection listing

  • Styles per collection

  • Map and info support for single collection

Missing functionality at the time of writing, and known issues:

  • API definition

  • Maps specific metadata (e.g., scale ranges)

  • Support for multi-collection map representation

  • HTML representation of a map with OpenLayers is only partially functional

OGC API - Maps Implementation status

OGC API - Maps

Version

Implementation status

Part 1: Core

Draft

Implementation based on early specification draft.

Part 2: Partitioning

Draft

Implementation based on early specification draft.

Installing the GeoServer OGC API - Maps module

  1. Login, and navigate to About & Status > About GeoServer and check Build Information to determine the exact version of GeoServer you are running.

  2. Visit the website download page, change the Development tab, and locate the nightly release that corresponds to the GeoServer you are running.

    Follow the Community Modules link and download ogcapi-maps zip archive.

    The website lists active nightly builds to provide feedback to developers, you may also browse for earlier branches.

    Warning

    Verify that the version number in the filename corresponds to the version of GeoServer you are running (for example geoserver-3.0-SNAPSHOT-ogcapi-maps-plugin.zip).

  3. Extract the contents of the archive into the WEB-INF/lib directory in GeoServer.

  4. Restart GeoServer.

    On restart the services are listed at http://localhost:8080/geoserver

Configuration of OGC API - Maps module

The module is based on the GeoServer WMS one, follows the same configuration and exposes the same layers. As a significant difference, Maps does not have a concept of layer tree, so only individual layers and groups can be exposed.

Previous: OGC API - Tiles
Next: OGC API - Coverages