Re: [mkgmap-dev] errors in routing
garvan.m...@online.com.kh wrote: Quoting Mark Burton ma...@ordern.com: Should now be fixed. Err, that's only for OSM input. For Polish input it's not fixed - you have to fix your data instead. Just make sure that no road is longer than 25Km between nodes. If necessary, add extra nodes. I don't know what the distance constraint is here but with your sample data, I limited the length of the way to 25Km and the problem went away. Cheers, Mark Thanks for your work on this, I will test it on the full map at lunch time or tonight. The problem is most evident when highways are added to otherwise blank sections of the map. I checked the entire map of the Netherlands yesterday to understand why others had not reported the problem and I found that all the road segments are short, so the problem did not show up. I may be able to use mkgmap to fix my road data automatically in a once-off conversion, mp-osm-img-mp. I will need to check each step to make sure nothing is lost. I tested the update on a full map, and it is working well. Thanks Garvan ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in routing
Hi Garvan, Should now be fixed. Cheers, Mark ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in routing
Should now be fixed. Err, that's only for OSM input. For Polish input it's not fixed - you have to fix your data instead. Just make sure that no road is longer than 25Km between nodes. If necessary, add extra nodes. I don't know what the distance constraint is here but with your sample data, I limited the length of the way to 25Km and the problem went away. Cheers, Mark ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in routing
Quoting Mark Burton ma...@ordern.com: Should now be fixed. Err, that's only for OSM input. For Polish input it's not fixed - you have to fix your data instead. Just make sure that no road is longer than 25Km between nodes. If necessary, add extra nodes. I don't know what the distance constraint is here but with your sample data, I limited the length of the way to 25Km and the problem went away. Cheers, Mark Thanks for your work on this, I will test it on the full map at lunch time or tonight. The problem is most evident when highways are added to otherwise blank sections of the map. I checked the entire map of the Netherlands yesterday to understand why others had not reported the problem and I found that all the road segments are short, so the problem did not show up. I may be able to use mkgmap to fix my road data automatically in a once-off conversion, mp-osm-img-mp. I will need to check each step to make sure nothing is lost. Garvan ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] errors in routing
Hi, Using polish format as input, I get routing errors on roads that have been split by mkgmap. The errors do not show up on all roads split, but they show up on most. The map will not route onto the split road. From what I can see the roads are being split because they exceed the maximum number of points in a line (250). I will test OSM data to see if it has the same problem, but I assume it would have been reported. I guess not many are using polish format input. Garvan ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in routing
On Aug 1, 2009, at 10:13, Garvan maew wrote:
I re-tested a sample I posted before with routing problems, except
this time I converted the data to OSM format first, and it has the
same problem with routing as I noted in a larger map, and as I
explained above.
In the attached sample, snip.osm, if is not possible to route from
N13.10744 E100.92402
To
N13.09385 E100.91529
Without jumping all over the place (or any points points on these
roads).
I did a quick test on a map extract of Asia which I had previously
compiled. I noted no routing errors between these points.
One thing I found suspicious is that you are routing over a motorway
with only one lane. The default style automatically adds a oneway
attribute to all motorways. Could this be related to your routing
problem?
You may wish to try a style file with the add oneway statement
removed from the following line:
highway=motorway {add oneway = yes; add bicycle = no; add foot = no }
[0x01 road_class=4 road_speed=6 resolution 12]
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] errors in routing
Clinton Gladstone wrote:
On Aug 1, 2009, at 10:13, Garvan maew wrote:
I re-tested a sample I posted before with routing problems, except
this time I converted the data to OSM format first, and it has the
same problem with routing as I noted in a larger map, and as I
explained above.
In the attached sample, snip.osm, if is not possible to route from
N13.10744 E100.92402
To
N13.09385 E100.91529
Without jumping all over the place (or any points points on these
roads).
I did a quick test on a map extract of Asia which I had previously
compiled. I noted no routing errors between these points.
One thing I found suspicious is that you are routing over a motorway
with only one lane. The default style automatically adds a oneway
attribute to all motorways. Could this be related to your routing
problem?
You may wish to try a style file with the add oneway statement
removed from the following line:
highway=motorway {add oneway = yes; add bicycle = no; add foot = no }
[0x01 road_class=4 road_speed=6 resolution 12]
Thanks for the tip about highways being one way, and for taking the time
to look at the issue. I normally use polish format so I did not think
about the styles. However when I change the highway and highway_link to
primary and primary_link the roads are no longer one way and I get the
same error. I will attach the corrected sample to this post.
I joined roads with the same name and attributes when importing OSM data
into Polish format, so the road lengths tend to be much longer in my
data than in the original, making this issue more apparent. The
unaltered data for Thailand is full of un-connected junctions so it is
difficult to test.
I have the same error happening in five or six places, all associated
with split roads. This sample is the smallest file I could make that
shows the problem.
Garvan
snip.osm.gz
Description: GNU Zip compressed data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
