OK, but shouldn't region be set by mkgmap from bounds information? El 12/08/15 a las 11:14, Gerd Petermann escribió:
Hi Carlos,
I am not sure if this is an error in mkgmap or not.
If you do what the message says, e.g. using --region-name=xyz, the message disappears, but I am not sure about the side effects and why mkgmap doesn't use a default value.
The message is produced by code that handles motorway-exit nodes, they are stored in some index structures, I have no idea why. I guess some devices allow (or allowed) to search for exits?
@Steve: The code was introduced with r984 and it used the default region to create a label instead of first checking the nodes' region attribute. I don't understand that.
Gerd
Date: Tue, 11 Aug 2015 13:50:01 +0200 From: cdavilam@orangecorreo.es To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] What's the meaning of the 'has no region' warnings?
What is supposed to be wrong regarding warnings of type '(MapBuilder): 55114001.o5m: Highway EX-A2 has no region (define a default region to zap this warning)'