Sort EndDates

[KathiSchleidt]

For most date intervals, we've just been ignoring the end date, only the monitoring facility has been done correctly as follows:

• Create an additional field in db (date_fin_unknown in example below) with string "unknown" in the case where end position is empty
• Modify endPosition mapping as in the example below

<AttributeMapping>
	<targetAttribute>eposb:linkingTime/gml:TimePeriod/gml:endPosition</targetAttribute>
	<sourceExpression>
		<OCQL>date_fin</OCQL>
	</sourceExpression>
	<encodeIfEmpty>true</encodeIfEmpty>
	<ClientProperty>
		<name>indeterminatePosition</name>
		<value>date_fin_unknown</value>
	</ClientProperty>
</AttributeMapping>

[nmco]

What's the plan here @KathiSchleidt, this basicly just App-Schema mappings updating, right?

[KathiSchleidt]

@sgrellet: this is mapping cosmetics, up to you if I do this (will the system continue to be used?)
However, if I do, I must also modify the DB views accordingly, provide "unknown" in an additional column for the case where end-date is empty

[KathiSchleidt]

PS: not that relevant for the WFS3 output. In GML, this would provide an error (timePeriod without endPosition), but in JSON the endPosition is just not there...

[sgrellet]

mapping and views will be updated by @spifman when he has all the registries available. From latest discussions, should be available aorund the 26th .