Closed bjtaylor1 closed 10 years ago
aa - it's because it seemingly now has to set "way.forward_speed" and "way.backward_speed" as well as just (or instead of) "way.speed".
What is way.backward_speed used for? Should it always be the same as way.forward_speed? Is way.speed still needed?
Is it possible to get notifications of things that might break an existing lua script?
AFAIK backward_speed is used for ways that can be traveled in both directions, but has different speed limits for each direction. See for example the specification on maxspeed in the OSM wiki "maxspeed:forward" vs. "maxspeed:backward"
As far as notifications go, please remember develop is the development branch. Seriously, it is a very bad idea to use it if you have any serious concerns of stability and backward compatibility. If the profile API changes, that will be probably mentioned in the release notes of the new version.
yep, sure - cheers.
A couple of my luas are not working on the develop branch but they work fine on the master branch. (i could just use master but am conscious to keep ahead of any issues for when develop gets merged into master).
using this lua:
then osrm-extract returns:
and with this lua
I get:
lib is present and contains access.lua, whitelist.lua which is:
and blacklist.lua which is:
the develop branch works fine with car.lua and the above profiles work fine with the master branch, so it appears to be something that has changed in the develop branch that isn't in master yet that the above luas have failed to keep pace with so I'm just wondering if you can suggest what it could be?