| [railVIVID 2.1] Visualisation issue [message #3754] |
Wed, 22 October 2025 21:25  |
Mathias Vanden Auweele
Messages: 90 Registered: February 2025 Location: Brussels
|
Member |
|
|
Hello,
I am trying to visualise a railml 3.3 file in railVIVID 2.1.0-beta1. The file contains among other elements, those that are required by railvivid for visualisation, according to the documentation v1.6:
Tracks
Operationalcontrolpoints (OperationalPoints in railML 3.3)
Levelcrossings
Signals
The method of geometric positioning is RTM, depending on the element:
areaLocation/geometricCoordinateBegin
areaLocation/geometricCoordinateEnd
linearLocation/geometricCoordinateBegin
linearLocation/geometricCoordinateEnd
(there is a typo in the documentation as it states linearLocation/geometricCoordinateEnd two times)
Note: we do not use gmlLocation
Here is an example of a track element:
<track id="_track_173daf21-d681-464d-a290-b4ac7ca0d5ec" type="mainTrack" infrastructureManagerRef="_im01">
<name name="1" language="en"/>
<isValid from="2019-01-01"/>
<linearLocation id="_linearlocation_173daf21-d681-464d-a290-b4ac7ca0d5ec__track_173daf21-d681-464d-a290-b4ac7ca0d5ec" applicationDirection="both">
<associatedNetElement netElementRef="_netelement_1b975e4c-b7ee-4386-b8b2-425e1b24e386_0.0" intrinsicCoordBegin="0.0" intrinsicCoordEnd="1.0">
<geometricCoordinateBegin x="660598.754" y="6677336.04" z="144.514" positioningSystemRef="_gps01"/>
<geometricCoordinateEnd x="665430.857" y="6676522.117" z="149.134" positioningSystemRef="_gps01"/>
</associatedNetElement>
</linearLocation>
<designator register="BaneData" entry="KO-SPO-001181"/>
<elementState value="operational">
<validity>
<period from="2019-01-01T00:00:00"/>
</validity>
</elementState>
<length value="5659.5" type="physical" validForDirection="both"/>
</track>
The error message in railVIVID is: "Data for visualization of infrastructure was not found".
I'm not at liberty to share the file in the forum but I could send it privately over mail.
Are we missing something?
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
| Re: [railVIVID 2.1] Visualisation issue [message #3755 is a reply to message #3754] |
Wed, 22 October 2025 21:58   |
Mathias Vanden Auweele
Messages: 90 Registered: February 2025 Location: Brussels
|
Member |
|
|
Ah I overlooked a part of the documentation where it is stated that only EPSG 4326 is supported. So that is likely the issue. Some tips: a custom warning when no geometric positioning system with epsg 4326 is provided. Or maybe just convert the coordinates on the fly?
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
| Re: [railVIVID 2.1] Visualisation issue [message #3757 is a reply to message #3755] |
Thu, 23 October 2025 13:42   |
Mathias Vanden Auweele
Messages: 90 Registered: February 2025 Location: Brussels
|
Member |
|
|
I have added the EPSG 4326 coordinates to the railML file, but unfortunately the visualisation in railVIVD is still not working
<positioning>
<geometricPositioningSystems>
<geometricPositioningSystem id="_gps02" crsDefinition="EPSG:4326">
<name name="EPSG:4326 - WGS 84" language="en"/>
<isValid from="2000-01-01"/>
</geometricPositioningSystem>
<geometricPositioningSystem id="_gps01" crsDefinition="EPSG:25832">
<name name="EPSG:25832 - ETRS89 / UTM zone 32N" language="en"/>
<isValid from="2000-01-01"/>
</geometricPositioningSystem>
...
<netElement id="_netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751">
<elementCollectionUnordered id="_netelement_element_collection_unordered__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751">
<elementPart ref="_netelement_0122bc2e-db00-4c34-9f90-8b4d15a267ea_0.0"/>
</elementCollectionUnordered>
<associatedPositioningSystem id="_associated_positioning_system_gps01_meso__netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751" positioningSystemRef="_gps01">
<intrinsicCoordinate id="_intrinsic_coordinate_geometric_meso__netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751_0" intrinsicCoord="0">
<geometricCoordinate x="622675.874" y="6648836.979" z="108.236"/>
</intrinsicCoordinate>
</associatedPositioningSystem>
<associatedPositioningSystem id="_associated_positioning_system_gps02_netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751" positioningSystemRef="_gps02">
<intrinsicCoordinate id="_intrinsic_coordinate_geometric_gps02_netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751_0" intrinsicCoord="0">
<geometricCoordinate x="59.958601" y="11.196897" z="108.236"/>
</intrinsicCoordinate>
</associatedPositioningSystem>
<associatedPositioningSystem id="_associated_positioning_system_lps01_meso__netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751" positioningSystemRef="_lps01">
<intrinsicCoordinate id="_intrinsic_coordinate_linear_meso__netelement_meso__line_section_50eb2ec8-cf8c-4e29-b60c-518430448751_0" intrinsicCoord="0">
<linearCoordinate measure="33470.0"/>
</intrinsicCoordinate>
</associatedPositioningSystem>
</netElement>
...
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
[Updated on: Thu, 23 October 2025 13:43] Report message to a moderator
|
|
|
|
|
|
| Re: [railVIVID 2.1] Visualisation issue [message #3804 is a reply to message #3760] |
Tue, 02 December 2025 13:08   |
Marharyta Vyskarka
Messages: 22 Registered: April 2025
|
Junior Member |
|
|
Hello Mathias, sorry for the late reply and thank you so much for giving your feedback and sending us your file for evaluation.
railVIVID did have an issue with visualization of operational points in your file, which will be fixed in the next available version. As for the coordinate systems and their visualization, we visualize only the WGS84 system (EPSG 4326 and 4979), as the conversion of coordinates would require an additional solution which isn't easily available, and we do not interpolate the information taken from the net elements.
From what I have seen, your file does specify two different positioning systems, but actual functional infrastructure elements only seem to refer to the one that isn't in WGS84. In case if you were to provide multiple positioning systems in the file, and add functional infrastructure elements that refer to one in WGS84, it should still visualize such elements even when other systems are provided. As for what is currently visualized in the file, the operational points with GML coordinates are now visualized, as the issue with that has been fixed
Marharyta Vyskarka – Software Developer
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|