OGC Services

Create and publish following OGC services from the platform:

An OGC Web Map Service (WMS) returns static maps, rendered as images. The WMS specification defines a standard web service interface for the retrieval of maps of geographical data over the Internet. In general, a WMS is accessed by a client application that provides the user with interactive controls.

An OGC Web Map Tile Service (WMTS) serves digital maps in the form of predefined image tiles. The OGC WMTS specification standardizes how a WMTS server publishes the available images, as well as how the images are exchanged between a WMTS server and a WMTS client.

A OGC Web Feature Service (WFS) service client allows you to insert, update, delete, query and discover geographic features on an OGC server. WFS delivers GML representations of simple geospatial features in response to queries from HTTP clients. Clients access geographic feature data through WFS by submitting a request for just those features that are needed for an application.

The OGC WFS specification defines a standard interface for querying and manipulating geographic data. Queries can be formulated based on various spatial and non-spatial constraints, as defined by the OGC Filter specification.

A WFS provides geographic information in a rich format, without any prior interpretation or rendering, and with full georeferencing. This contrasts with, for instance, the WMS interface, which renders maps on the server side and returns simple images to the client. The default exchange format for geographic features is GML, another OGC standard.

The OGC 3D Tiles protocol is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds from a server to a client. It defines a hierarchical data structure and a set of tile formats which deliver renderable content.

HxDR supports creation and streaming of 3D tiles that contain a payload with:

• Point cloud data (the PNTS format)
• Reality meshes (the B3DM or Batched 3D Model format)

The OGC 3D Tiles format describes the structure of a 3D tile hierarchy. It consists of:

A metadata format that describes the 3D scene. It is encoded as JSON, and is typically named tileset.json. It can link to other tileset.json files or data files. The data files containing the tiles. Each tile contains a payload. In LuciadLightspeed, the payload consists of either a point cloud in PNTS or a textured 3D mesh in a Batched 3D Model (B3DM). For the encoding of the mesh data itself, the OGC 3D Tiles specification uses glTF. For more information about glTF, see https://www.khronos.org/gltf/ (opens in a new tab). Each tile in a tileset can also contain metadata such as:

• A bounding volume.
• The geometric error, which represents the visual error incurred by displaying a parent tile instead of its (more detailed) children.
• A list of child tiles.

The HxDR platform supports LTS for serving elevation coverages.

A Luciad Tile Service (LTS) allows you to efficiently serve elevation data, because it offers that data in a hierarchical tile structure, called a coverage. Because an LTS service serves only LuciadFusion coverages, though, you must pre-process the elevation data into such a coverage first. HxDR offers creation and streaming of elevation coverages.

What data can you add to an LTS service? (opens in a new tab)

Related Pages

GraphQL API reference

mutation TriggerProcessingV2 {
  triggerProcessingV2(
    params: {
      groupedAssetId: "[groupedAssetId]"
      outputFormat: "[outputFormat]"
      processingPipelineName: "[processingPipelineName]"
    }
  ) {
    ... on TriggerProcessingOutput {
      success
    }
  }
}

To successfully execute a request on HxDR GraphQL playground, See following :

JS-SDK reference

• OGC Services

  OGC Services