Some projects coming up involve paths or journeys that can be represented by LineStrings, but in order to be usefully displayed, will need to allow for directionality. The plan is as follows:
The TEI <location> element, which is currently only acted on if it has @type="GeoJSON", will have an optional @subtype="directional", which would be constrained by Schematron such that if the child <geo> element's geometry type is not "LineString", an error would be raised.
Where both these conditions pertain, the resulting GeoJSON for the feature will be assigned a boolean property "directional" set to true.
Where a feature has this property, a distinct style will be used to render it, incorporating arrows and/or animated rendering of the line.
The directionality will be assumed to be that which is inherent in the coordinate sequence.
Some projects coming up involve paths or journeys that can be represented by LineStrings, but in order to be usefully displayed, will need to allow for directionality. The plan is as follows:
The TEI
<location>
element, which is currently only acted on if it has@type="GeoJSON"
, will have an optional@subtype="directional"
, which would be constrained by Schematron such that if the child<geo>
element's geometry type is not "LineString", an error would be raised.Where both these conditions pertain, the resulting GeoJSON for the feature will be assigned a boolean property "directional" set to true.
Where a feature has this property, a distinct style will be used to render it, incorporating arrows and/or animated rendering of the line.
The directionality will be assumed to be that which is inherent in the coordinate sequence.