Wwat would happen as far as routing is concerned if I download 3 different countries from Geofabrik and then combine them in a single file...e.g I download england, scotland, wales and then run java -Xmx2048M -jar mkgmap.jar --latin1 --gmapsupp --route --region-name="abc" --region-abbr="abc" --max-jobs --remove-short-arcs --net --code-page=1252 --country-name="abc" --country-abbr=abc --tdbfile --tdb-v4 --description="abc" england.osm scotland.osm wales.osm What I'm expecting is that routing within each country will work but routing across borders won't I've created a map with the above options and whilst what I expect to happen does seem to be happening I thought I'd check On a related note if I were to create separate england.img, scotland.img, wales.img files and then combine them into a single gmapsupp.img which of the family-name, map-name, series-nam etc options would I need for the individual files and for the combination step so that I could turn the individual maps on or off? Cheers Paul
Hi! Paul schrieb:
Wwat would happen as far as routing is concerned if I download 3 different countries from Geofabrik and then combine them in a single file...e.g
In my experience, you should encounter alls sorts of weird artefacts along the border of the pasted areas (cut roads, damaged lakes and rivers, weird fragments of woods etc.) This is because the planet files are cut with osmosis which does its job rather brutally along the borders of the cutting polygon. bye Nop
Nop wrote:
Hi!
In my experience, you should encounter alls sorts of weird artefacts along the border of the pasted areas (cut roads, damaged lakes and rivers, weird fragments of woods etc.) This is because the planet files are cut with osmosis which does its job rather brutally along the borders of the cutting polygon.
Weird artifacts at the border I can cope with and were to be expected. The places I'm visiting are hundreds of miles apart and not near any borders so that in itself shouldn't be an issue Cheers Paul
Hi
Weird artifacts at the border I can cope with and were to be expected. The places I'm visiting are hundreds of miles apart and not near any borders so that in itself shouldn't be an issue
For routing to work across the tiles, the road end point has to be in exactly the same place (well within 3 garmin units, about 20m) on both tiles and they have to be marked as edge nodes. mkgmap does this only if each tile has roads (etc) that extend beyond the declared bounds for the tile and that those bounds match up exactly. It cuts the roads exactly to the boundary and therefore knows that the node it inserted is an edge node. Cheers, ..Steve
Steve Ratcliffe wrote:
Hi
Weird artifacts at the border I can cope with and were to be expected. The places I'm visiting are hundreds of miles apart and not near any borders so that in itself shouldn't be an issue
For routing to work across the tiles, the road end point has to be in exactly the same place (well within 3 garmin units, about 20m) on both tiles and they have to be marked as edge nodes.
mkgmap does this only if each tile has roads (etc) that extend beyond the declared bounds for the tile and that those bounds match up exactly. It cuts the roads exactly to the boundary and therefore knows that the node it inserted is an edge node.
Cheers,
..Steve
Routing across borders isn't an issue (I'll be flying across that part) as long as I can route within each tile Cheers Paul
On Tue, Jul 14, 2009 at 09:12:20AM +0100, Paul wrote:
mkgmap does this only if each tile has roads (etc) that extend beyond the declared bounds for the tile and that those bounds match up exactly. It cuts the roads exactly to the boundary and therefore knows that the node it inserted is an edge node.
Cheers,
..Steve
Routing across borders isn't an issue (I'll be flying across that part) as long as I can route within each tile
This morning, I created a combined map of Geofabrik.de's finland.osm.bz2 and estonia.osm.bz2 (one tile) for tomorrow's trip. I ran both map extracts through splitter.jar (Estonia was just one tile, called 63240004 by me, and Finland was 63240001...63240003, with custom areas.list). Then I added the fourth tile to my mkgmap.args that I usually use for compiling Finland. All was well and good, but for some reason, the Estonian tile appears to lack --net information. I can't search for roads, and if I click on some POI icon on the map, no data will be available. The Finnish tiles are OK. Something similar happened some weeks ago when I compiled a small extract of my neighbourhood. I just reran the compilation with java -ea. No assertion failed. I am using mkgmap r1087. Any ideas? Marko
participants (4)
-
Marko Mäkelä -
Nop -
Paul -
Steve Ratcliffe