[mkgmap-dev] Basecamp and NET/NOD changes
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Tue Nov 26 16:31:44 GMT 2019
Hi Gerd I've trying various things, like changing the TYP, removing road -speed/class, ... to try and pin down this problem and generally, the behaviour got worse. I experimented a bit with your cut-down area: ticker-part-mod.zip but had problems. Way -1477104 confused me for a while. So I went back to the full tile. I've just updated to trunk latest r4387, removed all my changes and did a clean rebuild, then, with --check-routing-island=-1 tried lots of Motorcar routing in Basecamp and I find areas of my map still misbehave. EG: "so23 0je" > "so23 0ps" straight line to a road a few roads east then straight line back. "so23 0qb" > "so23 9ru" straight line. Generally, all routing fails around this small area, but other areas north and west work fine. The setup and data is identical to before but I've just been using the northern tile (74210002.osm.pbf) I'm just going to try some of these on the Device and pick some other areas with island=-1 on the ticker-part-mod Ticker On Mon, 2019-11-25 at 07:16 +0000, Gerd Petermann wrote: > Hi Ticker, > > okay, I was not able to reproduce the problem on my Oregon, and it > turned out that the one routing problem in Mapsource was my fault, I > asked for a route which was forbidden because of oneway roads. > I think that means that nobody should use option --check-routing > -island-len=INTEGER when they use BaseCamp or when they publish their > maps unless we find a better implementation. > > Gerd
- Previous message: [mkgmap-dev] Basecamp and NET/NOD changes
- Next message: [mkgmap-dev] Basecamp and NET/NOD changes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list