Profile - Position CRS

speccustomimplproposal

Profiles for positions stored in a reference system that differs from the storage CRS.

Scope

If the feature schema includes at least one geometry property with a variants declaration, one of two profiles can be used to select the representation of these positions in the response. With "crs-original", positions are represented as recorded: in their original reference system, identified by the stored verbatim CRS identifier, unaffected by the crs query parameter. This includes positions in reference systems that cannot be expressed as the CRS of the response, such as realizations that map to the same coordinate reference system or 1D vertical reference systems.

With "crs-requested" (the default), the position of the primary geometry property is returned in the requested CRS in all feature encodings; a feature whose position cannot be represented in the requested CRS (for example, a position in a 1D vertical reference system) is returned without a geometry.

The profile is supported by GML (the position element carries the original identifier as srsName, 1D positions are encoded with srsDimension="1") and by GeoJSON with the JSON-FG extensions (place carries the original position with the identifier in coordRefSys; for a 1D position, the vertical coordinate and the identifier appear in properties). Feature encodings that cannot represent positions in other reference systems (for example, plain GeoJSON) ignore the profile.

Configuration

Options

Name	Default	Description	Type	Since
buildingBlock		Always PROFILE_CRS.	string	v2.0
enabled	true	Enable the building block?	boolean	v2.0

This building block does not require or support any additional configuration files.

Examples

- buildingBlock: PROFILE_CRS
 enabled: true