popej, aren’t those segment IDs also being used in the search index files? Changing them would break search possibilities I guess…
I did think of adding the option to change the segment IDs in GMTK, but this kept me from doing it…
It’s not a trivial task. GMapTool simultaneously changes map ID in many places including search index. Corrected subfiles are: TRE, GMP, MPS, MDR, MD2, TRF, MMR. You can find map ID in other files - TDB, MDX, JCV. These aren’t processed by GMapTool.
Is it possible that the latest Open Fietsmap Lite as downloaded from garmin.openstreetmap.nl misses the area-features?
I only get lines and points on a light green background (“Land”). Both from the installer and from the gmapsupp.img. And from both latest versions.
In the older versions this wasn’t the case.
Geert
You are right, it looks like something went wrong. If I remove the typ file, the area objects appear again so they are somehow invisible.
I can’t see any faults in my typ files, the light version on my openfietsmap.nl looks good (generated with mkgmap r2431).
Lambertus’ version is generated with mkgmap-r2423, maybe this version has some bugs.
I reported one issue which had to do with the typ file processing too, so maybe in the next update with an improved mkgmap version it’s solved?
Lambertus, can you check if the lite version uses the parameter --generate-sea=land-tag=natural=background?
I suspect it uses somehow natural=land as background (0x27) which covers almost everything because I use it for other purposes in my typ file (islands in a lake for instance).
A typ file to fix this issue can be downloaded here (temporarily workaround, need to be fixed in the compilation process)
Thanks for reporting this problem. I’ve updated Mkgmap to the latest version (r2440) and started a new map update. The new OpenFietsMap Lite version should be online in 1-2 days.
The new OpenFietsMap Lite version is online. I hope polygon problem is fixed now?
Hi. Unfortunately I still need the fix-typ file to get the polygons.
Geert
Lambertus, have you checked the --generate-sea option?
Hi,
Is the site no longer working with FF18 ?
There are some users reporting in the Q&A Forum and myself also have no success.
Chris
Which site? This Forum? I have no problems with FF18.
Peter
Hi,
was already repaired by Lambertus.
Chris
I’ve been informed that the server is currently not reachable because of network maintenance work. Please be patient, the server should be back in a few hours.
Hi,
since Saturday I am trying to download a map with some Asian tiles.
I am able to select the regarding tiles and submit the request, but I do not get any mail. No confirmation and no mail containing the download path.
What can I do?
Regards wwgkn
Thanks for the report. I think the mail service has stopped because of the network maintenance. The mail service has been restarted and verified that it’s working again. I don’t know if you’ll receive the old messages, but you can simply request your map again in case you don’t.
Thank you.
I now received all mails of the previous tries of map generation.
I started to download the relevant files. However it seems that I am not the only one who is doing this now.
But this is a minor issue and will disappear, soon.
Best Regards wwgkn
It’s possible that many people are downloading now. If they all do at the same time then the harddisks will be having a hard time providing the proper bytes and everyone will have much reduced download speeds. If you don’t need your map immediately then you can try again in a few hours and enjoy a much faster download 
Edit: Yup, the custom map server is quite busy:
The OFM Lite background is still not in order. I can’t find any OFM Lite options on the server, only one build.php that redirects to a general one. There is one build.php.old that contains the generate-sea=land-tag=natural=background options so there might be something wrong in the scripts. Can you check this Lambertus?
Indeed, there is currently only one build script for both maps which includes a config script that is map-specific. I messed-up while extracting the config from the old (individual) build scripts, somehow the generate-sea option was lost during this process which I only noticed after you mentioned it. I’ve added this option to the config last weekend and a new update is running.
BTW, the previous update failed because the planet update script generated (the osmupdate too actually) a corrupt planet somehow. There are so many steps where things can (and do!) go wrong… sigh 
Lambertus, you remind me of this guy: 
