To know more easily which neworks can be integrated in the, I suggest to create a doc with requirements foreach different type of networks (subway, train, light_rail)
It's can be a web page of the validator to improve visibility to our community
Create a doc about network requirements #84
Open
opened 2026年05月13日 22:21:05 +02:00 by jeanbaptisteC
·
2 comments
jeanbaptisteC
commented 2026年05月13日 22:21:05 +02:00
To know more easily which neworks can be integrated in the, I suggest to create a doc with requirements foreach different type of networks (subway, train, light_rail)
It's can be a web page of the validator to improve visibility to our community
jeanbaptisteC
commented 2026年05月25日 20:42:09 +02:00
Subway:
-
relation route_master
- having
type=route_master - having a
colourtag - having a
reftag - having a
nametag - contains route relations
- having
-
relation route
- having
type=route - having
type=subway - having a
colourtag - having a
reftag - having a
nametag - having a
networktag that match withnetworktag from the route_master relation - contains stop_positions
- having
public_transport=stop_positiontag - having
railway=stoporrailway=tram_stoptag - having
subway=yestag
- having
- contains platforms
- having
public_transport=platformtag - having
railway=platformor railway=platform_edgetag - having
subway=yestag - contains railway tracks
- having
railway=subwaytag
- having
- items should be order in the relations
- stop_position/platform
- tracks
- each stop positions and platforms present in the relation should be inside a stop_area relation
- having
public_transport=stop_areatag - having
type=public_transporttag - having
nametag - the stop_area relation should contains also a station
- having
public_transport=stationtag - having
railway=stationtag - having
station=subwayorrailway=halttag - having
subway=yestag - having a
nametag
- having
- having multiple stop_area relation for different route is possible but require to use a stop_area_group and include stop_area relations inside
- having
nametag - having
public_transport=stop_area_grouptag - having
type=public_transporttag
- having
- having
- having
Subway:
- relation route_master
- having `type=route_master`
- having a `colour` tag
- having a `ref` tag
- having a `name` tag
- contains route relations
- relation route
- having `type=route`
- having `type=subway`
- having a `colour` tag
- having a `ref` tag
- having a `name` tag
- having a `network` tag that match with `network` tag from the route_master relation
- contains stop_positions
- having `public_transport=stop_position` tag
- having `railway=stop` or `railway=tram_stop` tag
- having `subway=yes` tag
- contains platforms
- having `public_transport=platform` tag
- having `railway=platform` or railway=`platform_edge` tag
- having `subway=yes` tag
- contains railway tracks
- having `railway=subway` tag
- items should be order in the relations
- stop_position/platform
- tracks
- each stop positions and platforms present in the relation should be inside a stop_area relation
- having `public_transport=stop_area` tag
- having `type=public_transport` tag
- having `name` tag
- the stop_area relation should contains also a station
- having `public_transport=station` tag
- having `railway=station` tag
- having `station=subway` or `railway=halt` tag
- having `subway=yes` tag
- having a `name` tag
- having multiple stop_area relation for different route is possible but require to use a stop_area_group and include stop_area relations inside
- having `name` tag
- having `public_transport=stop_area_group` tag
- having `type=public_transport` tag
jeanbaptisteC
commented 2026年05月25日 20:45:13 +02:00
@Bovi887 review is appreciated to having a first valid version to know more easily which network can be integrated
I have planned to doing the same thing for light_rail and commuters train relations
Feel free to edit my comment or suggest a version in a different format
@Bovi887 review is appreciated to having a first valid version to know more easily which network can be integrated
I have planned to doing the same thing for light_rail and commuters train relations
Feel free to edit my comment or suggest a version in a different format
Sign in to join this conversation.
No Branch/Tag specified
Labels
Clear labels
bug
Something is not working
contribution welcome
Contributions are very welcome, get started here
duplicate
This issue or pull request already exists
enhancement
New feature
good first issue
Interested in contributing? Get started here.
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
transport data edit
upstream
Related to an upstream repository, already reported there
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
transport data edit
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".
No due date set.
Dependencies
No dependencies set.
Reference
comaps/subways#84
Loading...
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?