Hello mkgmap developers!
I experimented a little bit with the AiO Europe Map in Mapsource and the
496 available *.img tiles.
( Source of *.img files:
ftp://ftp5.gwdg.de/pub/misc/openstreetmap/download.openstreetmap.de/aio/europa-daily/img/
)
Installing and viewing the AiO map in Mapsource is
I have the same problem with Mapsource here.
Since r1919 Mapsource crashes again with OSM Europe, when you try to
select tiles to be uploaded to the GPS. You can view the tiles, zoom in
and out. All fine, but as soon as you select one tile Mapsosurce crashes.
Yet the error is different than the
> What version of MapSource are you using?
6.16.3 on Win7_x64
Peter
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> DSK_PRIVPARTITION.CPP-314-6.13.7.0
This is the same error I had when the mdr-file exceded the former fixed limit
of 256 MB.
Maybe one file is larger than the adjusted C/H/S values now specify.
Peter
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkg
>> Maybe one file is larger than the adjusted C/H/S values now specify.
> I don't think so. All my other maps, even the smallest ones are broken
> with the patched mkgmap. Did it fix the problem for you?
Can you get me a compiled jar including the fix? I'm not a dev guy ...
Peter
__
> New patch attached.
> Description: version of mkgmap with patch for header size values.
The whole Europe map still seems to blow some limits.
The osmmap_mdr.img >240 MB seems to be the problem.
"NOT OK"
try 491520, for mb=493761
try 507904, for mb=493761
"OK!!!"
try 491520, for mb=493113
try
> Could you try with the attached patch and (if it is still NOT OK) please
> send me the whole output and the exact size of the mdr file.
Sorry, the complete europe map still seems to trigger some limits.
It's again the mdr.img being >240MB. I uploaded the faulty file to the
mkgmap website. Her
>> Sorry, the complete europe map still seems to trigger some limits.
I did some more testing.
With the option --block-size=8192 I got the whole europe map as far so
that I could select tiles. But now the gmapsupp index creation fails.
- pan and zoom: OK
- select tiles: OK now
- idx creation:
Hi Steve,
> Thanks, I will take this as confirmation that the patch works.
One step further ...
> MDR_TRIM_ADDR.CXX-440-6.16.3.0
>
> This is a completely different problem. Would it be possible to upload this
> broken file too?
That's done.
Peter
___
Steve,
> Thanks, that's great. It may take a while to work out what the problems
> is. Do you have an mdr file that a bit smaller that still works completely?
I'm still on the follwing Mapsource upload problem.
- pan and zoom: OK
- select tiles: OK
- idx creation: CRASH at ca. 14%
After some ex
I forgot to mention that I already uploaded the problematic tiles and
idx files to http://files.mkgmap.org.uk/download/ ...
Peter
Am 27.05.2011 00:01, schrieb Peter Lerner:
> Steve,
>
>> Thanks, that's great. It may take a while to work out what the problems
>> is.
Steve,
> I think we should investigate the lower case letter
> problem first and see if that makes a difference. If you can send me the
> osm files too I can try it out myself.
The OSM src files are uploaded.
> I'm not sure why the lower case letters get there, since they only occur
> in the asc
Steve,
I tested the greek_index patch patch only. I assumed it was an
alternative to the translit_first patch. Was it? Or should it accumulate?
First thing with the greek_index patch, should be to add the
forceUppercase()-method definition to the Transliterator interface to be
able to compile
>74 525,9 MB MDR_TRIM_SC.CXX-808-6.16.3.0
>49 346,3 MB MDR_TRIM_SC.CXX-808-6.16.3.0
> With a few less tiles we trigger another TRIM-error in mapsource.
> It changed from ADDR to SC(?).
I uploaded the mapsource tmp file when the error wa
>74 525,9 MB MDR_TRIM_SC.CXX-808-6.16.3.0
>49 346,3 MB MDR_TRIM_SC.CXX-808-6.16.3.0
I could successfully transfer 596 tiles with a total of 3,67 GB --
excluding Balkan states and eastwards!!
That means greek and cyrillic(?) letters a
Steve,
>> Yes I mean the problem was unchanged.
> Well I think that you cannot be running the same patch as me then as
> there is certainly a difference in what goes into the osmmap_mdr.img
> It may still not work in mapsource, but I have no way of knowing that
> without some help.
I also stil
Steve,
> Done. Its at: http://files.mkgmap.org.uk/download/33/mkgmap.jar
I think "locator + city-region-index branches (2)" is a milestone!
This is a strong "+1" from my side to commit the changes as soon as
possible and try to base a stable mkgmap release v1.0(?) on this version.
For a long ti
Wanmil,
>> This should IMHO be the overall goal of the whole mkgmap project.
> Agreed!
NOT AGREED. At least not completely!
You should take into consideration the user's necessity to visually
select tile subsets for an interesting region. You would also have to
clone and engineer the visual ti
Zsolt,
...
> What am I doing wrong? If you need any more detail I'd be glad to
> provide it.
not an answer to your problem, but a question to the list:
Do we have a bugtracking tool that we can use to document software problems?
Peter
___
mkgmap-dev
Steve,
This should IMHO be the overall goal of the whole mkgmap project.
>>> Agreed!
>> NOT AGREED. At least not completely!
>>
>> You should take into consideration the user's necessity to visually
>> select tile subsets for an interesting region
>
> You are right, Peter.
> However, it i
Zsolt,
> Sorry, I thought MapSource usage is common on this list. The red areas
> are where the map was completely rendered and you can mark them for
> upload. The grey and yelllow areas are rendered only on the lowest
> resolution, so they cannot marked for upload. The rendering process is
> brok
21 matches
Mail list logo
