Data Mappings: Multiple Representations
With the power of the SEDRIS DRM, data can be stored in a variety of different representations
In some cases, STF to CTDB can handle multiple representations
- For buildings it can understand <Areal Features>, <Point Features> and <Geometry Models>
However, it cannot possibly handle every representation
- For example roads could be stored as:
- <Linear Features> representing the route of each road with a <Property Value> to give the width.
- <Areal Features> representing the outline of the complete road, where width would have to be reasoned from the width of the <Areal Feature> itself.
- <Polygons> stitched into the terrain tagged as ECC_ROAD.
- etc�
- STF to CTDB can only handle <Linear Feature> representation
The set of data mappings described here documents which representations the STF to CTDB does handle
- An informal Transmittal Contents Requirement Specification for the STF to CTDB compiler.