-
Notifications
You must be signed in to change notification settings - Fork 3
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
LCID default scenario does not contain trips originating in the development zone #174
Comments
Update: seems people are correctly emanating from the Allerton Bywater site but the site boundary is not there. |
I've had a quick look, and it looks like all the site boundaries aren't showing - I am also getting the same issue as @Robinlovelace for lcid, and unsure what the root issue is, as it's not the case for any other sites . Ill check through the geojson to see if I see anything funky |
Heads-up, I think Dustin has identified the issue (updated A/B Street schema) and documented it here: a-b-street/abstr#29 We could mark this as a duplicate but good to have an issue open in the ActDev repo as that's where people will look. |
The missing study area polygon issue was fixed in You can confirm the LCID site boundary is showing up in the latest web build: I watched the LCID simulation (as of the 0.2.48 release) and saw trips coming from the new zone. So basically, this is fixed upstream, but we need to push a new actdev deployment. |
Great work, thanks Dustin! |
Not sure what is causing this but having just demonstrated https://actdev.cyipt.bike/abstreet/?--actdev=lcid&--cam=14.95/53.79136/-1.53469&--actdev_scenario=base I noticed that people are not starting their morning commutes in the development location but seemingly anywhere on the map. Any ideas @dabreegster or @natesheehan ? Will check for other areas. This is what I see (note: LCID is roughly in the centre of the map but the highest flows are not emanating from the site):
Also it seems the site boundary is no longer there.
The text was updated successfully, but these errors were encountered: