Hello,
in the archive (september 2009) I saw that there were some discussion about
inter tile routing problems. I use version 1445 and have the same problem
when doing a routing in Mapsource over 4 interceptions. 3 interceptions
working fine.
Are there some news about that issue?
Another
Hi Stefan,
in the archive (september 2009) I saw that there were some discussion about
inter tile routing problems. I use version 1445 and have the same problem
when doing a routing in Mapsource over 4 interceptions. 3 interceptions
working fine.
Are there some news about that issue?
I
Hi Michael,
--ignore-osm-bounds
If you ignore the bounds, the ways don't end at the same coordinates.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
MB I haven't the faintest clue what could be the issue here so until we
MB get some hint as to what the problem could be, I'm ignoring it.
MB I simply don't have spare time to dream up possible reasons why
MB this problem exists.
Can't say I blame you, doesn't sound like an easy one to get to the
Mark Burton schreef:
There is a particular failure of inter-tile routing that we have seen
quite often which is that it fails to find a route when the source and
destination are in the same tile and the only (sensible) route is via
another tile. (If a sub-optimal route that only uses the
MB There is a particular failure of inter-tile routing that we have
MB seen quite often which is that it fails to find a route when the
MB source and destination are in the same tile and the only (sensible)
MB route is via another tile. (If a sub-optimal route that only uses
MB the source tile is
Hi Chris,
When I get a chance in the next couple of days, I'll have a play around with
some of the official Garmin maps and see if they can be made to exhibit the
same problem. If so then the limitation is most likely in the routing
algorithm
in MapSource and/or on the device. If that's
Using a recent GB tiled map on my eTrex, I have found that it performs
differently (better?) to mapsource with regard to the problem of not
routing across a boundary and back to the source tile.
An example route I tried used a road that snaked across a boundary.
Mapsource failed miserably in the
did some experiments in Mapsource and Garmin maps don't suffer from this
problem.found a place where the direction of the route defines which way
is chosen. makes perfect sense because right turns are faster and easier
than left turns.
Mapsource will even choose the longer way across the tile
Apollinaris Schoell wrote:
did some experiments in Mapsource and Garmin maps don't suffer from this
problem.found a place where the direction of the route defines which way
is chosen. makes perfect sense because right turns are faster and easier
than left turns.
Mapsource will even choose the
I bet you used --ignore-osm-bounds option on compiling!
Carlos Dávila wrote:
Yesterday I realized I can no longer calculate routes involving more
than one tile in Mapsource using my Spain map. I compile it daily using
latest svn and I don't know when the problem was introduced (it worked
Felix Hartmann escribió:
I bet you used --ignore-osm-bounds option on compiling!
You win. That was the origin of the problem. I remember having read
something about --ignore-osm-bounds affecting routing in the list or
somewhere else some time ago, but I didn't take care of it :-[ .
Cheers
12 matches
Mail list logo
