We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the lua-profile returns '120' as 'forward_priority', it becomes zero in the debug output.
I did put in a 'debug'-statement for a testcase.
When the profile is called with
highway = motorway oneway = both _direction = against access = yes speed = 120
the resulting object is:
forward_speed = 120 backward_speed = 120 forward = 0.008333333333333333 backward = 0.008333333333333333 canstop = true
Other tags and their results in this document
However, the route mysteriously fails. When trying a very synthetic testcase, it won't take the motorway but will make the detour for car.fast:
car.fast
(The motorway is the straight line, the detour are residentials)
When dumping the routerdb to geojson, the following data is obtained. testcase-motorway.osmcar.fast.geojson.txt
Note that _forward:factor is 0 for the motorway, but not for the residential area
The text was updated successfully, but these errors were encountered:
Testfiles can be found in the routing profiles repo
Sorry, something went wrong.
Note that this test works if the profile is patched to have 'forward:factor' 10 times larger
If this bug is resolved, the warning in AspectedRouting/ProfileTestSuite.cs (priority is not within range) should be removed
priority is not within range
Add check that priority is always between -100 and +100, see itinero/…
4689760
…routing2#30
No branches or pull requests
When the lua-profile returns '120' as 'forward_priority', it becomes zero in the debug output.
I did put in a 'debug'-statement for a testcase.
When the profile is called with
the resulting object is:
Other tags and their results in this document
However, the route mysteriously fails. When trying a very synthetic testcase, it won't take the motorway but will make the detour for
car.fast
:(The motorway is the straight line, the detour are residentials)
When dumping the routerdb to geojson, the following data is obtained.
testcase-motorway.osmcar.fast.geojson.txt
Note that _forward:factor is 0 for the motorway, but not for the residential area
The text was updated successfully, but these errors were encountered: