You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 15, 2024. It is now read-only.
The VectorLinks, VectorReferenceLines and VectorWaymarks are all self-explanatory and the properties of the shapefile contain all the required information: ELR, start and end mileages, track ID etc., making them extremely useful.
However, there's nothing in the properties of the VectorNodes shapefile that makes it possible to identify what the points represent. They appear to be a mix of signals, points, buffer-stops etc., but there's no way of knowing.
Would it be possible to add some identifying information into the layer properties or is there a separate source that could be cross-referenced.
Thank you.
The text was updated successfully, but these errors were encountered:
A point in these datasets does not necessarily represent a tangible element in reality. There are probably other data sets in existence which position signals on the infrastructure data here, but they may not be complete.
Have you tried submitting an FOI request to Network Rail asking for further sets of data?
I haven't tried a FOI request. That certainly sounds like a good idea.
Just out of interest then... how would you describe the VectorNodes layer? Does it just represent the points at which the polylines in VectorLinks join/end?
Thanks
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The VectorLinks, VectorReferenceLines and VectorWaymarks are all self-explanatory and the properties of the shapefile contain all the required information: ELR, start and end mileages, track ID etc., making them extremely useful.
However, there's nothing in the properties of the VectorNodes shapefile that makes it possible to identify what the points represent. They appear to be a mix of signals, points, buffer-stops etc., but there's no way of knowing.
Would it be possible to add some identifying information into the layer properties or is there a separate source that could be cross-referenced.
Thank you.
The text was updated successfully, but these errors were encountered: