Detail
Definition
A Detail models the presence, location and extent of a physical object. Recognition of the feature in a map is heavily dependent upon the spatial context and cognitive recognition. (Illustration)
Feature Structure
- Detail objects are Feature objects
- Detail objects MUST have an
"id"
member with aFEATURE-ID
value - Detail objects MUST have a
"feature_type"
member with the value"detail"
- Detail objects MUST have a
"geometry"
member with aLINEAL
value
Property Keys
Property | Type | Description |
---|---|---|
level_id |
LEVEL-ID |
Unique identifier of the Level the Detail possesses a spatial relationship with |
Example
{
"id": "11111111-1111-1111-1111-111111111111",
"type": "Feature",
"feature_type": "detail",
"geometry": {
"type": "LineString",
"coordinates": [
[100.0, 0.0],
[101.0, 1.0]
]
},
"properties": {
"level_id": "22222222-2222-2222-2222-222222222222"
}
}
Geometry Capturing Rules
- The Venue Organization is responsible for establishing the scope and purpose of a Detail. They are not defined by IMDF. When deciding the scope of the map data requirements, a Venue Organization SHOULD consider:
- Venue Organizational (internal) needs
- General map purpose
- The use case model supported by the map application
- The value that is derived through augmentation of the map with Details
- Map data context, map scale and the relevance of a Detail at each of the viewable map-scales
- The expected level of interaction between a pedestrian and the physical object, and the degree to which the map application can enrich that "experience" through the presentation of these modeled objects
- Map aesthetic quality considerations