MapFactor Forum

I was thrown by a routing that took me from Frankenmuth, MI to Kitchener, ON, by going south of the great lakes, crossing into Canada at Montreal, PQ and then west to Kitchener. That made no sense.

I finally found the problem was the Charge Road was not enabled. Charge Road was a term that I haven't seen used before, on other mapping programs or GPS.

Thanks

In my case, the only road that it must have considered to be a charge road, would have been the Bluewater Bridge, between Port Huron, MI and Sarnia, ON and the Ambassador Bridge, between Windsor and Detroit. Most programs seem to treat this as a Toll Road, since you pay a per use fee, EVERY time you use it.

There are pluses with the concept of Charge Road, vs Toll Road, once you understand what a Charge Road is. Some cases, you want to avoid toll roads, but you often have no choice when it comes to something like an International bridge. If you want to leave the country, you have to use it. No Choice, No discussion.

I'm looking for devices to allow you to set-up Toll Roads as an avoidance, only when the tolls exceed a specific limit. Would be nice, but impossible to set-up. In my case, my GPS allows me to create a Custom Avoidance, that allows me to avoid sections of road that I highlight. It's a pain to set-up, but if you pre-plan it can be very useful (and frugal).

Just note, that attributes charge/toll work correctly for example in Tom Tom data, but not in OpenStreetMap source. They are not distinguishable and for tag toll=yes are set both charge/toll attributes to be true in MCA file.

Congestion charge in London is used in Tom Tom maps. Is it defined also in OSM?

At first I wanted to complain that
http://www.openstreetmap.org/relation/3124618
is not polygon ... but maybe it would be enough to set the congestion charge bit only on the boundary??
I should read it first "is a toll-free circular primary route." and inside should be "type=toll" and here is the toll polygon:
http://www.openstreetmap.org/relation/3045928
... now just to implement it in data conversion.
thanks
   Martin

The first attempt is now integrated in the conversion process. There could be OSM problem in October 2014 data due to deletion of http://www.openstreetmap.org/way/227880171 (fixed by woodpeck_repair) near the planet dump release date ... we will see.
Martin