Inconsistency between two realisations of the same location

Submitted by Loïc Blaive on Wednesday, 21 January, 2015 - 23:58
Issue ID
182
Component
Documentation
Category
Bug report
Priority
Normal
Assigned
Status
Needs work
Source
CEN
Description

Issue raised by UK during the stage "TC comment" of CEN TS 16157-2:
Comment: "Clarifying meaning of "without being exclusive". What is the interpretation if two methods are used to generate an irresolvable location?"

Proposal: woud it be better to make this an excusive choice?

14.00 Normal 0 21 false false false FR X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tableau Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif"; mso-fareast-language:EN-US;} 14.00 Clarify meaning of "without being exclusive" – what is the interpretation if two methods are used that generate an irresolvable location?"
Proposal: 14.00 Would it be better to make this an exclusive choice? Normal 0 21 false false false FR X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tableau Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} Normal 0 21 false false false FR X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Tableau Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";} -->

Found Version
{"changeLogs":[{"date":1527782122647,"componentOLD":"- Select a value -","component":"Documentation","categoryOLD":"- Select a value -","category":"Bug report","priorityOLD":"- None -","priority":"Normal","assignedOLD":"","assigned":"Loïc Blaive (23)","statusOLD":"- None -","status":"Needs work"},{"date":1537266893481}]}

Posted by Loïc Blaive on March 26, 2024 Permalink

Discussion in CEN TC278 WG8: This comment is relevant but cannot be accepted as such. After discussion it is considered such restriction does not appear to tackle other requests, as they need to consider the Linear class as an open container to receive any kind of linear locations. The raised issue has to be solved outside the present Technical Specification.

Posted by iancornwell on May 26, 2023 Permalink

Loic documented the decision to add to comment and user guide.
This applies to Linear, Point, and Area. New text has been added to the UML comment about aggregated instances on the diagrams for each of those 3 classes.
The issue is left unresolved because of the documented suggestion to update the user guide: "Beside the added note in the data model some guidance should be provided advice to users and developers in the Users’ Guide. ... Possible text: “Attention is drawn on the necessity to ensure the different location referencing realisation must be consistent by picturing the same coded geographic feature”."