[mkgmap-dev] Basecamp and NET/NOD changes

Tue Nov 26 16:58:23 GMT 2019

Hi Ticker,

the reason for way -1477104 is simple:
It is the only island when you use the default style and it appears as first way in the file. With option --preserve-element-order
this seems to be a worst case scenario for BaseCamp. My understanding is that BaseCamp builds internal tables for road data
and NOD data and that this fails when a road without NOD is processed before one that has NOD.
So, my goal was to sort the data so that BC reads all the roads with NOD first. I gave up because I have no idea how exactly BC reads the data. It seems to ignore the order in NET, it seems to read the RGN file and uses the pointers to NET in it.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Dienstag, 26. November 2019 17:31
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Basecamp and NET/NOD changes

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

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev