Table 1. Supported data formats
Format Decoder Encoder Notes Type File extensions

Esri Shapefile

x

Decoded through GdalModelDecoderGdalModelDecoderGdalModelDecoder

Vector features

*.shp

GeoPackage

x

x

OGC GeoPackage, decoded through GeoPackageModelDecoderGeoPackageModelDecoderGeoPackageModelDecoder, feature encoding through GeoPackageModelEncoderGeoPackageModelEncoderGeoPackageModelEncoder

Vector features, tile matrix sets of imagery and raster maps

*.gpkg

GeoTIFF

x

Decoded through GdalModelDecoderGdalModelDecoderGdalModelDecoder

Raster

*.tif, *.tiff

HSPC

x

Not applicable

Hexagon Smart Point Cloud

Point clouds

tree.hspc

OGC 3D Tiles

x

Not applicable

OGC 3D Tiles

3D meshes and point clouds

tileset.json

WMS

x

Not applicable

OGC Web Map Service

Raster

Not applicable

WMTS

x

Not applicable

OGC Web Map Tile Service

Raster

Not applicable

DTED

x

Digital Terrain Elevation Data

Raster

*.dt0, *.dt1, *.dt2, dmed

MBTiles

x

File format for storing tiled data in SQLite databases. MBTiles files with image tiles in JPG, PNG or WebP format are supported, as well as vector tiles.

MBTiles web services (TileJSON endpoints) are supported next to files.

Decoded through MbTilesModelDecoderMbTilesModelDecoderMbTilesModelDecoder

Vector, raster

*.mbtiles

Model decoders

For all formats supported in LuciadCPillar there is a model decoder available. The naming convention for the model decoders is: FormatModelDecoder, for example GeoPackageModelDecoderGeoPackageModelDecoderGeoPackageModelDecoder. For more information on a specific model decoder, see the API reference documentation.

Model encoders

For the GeoPackage format there is a model encoder available for feature models. The naming convention for the model encoders is: FormatModelEncoder, for example GeoPackageModelEncoderGeoPackageModelEncoderGeoPackageModelEncoder. For more information on a specific model encoder, see the API reference documentation.