tsne / monav

Automatically exported from code.google.com/p/monav
0 stars 0 forks source link

Doesn't route via barrier=toll_booth #31

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hello :)
During my experiments, I found that MoNav doesn't route through _any_ barrier=* 
node. This is wrong, since there is at least barrier=toll_booth which is 
routable (with a fee, usually).

It would be best to add an option to the client (like: "Avoid paid routes?") 
but, for the moment, I've made a patch making it route through toll_booths.

I'll include this patch in my upcoming Debian package ;) (which is quite ready, 
I must say).

Thanks for your work on MoNav! :)

Original issue reported on code.google.com by d.pale...@gmail.com on 11 Jan 2011 at 12:20

Attachments:

GoogleCodeExporter commented 9 years ago
According to http://wiki.openstreetmap.org/wiki/Key:barrier a barrier has to be 
tagged with the correct access tag to allow passage. The implied value is 
"access=no", meaning no access very anyone.

At the moment I would tend to forbid routing through a toll booths unless it is 
tagged correctly.

What is your opinion on this?

Original comment by veaac.fd...@gmail.com on 11 Jan 2011 at 12:27

GoogleCodeExporter commented 9 years ago
I'd say that barrier=toll_booth is an exception to this :)

The default "access=no" (when no access= specified) might be ok for other kinds 
of barriers, but a toll booth is usually a "access=fee" (ok, it doesn't exist, 
but the meaning is that one). That's why I was referring to the hypothetical 
switch "Avoid paid routes" ;)

If toll_booths were access=no by default, wrong routes would be planned.
To say, from Catania to Messina (Sicily), instead of taking the motorway, it 
would follow the motorway up to the first toll_booth, exiting it right before 
the barrier, and then following the nearby primary for ~80km. This is not the 
"ideal" route ;)

Original comment by d.pale...@gmail.com on 11 Jan 2011 at 3:30

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
See the attached images: a route from right before to right after a 
barrier=toll_booth, on an Italian motorway.

The first one is with your current code -- see the absurd route it takes ;)
The second one is with the patch applied.

Thank you,
David

Original comment by d.pale...@gmail.com on 11 Jan 2011 at 4:05

Attachments:

GoogleCodeExporter commented 9 years ago
In that case I would suggest adding a node modificator to the speed profile for 
barrier=toll_booth that sets access=yes. That would require no modifications to 
the code.

However, this is only possible in the SVN version. When packaging 0.2 it might 
be better to add an option to the OSMImporter's setting dialog. I will look 
into this during the weekend, also back-porting a a fix for the OSMImporter.

Original comment by veaac.fd...@gmail.com on 11 Jan 2011 at 4:15

GoogleCodeExporter commented 9 years ago
Ah, no need to :)
I'm packaging revision 405 anyway now ;)

Original comment by d.pale...@gmail.com on 11 Jan 2011 at 4:34

GoogleCodeExporter commented 9 years ago

Original comment by veaac.fd...@gmail.com on 11 Jan 2011 at 8:46

GoogleCodeExporter commented 9 years ago
Hmm, was this bug already fixed then?

Original comment by timo.lin...@gmail.com on 21 Jul 2011 at 6:09

GoogleCodeExporter commented 9 years ago
Yeah, you could say so. You can now create speed profiles that can either 
ignore toll booths or not. The official packages allow routing through toll 
booths.

Original comment by veaac.fd...@gmail.com on 22 Jul 2011 at 10:47