| Re: [railML2] Adding a new element informationArea to ocp [message #2781 is a reply to message #2777] |
Thu, 01 July 2021 23:52   |
Thomas Nygreen
Messages: 68
Registered: March 2008
|
Member |
|
|
Dear all,
If merging the two area approaches, then <genericArea> seems like a good name suggestion. If we were to keep them separate, I suggest <trackArea> for the type defined by positions on tracks and maybe something like <geographicArea> for the type defined by geographic coordinates. When joining the two, it is important to make sure that the added flexibility has a benefit and does not only end up being a burden to the consumers of the files. Continuing on that note, I would suggest skipping the rectangle definition altogether, as it is just a special case of a polygon.
Following Torben's train of thoughts, how generic should we make this element? Possible properties include (at least):
- The usuals: id, code, name, description
- designator
- list of references to limiting elements (defining the borders of the area in the track network)
- geographic coordinates
- ocp reference (or vice versa: the ocps can reference to its areas by id)
- zip code or other external area codes or area names
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
