-
Notifications
You must be signed in to change notification settings - Fork 7
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
Control for attributes
parameter
#1
Comments
Hi Nils, thanks very much for the suggestions. Regarding the first point, just checking I'm correct that this is the I'll have a look at the |
Oops, so sorry, didn't see this one. You're right, it's not documented.. It basically calculates the ratio of actual isochrone area over the theoretically possible area one could reach if there were no roads (i.e. as the crow flies). That assumes a certain speed and is not actually modelled like the routing, just a plain circular "isochrone/equidistant" with constant mode speed. Hope you understood what I mean. We're rebuilding a bit of that currently, since these constant speeds were waaay too high (50 km/h for bike haha), so reachibility was ALWAYS < 0.2 or so, even in super accessible areas like central squares in cities. |
No problem at all Nils, really appreciate your feedback and input. Thanks very much for the clarification. Please could you let us know when you've finished updating this aspect? |
Hi @nilsnolde, just picking up on this one again whilst preparing the new version of the plugin to use the V2 API. I've implemented the |
Hm, shouldn't be, but you're right! I'll look into it real quick and might open an issue on our side. |
Thanks as always Nils for your fast response. Hope it's not a pain to fix! |
No worries:) I actually did fix that while fixing general issues with |
That's great, glad you've already fixed it! I'll handle it in the plugin so that if Thanks again Nils! |
…or a choice of: area, reach_factor and total_pop to be returned from the API. Previously area and total_pop were hard-coded. This was the suggestion from @nilsnolde in issue #1. Updated the documentation following this change and previous commit afdaaa6 which implemented the smoothing parameter, also suggested by @nilsnolde in #1.
Release v2.0.0 implements everything discussed here so closing this now. Nils, please feel free to add further comments regarding |
Might be of interest to include the
reachability
attribute to the isochrone output or alternatively add a control parameter for whichattributes
to get.Also, we have a new
smoothing
parameter. It's not really documented yet, but it's working. Here you can see some documentation on it inline. Its range is [0.0, 1.0] and it's a float.The text was updated successfully, but these errors were encountered: