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

Make school layer rnet consistent with commute layer #704

Closed
AnnaGoodman1 opened this issue Apr 4, 2019 · 6 comments
Closed

Make school layer rnet consistent with commute layer #704

AnnaGoodman1 opened this issue Apr 4, 2019 · 6 comments

Comments

@AnnaGoodman1
Copy link
Contributor

@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...

@Robinlovelace
Copy link
Member

@AnnaGoodman1 yes, as discussed, I'm proposing to provide all routes intersecting with each region in the rnet_full files for the commute layer. This is better from the perspective of encouraging joined-up, strategic networks.

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.

@AnnaGoodman1 AnnaGoodman1 changed the title Commuting and school layer not consistent on rnet? Make school layer rnet consistent with commute layer Apr 4, 2019
@AnnaGoodman1
Copy link
Contributor Author

yes fine. and to double check, you will do a hard clip of each region at boundaries to avoid the double counting issues?

@Robinlovelace
Copy link
Member

There are 2 methodologies to prevent double counting:

  1. Do a 'hard clip' (aka an intersection, with st_intersection) for each region.
  2. Combine all the 'internal route networks' and then add the route network resulting from all routes that intersect with the region boundaries.

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.

@AnnaGoodman1
Copy link
Contributor Author

@Robinlovelace , Remembering about this issue, in the context of adding a new schools go Cambridge scenario. How about

  1. I confirm with DfT they are happy with the scenario
  2. I create the go Cambridge scenario, and all associated files except rnet and raster
  3. you create new rnets + rasters for all school scenarios, this time using a method comparable to the commute layer. I think it does ideally need to be all scenarios recreated, otherwise different scenarios within the same layer will be using slightly different methods...

@Robinlovelace
Copy link
Member

Sounds good @AnnaGoodman1, looking forward to Go Cambridge!

@AnnaGoodman1
Copy link
Contributor Author

not 100% consistent still, but good enough and this can close

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