The 3D Portrayal Services

The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal.

Example Layer

# Layer Type Area Request URL Client Demo
1 Building 3D Tiles Wuestenrot, DE 3DPS Request 3D Client
2 Building I3S Wuestenrot, DE 3DPS Request 3D Client
3 Building 3D Tiles Sejong, South Korea 3DPS Request 3D Client

Concept

The 3D contents are loaded to the clients using the 3DPS GetScene request according to the 3DPS standard.

Name and example a Optionality Definition and format

service=3DPS

Mandatory

Service type identifier

request=GetScene

Mandatory

Operation name

version=1.0

Mandatory

Standard version for operation

crs=epsg:4327

Mandatory

Identifier URI of primary CRS

boundingBox=0.0,0.0,0.0,10.0,10.0,50.0

Optional

Bounding box surrounding selected dataset, in available CRS

spatialSelection=cut

Optional

Method of selecting objects with BoundingBox

layers=layer1,layer2

Mandatory

Identifiers of layers to retrieve the data from, comma-separated list

styles=style1,style2

Optional

Identifier of service style to be used applied, comma-separated list

background=darkSky

Optional

Background identifier as string

lods=citygml:4

Optional

List of LODs requested for the layers, comma-separated list

lodSelection=equals_or_similar

Optional

Method for selecting LODs

overallStyles=photorealistic

Optional

Identifier(s) of desired overall scene style(s)

deliveryOptions=regroupGeometry

Optional

URIs: Names of the delivery options requested by the client, comma-sparated

exceptions=text/xml

Optional

Format of exceptions

offset=200000,200000,0

Optional

Offset vector which shall be applied to the scene, using the mode specified (if any)

format=model/x3d+xml

Mandatory

Format encoding of the scene

viewpoints=Overview,13.4097,52.5177,
220.0,13.4087,52.5202,120.0,100

Optional

Viewpoints as tuple values to be added by server, comma-separated list of string

a All parameter names are listed here using mostly lower case letters. However, any parameter name capitalization shall be allowed in KVP encoding. All example values depend on how a specific OWS specifies them.

Contact

Thunyathep Santhanavanich (JOE) PhD candidate
Faculty of Geomatics, Computer Science and Mathematics,
University of Applied Sciences Stuttgart, Schellingstr. 24, D-70174 Stuttgart
thunyathep.s@outlook.com