bugfix: parameters not passed #51

JamesSaxon · 2025-05-19T11:07:43Z

@jkoschinsky copied this issue to an old one:

I am a Masters Student in Geoinformatics from Hamburg, Germany and i am currently writing my thesis. My broad topic is the influence of demographic change in germanys on the accessibility of doctors in the metropolitan region of Hamburg. In Germany, more people retire than young people come into the system → supply decreases while demand increases.

For the calculation of TravelTimes i used “r5py” and for the accessibility assessment i am using your very helpful (!) Python module “Access”.

In Germany, global PPR values are different from those in the US, and they also vary based on the type of physician that one wants to evaluate the accessibility to.

When i tried to alter these values, i found that nothing was happening at all.

But then i noticed, that the rho-parameter is not passed into the raam.raam-method! To fix that i had to modify the code a little to alter the PPR ("half_life" is mossing too).

Before, it simply ignored the users input into Access.raam() where the function is called:

It took me a while to understand that i was not misunderstanding the calculation, but instead my input was simply ignored.

So if a future update is planned other users would likely thank you for this tiny adjustment! :)

JamesSaxon mentioned this issue May 19, 2025

Replace old travel times with OpenTimes #50

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

bugfix: parameters not passed #51

bugfix: parameters not passed #51

bugfix: parameters not passed #51

bugfix: parameters not passed #51

Comments

Uh oh!