Problems loading map to GPSr - MDR_TRIMMER.H
With the latest builds, I can no longer transfer my maps of Germany using mapsource to my e-Trex. The maps are build with the --index option, which I suspect may be part of the problem, as the error comes from MDR_TRIMMER.H. Does anyone have an idea? - I still have the region-munge.patch applied, as this was previously necessary to get the transfer to work. Below is the error information from mapsource: <Error> <Exception> <SourceCodeLocation> <SourceFileName>MDR_TRIMMER.H</SourceFileName> <SourceFileLine>930</SourceFileLine> </SourceCodeLocation> </Exception> <Application> <Name>MapSource</Name> <Build> <Version> <VersionMajor>6</VersionMajor> <VersionMinor>13</VersionMinor> <BuildMajor>6</BuildMajor> <BuildMinor>0</BuildMinor> </Version> <Type>Release</Type> <Time>Nov 28 2007, 11:23:32</Time> <Builder>SQA</Builder> </Build> <LanguageID>1033</LanguageID> <PartNumber>006-A0041-00</PartNumber> </Application> <Computer> <OperatingSystem>Windows XP Service Pack 3</OperatingSystem> <Processor>x86, Processor Level: 6, Processors:2, Model: 23 Stepping: 10</Processor> <RamSize>2097151</RamSize> </Computer> <Time>2009-11-11T20:34:54Z</Time> </Error>
+1 same problem resurfaced for me to (for Germany - most countries are no problem at all) Clinton Gladstone wrote:
With the latest builds, I can no longer transfer my maps of Germany using mapsource to my e-Trex. The maps are build with the --index option, which I suspect may be part of the problem, as the error comes from MDR_TRIMMER.H.
Does anyone have an idea?
- I still have the region-munge.patch applied, as this was previously necessary to get the transfer to work.
Below is the error information from mapsource:
<Error> <Exception> <SourceCodeLocation> <SourceFileName>MDR_TRIMMER.H</SourceFileName> <SourceFileLine>930</SourceFileLine> </SourceCodeLocation> </Exception> <Application> <Name>MapSource</Name> <Build> <Version> <VersionMajor>6</VersionMajor> <VersionMinor>13</VersionMinor> <BuildMajor>6</BuildMajor> <BuildMinor>0</BuildMinor> </Version> <Type>Release</Type> <Time>Nov 28 2007, 11:23:32</Time> <Builder>SQA</Builder> </Build> <LanguageID>1033</LanguageID> <PartNumber>006-A0041-00</PartNumber> </Application> <Computer> <OperatingSystem>Windows XP Service Pack 3</OperatingSystem> <Processor>x86, Processor Level: 6, Processors:2, Model: 23 Stepping: 10</Processor> <RamSize>2097151</RamSize> </Computer> <Time>2009-11-11T20:34:54Z</Time> </Error>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 12/11/09 00:43, Clinton Gladstone wrote:
With the latest builds, I can no longer transfer my maps of Germany using mapsource to my e-Trex. The maps are build with the --index option, which I suspect may be part of the problem, as the error comes from MDR_TRIMMER.H.
Does anyone have an idea?
That is interesting. Do you have a range of versions where the problem started? I have not made a change to MDR for a while. It would be interesting if one of Mark's changes caused it as that would mean that you can get MDR errors due to differences in the individual .img files. I've been wondering if the region problem is caused by something in the maps and not in the index.
Below is the error information from mapsource:
Sorry, I've never been able to make any sense of these messages :( The SourceFileName is probably the only useful bit as it hints that it is and MDR problem.
<SourceFileName>MDR_TRIMMER.H</SourceFileName>
..Steve
Steve Ratcliffe wrote:
On 12/11/09 00:43, Clinton Gladstone wrote:
With the latest builds, I can no longer transfer my maps of Germany using mapsource to my e-Trex. The maps are build with the --index option, which I suspect may be part of the problem, as the error comes from MDR_TRIMMER.H.
Does anyone have an idea?
That is interesting. Do you have a range of versions where the problem started? I have not made a change to MDR for a while. It would be interesting if one of Mark's changes caused it as that would mean that you can get MDR errors due to differences in the individual .img files.
I've been wondering if the region problem is caused by something in the maps and not in the index.
Below is the error information from mapsource:
Sorry, I've never been able to make any sense of these messages :(
The SourceFileName is probably the only useful bit as it hints that it is and MDR problem.
<SourceFileName>MDR_TRIMMER.H</SourceFileName>
..Steve
You can download my Germany map where it is failing from here: http://openmtbmap.x-nation.de/maps/mtbgermany.7z.zip (350MB) The big difference is that now every tile even as a single tile will fail. Before the patch I only had certain tiles failing (more than 16 regions) - now the error seems to be elsewhere.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Just as addition, if i trie to use the search via Places in the map(http://openmtbmap.x-nation.de/maps/mtbgermany.7z.zip) of Felix, MS crashes with an error in "MPL_MAPDIRECTORY.CPP". cheers Gert
On Thu, Nov 12, 2009 at 4:29 PM, Steve Ratcliffe <steve@parabola.me.uk> wrote:
That is interesting. Do you have a range of versions where the problem started? I have not made a change to MDR for a while. It would be interesting if one of Mark's changes caused it as that would mean that you can get MDR errors due to differences in the individual .img files.
I'll try narrowing this down. It appeared to start occurring at about the same time that both 'r1352: Fix "double city" display' and Mark's changes were committed. (It could, of course, also be a case of bad OSM data that crept into the Germany extract at around this time.) Cheers.
On 12/11/09 16:25, Clinton Gladstone wrote:
I'll try narrowing this down. It appeared to start occurring at about the same time that both 'r1352: Fix "double city" display' and Mark's
Ah ok, if was that long ago, then it could well be 1352. It involves the region area, where we are clearly missing something. ..Steve
Steve Ratcliffe wrote:
On 12/11/09 16:25, Clinton Gladstone wrote:
I'll try narrowing this down. It appeared to start occurring at about the same time that both 'r1352: Fix "double city" display' and Mark's
Ah ok, if was that long ago, then it could well be 1352. It involves the region area, where we are clearly missing something.
Well just retested - 1351 still works. However there is one bug that still blows mdr creation (on both current svn as well as 1351): Error output is: Exception in thread "main" java.lang.AssertionError: Invalid label offset found 425984 at uk.me.parabola.imgfmt.app.lbl.LBLFileReader.fetchLabel(LBLFileReader.java:83) at uk.me.parabola.imgfmt.app.lbl.LBLFileReader.readPoiInfo(LBLFileReader.java:293) at uk.me.parabola.imgfmt.app.lbl.LBLFileReader.<init>(LBLFileReader.java:71) at uk.me.parabola.imgfmt.app.map.MapReader.<init>(MapReader.java:80) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onMapEnd(MdrBuilder.java:108) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:361) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:124) at uk.me.parabola.mkgmap.main.Main.main(Main.java:122) You can download the map that causes this error (Isle of Man) here: http://openmtbmap.x-nation.de/maps/beta/63550000.zip I think I had a similar error on south-america but all other countries of Eurasia more or less are fine.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Nov 13, 2009, at 1:54, Felix Hartmann wrote:
Ah ok, if was that long ago, then it could well be 1352. It involves the region area, where we are clearly missing something.
Well just retested - 1351 still works.
And I retested 1352: it works as well. I tried again with 1362, but this failed. I'll continue to try to narrow it down. Cheers.
On 13/11/09 00:54, Felix Hartmann wrote:
Well just retested - 1351 still works.
Anton has made a breakthrough with the regions. He suggests sorting them by region id. This is working well for me in a quick test on the UK so I will commit it. Make sure that you remove any region-munge patch you have installed before trying it.
However there is one bug that still blows mdr creation (on both current svn as well as 1351):
Error output is: Exception in thread "main" java.lang.AssertionError: Invalid label offset found 425984
This and similar errors are down to incorrect maps created with road-name-pois and other options that can create cities. I can certainly stop the mdr creation bombing out, but there will be missing POI infomation. ..Steve
On Fri, Nov 13, 2009 at 10:46 AM, Steve Ratcliffe <steve@parabola.me.uk> wrote:
On 13/11/09 00:54, Felix Hartmann wrote:
Well just retested - 1351 still works.
Anton has made a breakthrough with the regions. He suggests sorting them by region id. This is working well for me in a quick test on the UK so I will commit it. Make sure that you remove any region-munge patch you have installed before trying it.
I will try this out later on. I have slightly narrowed down the release which causes Germany to fail: 1352: Works 1357: Fails If the region sort does not work, I'll continue narrowing down the release. Cheers.
Hi Clinton,
I will try this out later on. I have slightly narrowed down the release which causes Germany to fail:
1352: Works 1357: Fails
If the region sort does not work, I'll continue narrowing down the release.
Within that range of commits, the only one that alters the map data is: Substitute '/' for ';' in display_name to avoid it getting split. Based on patch from Clinton Gladstone. git-svn-id: http://svn.parabola.me.uk/mkgmap/trunk@1353 Weird or what? Cheers, Mark
On Fri, Nov 13, 2009 at 12:36 PM, Mark Burton <markb@ordern.com> wrote:
Within that range of commits, the only one that alters the map data is:
Substitute '/' for ';' in display_name to avoid it getting split.
Based on patch from Clinton Gladstone.
git-svn-id: http://svn.parabola.me.uk/mkgmap/trunk@1353
Weird or what?
Wow. I will be so annoyed if this turns out to be the problem! ;-) Cheers.
No I don't think this is responsible. I just deleted exactly that line: "displayName = displayName.replace(";","/");" but Mapsource still crashes upon clicking on "find places". Mark Burton wrote:
Hi Clinton,
Wow. I will be so annoyed if this turns out to be the problem! ;-)
It would be somewhat ironic if the character chosen to replace occurrences of ';' turned out to be poisonous. If it is that, how about trying '-'?
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
No I don't think this is responsible. I just deleted exactly that line: "displayName = displayName.replace(";","/");" but Mapsource still crashes upon clicking on "find places".
Maybe there are still ';' in the names and mapsource is barfing on those? Maybe mapsource doesn't like '/' or ';'?
Mark Burton wrote:
No I don't think this is responsible. I just deleted exactly that line: "displayName = displayName.replace(";","/");" but Mapsource still crashes upon clicking on "find places".
Maybe there are still ';' in the names and mapsource is barfing on those?
Maybe mapsource doesn't like '/' or ';'?
That is definitely not the problem. It is the city code introduced with 1352. If I add the changes of 1353 to 1351 it still works without problems, just 1352 is somehow breaking it.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Felix,
Maybe mapsource doesn't like '/' or ';'?
That is definitely not the problem. It is the city code introduced with 1352. If I add the changes of 1353 to 1351 it still works without problems, just 1352 is somehow breaking it.
Ok, well it did seem a bit unlikely that / or ; were the culprits! As I don't know how any of the MDR stuff works, I can't suggest what could be wrong with 1352. Sorry. Cheers, Mark
Clinton Gladstone wrote:
On Fri, Nov 13, 2009 at 10:46 AM, Steve Ratcliffe <steve@parabola.me.uk> wrote:
On 13/11/09 00:54, Felix Hartmann wrote:
Well just retested - 1351 still works.
Anton has made a breakthrough with the regions. He suggests sorting them by region id. This is working well for me in a quick test on the UK so I will commit it. Make sure that you remove any region-munge patch you have installed before trying it.
I will try this out later on. I have slightly narrowed down the release which causes Germany to fail:
1352: Works 1357: Fails
If the region sort does not work, I'll continue narrowing down the release.
Cheers.
Could you please retest 1352. I have 1351 working, 1352 failing on Germany. I my opinion it is definitely the fix city code by Anton that is causing the problem! (remember to run ant clean when downgrading before using ant dist, otherwise it will still fail)
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Fri, Nov 13, 2009 at 1:39 PM, Felix Hartmann <extremecarver@googlemail.com> wrote:
Could you please retest 1352. I have 1351 working, 1352 failing on Germany. I my opinion it is definitely the fix city code by Anton that is causing the problem! (remember to run ant clean when downgrading before using ant dist, otherwise it will still fail)
I'll try 1352 again. I do think that this is most likely. I may have made an error selecting the revision, or in building. Cheers and thanks for helping track this down.
participants (5)
-
Clinton Gladstone -
Felix Hartmann -
Gert Münzel -
Mark Burton -
Steve Ratcliffe