Supported specifications and technologies

This is an overview. For constraints and limitations see the documentation of the ldproxy building blocks.

Web API Specifications

The following published standards and drafts of future standards for geospatial Web APIs or HTTP APIs are implemented in ldproxy:

• OGC API - Features - Part 1: Core, Version 1.0.1
• OGC API - Features - Part 2: Coordinate Reference Systems by Reference 1.0.1
• OGC API - Features - Part 3: Filtering, draft
• OGC API - Features - Part 4: Create, Replace, Update and Delete, draft
• OGC API - Tiles - Part 1: Core, Version 1.0.0
• OGC API - Styles, draft
• OGC API - Routes - Part 1: Core, draft
• OGC API - 3D GeoVolumes, draft
• Common Query Language (CQL2), draft

The functionality implemented in lproxy will in general differ from the current draft specifications since the drafts are changing.

Additionally, several ldproxy extensions are supported for which no official drafts are available at this time.

ldproxy is certified as an OGC reference implementation for "OGC API - Features - Part 1: Core" and "OGC API - Features - Part 2: Coordinate Reference Systems by Reference".

Formats

ldproxy supports the following formats that are supported by existing tools and libraries:

• General resources
  • JSON
  • HTML
  • XML (only for resources specified in OGC API Features)
• API definitions
  • OpenAPI 3.0.3 as JSON, YAML and HTML
• Features
  • GeoJSON
  • JSON-FG 0.1.1
  • HTML
  • GML 3.2.2
  • FlatGeobuf
  • CSV
  • CityJSON 1.0 and CityJSON 1.1
  • glTF 2.0
    • KHR_mesh_quantization
    • EXT_mesh_features
    • EXT_structural_metadata
    • CESIUM_primitive_outline
• 2D Tiles
  • Mapbox Vector Tiles 2.1
  • PNG (not for Feature Tile Providers)
  • JPEG (not for Feature Tile Providers)
  • WebP (not for Feature Tile Providers)
  • TIFF (not for Feature Tile Providers)
• 3D Tiles
  • 3D Tiles 1.1
• Tile Set metadata
  • OGC Two Dimensional Tile Matrix Set and Tile Set Metadata 2.0
  • TileJSON 3.0.0
• Tile Matrix Sets
  • OGC Two Dimensional Tile Matrix Set and Tile Set Metadata 2.0
• Style encodings (styles in most formats can be shared via OGC API Styles, but are not processed by ldproxy)
  • MapLibre Style Spec (styles can be used in HTML representations where MapLibre GL JS is the map client)
  • 3D Tiles Styling (styles can be used in HTML representations where CesiumJS is the map client)
  • OGC SLD 1.0
  • OGC SLD 1.1
  • QGIS QML
  • ArcGIS Desktop (lyr)
  • ArcGIS Pro (lyrx)
• Route Encodings
  • OGC Route Exchange Model, draft

HTML can be annotated with schema.org markup (schema:Place, schema:Dataset and schema:DataCatalog).

Data Providers

Features

All feature data in ldproxy is provided by feature providers, where each API has one provider. Two types of providers are supported:

• PostgreSQL databases (version 9.6 or later) with PostGIS (version 2.4 or later)
  • All tables of a provider must be in one database and one schema. Each table, except intermediate tables, must have a unique identifier column (primary key or with unique index). It is recommended to use integers for the identifiers for performance reasons.
• GeoPackage
• OGC Web Feature Services (WFS)
  • The WFS should support the query parameters COUNT and STARTINDEX in the GetFeature operation.

2D Tiles

All tiles are provided by a tile provider.

Three types of tile providers are supported:

• Features (provided by the same API)
• MBTiles
• HTTP (access via a xyz-URI-Template)

3D Tiles

All tiles are generated from a PostgreSQL feature provider with CityGML building features (LoD 1, LoD 2).