Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VectorNodes reference information #2

Open
beard7 opened this issue Nov 15, 2022 · 2 comments
Open

VectorNodes reference information #2

beard7 opened this issue Nov 15, 2022 · 2 comments
Assignees

Comments

@beard7
Copy link

beard7 commented Nov 15, 2022

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.

@poggs poggs self-assigned this Nov 15, 2022
@poggs
Copy link
Member

poggs commented Nov 15, 2022

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?

@beard7
Copy link
Author

beard7 commented Nov 15, 2022

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 free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants