TN - AirNode significantPoint

[sMorrone]

Change proposal description

This proposal derives from the need to align the TN TG to the endorsed change INSPIRE-MIF/application-schemas#61.
This change requires that a clarification note is added in the 'Geometry representation' section specifying that an AirNode is not required to be present 'where Transport Links connect or end' when its significantPoint attribute is set to 'false'.

Addressed TG

TN

Location

Issue faced

An AirNode is not necessarily placed at the end or start of a Transport Link when it is not used for navigation/ATS purposes.
Example: an AerodromeNode could either simply represent the aerodrome location (significantPoint = false) or act as transport node for connectivity (significantPoint = true).

Proposed solution

A clarification note is added in Section 5.3.1.6. Geometry representation specifying that an AirNode is not required to be present where Transport Links connect or end when it is not intended for navigation/ATS purposes i.e., when its significantPoint attribute is set to 'false'.

Pull request

Additional information

Impact on INSPIRE validator

INSPIRE-MIF/helpdesk-validator#113