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
Make school layer rnet consistent with commute layer #704
Comments
@AnnaGoodman1 yes, as discussed, I'm proposing to provide all routes intersecting with each region in the I suggest that re re-name this issue 're-do regional rnets for schools', to make them consistent - not a priority issue but worth doing IMO. Sound reasonable? Thanks for raising this, and good point from a documentation + communication perspective. |
yes fine. and to double check, you will do a hard clip of each region at boundaries to avoid the double counting issues? |
There are 2 methodologies to prevent double counting:
The first is simpler so yes, going with that. Thanks for double checking and updating the issue. Not a priority ATM but definitely worth doing. |
@Robinlovelace , Remembering about this issue, in the context of adding a new schools go Cambridge scenario. How about
|
Sounds good @AnnaGoodman1, looking forward to Go Cambridge! |
not 100% consistent still, but good enough and this can close |
@Robinlovelace great to see all this progress on nat build...
My understanding of what you did for the rnet school layer is "the Route Network (LSOA, clickable) and the Route Network (LSOA, image) are built from all origin-destination fast routes within the region."
But am I right that for the commuting layer you are planning to do something different, namely build the route network from all flows starting or ending in the region? It doesn't seem ideal to do it differently for the two layers... though not the end of the world I guess...
The text was updated successfully, but these errors were encountered: