TRE value 4 -- maybe related to intertile routing?
Where is TRE4 set in mkgmap? I know that TRE values 1-3 are set here: uk/me/parabola/imgfmt/app/trergn/TREHeader.java writer.put3(displayPriority); writer.putInt(0x*110301*); However there is a fourth value which in most Garmin maps is 0xd, whereas we use 0xc. If I use gmaptool to adjust it to any uneven number (like the Garmin default 0xd) then routing does not work at all anymore. But Garmin maps use this value. Therefore I would like to try out what happens if we use mkgmap to directly set the fourth TRE value to different numbers, but I can't find it in the sourcecode.
On 01/05/10 10:52, Felix Hartmann wrote:
Where is TRE4 set in mkgmap?
It is in the LocatorConfig.xml file as poiDispFlag if that is what you mean. I didn't know that and I have no idea why it should vary by country, but presumably Bernhard knows or at least has an inkling of why it might vary. ..Steve
On 01.05.2010 16:12, Steve Ratcliffe wrote:
On 01/05/10 10:52, Felix Hartmann wrote:
Where is TRE4 set in mkgmap?
It is in the LocatorConfig.xml file as poiDispFlag if that is what you mean. I didn't know that and I have no idea why it should vary by country, but presumably Bernhard knows or at least has an inkling of why it might vary.
..Steve No I don't think you know what I want. Right now mkgmap sets the value to 0xc, but I think it has to be 0xd. It is definitely fixed somewhere and has implications on routing. However it seems to me that the actual number does not matter, however it matters whether the number is even or uneven. It is in gmaptool (using experimental options) the fourth value, but I have no clue at all where it is hardcoded in mkgmap.
No I don't think you know what I want. Right now mkgmap sets the value to 0xc, but I think it has to be 0xd. It is definitely fixed somewhere and has implications on routing. However it seems to me that the actual number does not matter, however it matters whether the number is even or uneven. It is in gmaptool (using experimental options) the fourth value, but I have no clue at all where it is hardcoded in mkgmap.
As I said the 0xc value is not hardcoded in mkgmap, but contained in the LocatorConfig.xml file. In fact we do know some of the bits in the value: 0x8 is to show zip before city in POI address 0x4 is to show street name before street number 0x2 is for transparency, but that is handled elsewhere 0x1 is the bit you are interested in finding the meaning of. Unless it happens to control something that varies from country to country, it would of course be sensible to set it within mkgmap separately from the LocatorConfig.xml file, just like the transparent bit is now. ..Steve
participants (2)
-
Felix Hartmann -
Steve Ratcliffe