-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update traffic join to avoid 'traffic evaporating' #555
Comments
Source: output of this:
|
But the segment is totally missing from the CBD layer: Source: https://nptscot.github.io/#/clos/#14.21/55.97816/-3.2004 |
Great diagnosis of the issue, thanks Zhao! |
I think a better solution would be to update the LAD boundaries file. We could add a simple buffer but that would cause duplicates. I have an idea... |
Another issue with that solution: it will lead to duplicate IDs. A reason for using centroids is you only get 1 per region. |
I'm on the case: I think I can come up with a quick fix to the LADs. |
It is covered by the new region boundary introduced in #557: Source:
|
Should be fixed upstream in nptscot/osmactive#66 |
Fixed in #550 |
There are small anomalies popping up e.g.:
https://osm.org/go/evfLeWTk?m=
It appears if the traffic is evaporating between these two high-flow section. There were a couple of other examples of this that occur if you need me to send them across too.
The text was updated successfully, but these errors were encountered: