Thank you @VladimirAlexiev,
We have a specific use case where the DSOs need to specify whether the given coordinate is related to the top or bottom of a pole/tower.
Typically the geospatial information in the power industry is derived from:
measured : The information is measured according to a given standard.
calculated : The power line is regularity scanned by taking plain photograph and from the geospatial information is calculated.
estimated : Based on other measured or calculated values the data is estimated.
manual : Based on looking at the map and other sourced the data is entered manually.
With refrence to the above, If the pole has been deployed but it's height has not yet been accurately measured, the DSOs could either
Measure the coordinate with reference to the bottom of the pole(ground level), this coordinate would then be reported according to the standard
Estimate the coordinate with reference to the top of the pole by adding the height of the pole to the measured coordinate at the bottom of the pole. This coordinate would then NOT be reported according to the standard.
This means that to stay compliant with the standard the DSOs would report a coordinate with reference to the bottom of the pole while the pole has not yet been accurately measured. Once the pole has been accurately measured the DSOs would report a coordinate with reference to the top of the pole.
Could such top/bottom references also be specified using f.ex. a role qualifier, similarily to what you showed in your example?
@EmilieSkog Yes, you should definitely add such qualifiers.
We've seen a similar case in urban planning, where a building height could be reported eg:
FROM: ground level, or German standard height reference (water level at some canal)
TO: bottom edge of roof, or top edge of roof
In our case we combined these 2 factors into thesaurus URLs like <heightReference/from/1000/to/4300> (where the codes come from the German XPlanung standard) because there were only a few combinations.
Thank you @VladimirAlexiev, We have a specific use case where the DSOs need to specify whether the given coordinate is related to the top or bottom of a pole/tower.
With refrence to the above, If the pole has been deployed but it's height has not yet been accurately measured, the DSOs could either
This means that to stay compliant with the standard the DSOs would report a coordinate with reference to the bottom of the pole while the pole has not yet been accurately measured. Once the pole has been accurately measured the DSOs would report a coordinate with reference to the top of the pole.
Could such top/bottom references also be specified using f.ex. a role qualifier, similarily to what you showed in your example?
Originally posted by @EmilieSkog in https://github.com/3lbits/CIM4NoUtility/issues/340#issuecomment-2011890094
@EmilieSkog Yes, you should definitely add such qualifiers.
We've seen a similar case in urban planning, where a building height could be reported eg:
In our case we combined these 2 factors into thesaurus URLs like
<heightReference/from/1000/to/4300>(where the codes come from the German XPlanung standard) because there were only a few combinations.Originally posted by @VladimirAlexiev in https://github.com/3lbits/CIM4NoUtility/issues/340#issuecomment-2012339428