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

Node missing shst_node_id and osm_node_id #153

Open
yueshuaing opened this issue Feb 7, 2024 · 0 comments
Open

Node missing shst_node_id and osm_node_id #153

yueshuaing opened this issue Feb 7, 2024 · 0 comments
Labels
MetCouncil Things for MetCouncil

Comments

@yueshuaing
Copy link
Member

In Lasso, during the process of converting GTFS shape to a list of node in cube format, the roadway network is joined to the shapes based on osm_node_id and shst_node_id to get the model_node_id for each node in GTFS shapes. Typically, buses are routed on the base network where all nodes have unique osm_node_id and shst_node_id.
However, in the Metcouncil workflow, we did rerouting on the built roadway network where newly added nodes via project cards lack osm_node_id and shst_node_id. When the code links the roadway network to shapes, it results in null values in shape_model_node_id for shapes using these new added nodes.
As a temporary solution, we divided the shapes data frame into two parts: one containing shapes missing shape_model_node_id, and the other containing shapes with shape_model_node_id. We then performed the joining process only for the former part, while skipping it for the latter. Finally, we combine these two parts to create a new shape data frame.

@yueshuaing yueshuaing added the MetCouncil Things for MetCouncil label Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MetCouncil Things for MetCouncil
Projects
None yet
Development

No branches or pull requests

1 participant