Hi Steve, I noticed that NodCheck reports an error when a road has no NOD information while the img file contains a NOD subfile. Attached patch seems to fix that. I fear the reason for this error is that no Garmin map with a NOD file contains roads with RoadDef.NET_FLAG_NODINFO = false or why didn't you face this problem up to now ? Gerd
On 08/04/15 07:50, Gerd Petermann wrote:
I noticed that NodCheck reports an error when a road has no NOD information while the img file contains a NOD subfile. Attached patch seems to fix that.
Yes, seems fine; display is all experimental, just commit anything that seems useful...
I fear the reason for this error is that no Garmin map with a NOD file contains roads with RoadDef.NET_FLAG_NODINFO = false or why didn't you face this problem up to now ?
Yes it is quite likely that they don't use non routable road hacks ;) I just checked a couple of files and did not see that error and I can't recall having seen it either. ..Steve
Hi Steve,
I fear the reason for this error is that no Garmin map with a NOD file contains roads with RoadDef.NET_FLAG_NODINFO = false or why didn't you face this problem up to now ?
Yes it is quite likely that they don't use non routable road hacks ;) I just checked a couple of files and did not see that error and I can't recall having seen it either.
They may also use a trick to place a dummy road at offset 0 or something like that. The question remains: Why do we have a flag like RoadDef.NET_FLAG_NODINFO if it is not allowed for this? Gerd
participants (2)
-
Gerd Petermann -
Steve Ratcliffe