Re: [mkgmap-dev] Bug in Road Merging - actually doubling roads.

Hi all, I don't think this problem is caused by merging, at least not the problem that I see with the default style. I also don't think that merging can help to solve the problem. This is just a problem of resolution. The junction is simply too far away from any Garmin grid point and there

Re: [mkgmap-dev] Maps aspect ratio

that's normal. Basecamp takes the central point (north/south) of any map as reference for the cache. The more north/south away from this point, the more it will be stretched. There is a way to define where this point is set - in Windows quite easy, on OSx a bit more complicated if I remember

[mkgmap-dev] Maps aspect ratio

One user of my maps has commented that in my maps longitude looks much shorter than latitude. Comparing the same area in three maps (CityNavigator, OpenFiestMap and my maps) they all show different aspect ratio [1]. Do you know reason for that? Any way to control it? [1]

Re: [mkgmap-dev] Bug in Road Merging - actually doubling roads.

I think merging is fine - maybe just add restrictions to the adjoining ways if preset. And it really should not happen that ways are merged past a junction - I now think this happens in some more places. Because it's not the first time I notice that a routing turns 180° to return to the junction

Re: [mkgmap-dev] Bug in Road Merging - actually doubling roads.

Hi Gerd, Maybe it's better to try to merge these small ways as they anyway only creates 'ugly' roads. With increasing level of details in OSM I think mkgmap will need some preprocessing to generalise the data first. I'm not only thinking about these very small ways, but also have the

Re: [mkgmap-dev] methods to write signed / unsigned integers

Hi Steve, I think msg.patch looks good. I'd like to postpone the other changes until the "shrink factor" in DEM is understood. Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: