Lambertus, the OFM lite Version 29/10 has still the old buggy TYP file…
Sorry, I think I updated the wrong path on the server. Updated the styles now and stated a new update. I’ve also cleaned up some old test directories to prevent this confusion in the future.
Ligfietser, with the new style files and Mkgmap version r2337 I get:
Error in style: Error: (polygons:85): Stack size is 2
Could not open style ofm_lite
Probably caused by a “0” in line 84, didn’t know how it got there 
http://code.google.com/p/mkgmap-style-sheets/source/diff?spec=svn83&r=83&format=side&path=/trunk/styles/Openfietsmap+lite/polygons
It should work now with r83?
Yes, it seems to be working again. Will have to restart the update though…
Don’t worry, it’s not good cycling weather anyway 
Have you fixed the issue of the custom maps without the type file too?
Custom openfietsmap_lite maps now have a type file as well.
Thanks, looks ok now, except the typ file should be updated as well: http://code.google.com/p/mkgmap-style-sheets/source/browse/trunk/typ/Openfietsmap+lite/
Can you perform an auotmatic svn update in your scripts next updates to the typ file too?
I could locally as well as on the other server(s) … if all directories names were consistently named, but that is part of the cleanup effort.
A problem has been reported that, using Chrome/Chromium (and perhaps Internet Explorer, but I did not check that), it was not possible to choose the OpenFietsMap lite map. This has been solved.
I used an onChange event in an HTML form element to detect when a user selected a map (Generic or Openfietsmap lite). This works in Firefox but aparently this event is not implemented in Chrome so now I’m using the onChange event on the individual HTML radiobutton input elements.
Have been using Garmin products since 2000 and contribute to OpenStreetMap and upgraded to Windows 8 10 days ago. Whilst I can download as usual maps tiles and install for MapSource as usual. The system does not like changes being made through Mapset Toolkit 1,77 to the name etc. If it accepts the change the map does not appear in MapSource. I find the only way is to use Mapset Toolkit to install the maps hte long way around then all goes well.
Palm Desktop doesn’t like Windows 8 so I have to use my XP verion to HotSync. Anybody found a solution?
First off, thank you Lambertus for your efforts. I bought a Garmin a few years ago, and I’ve been using your site ever since.
Recently, someone tagged the island I live on (Vancouver Island, http://osm.org/go/WDzgVj-) as place=island. The tagging’s fine, that isn’t the problem. The problem is that now when I generate a map from your site, the place=island layer seems to cover up some other items, like parks, golf courses, and cemeteries, so these don’t display. With the Mapnik TYP, I was able to edit it to either remove that layer or re-order it so it’s underneath, but I can’t do that with the default, no-TYP style, which I prefer. Would it be possible for you to change the settings so the place=island layer doesn’t cover up other items? Sorry, I’m not very familiar with the map generation process, so I really don’t know how involved this may be.
Thanks in advance
Andrew
I think there are two options, either remove place=island from the mkgmap polygon style (which seems plausible, because the shapes can be rendered with multipolygons now perfectly without this island tag) or leave it as it is and render the maps with a typ file (which can be customised like you have done). BTW, with a typ file editor you can edit the mapnik typ file and make the map appear as the map without a typ file by deleting the unwanted objects.
I have used the downloaded maps in Mapsource and now Basecamp for some time and have been very pleased. However the latest UK map download (02-12-2012) appears distorted in both Mapsource and Basecamp, the horizontal distances are shrunk and the whole map looks taller & thinner than it should be. The map looks OK on my Garmin Legend though!
I have not changed any setting in Mapsource or Basecamp and they both display the previous downloaded version OK.
Any thoughts about why this is happening?
Thanks
Ken
No idea why it happened, but you can try Ctrl-Alt-A in MapSource to reset the projection angle
Thanks for the reply. I used Ctrl-Alt-A in Mapsource and chose “let MapSource choose the projection angle” and restarted MapSource but there was no difference.
I then chose an angle of 50 degrees, when I restarted MapSource the map looked OK. I then started Basecamp and that looked OK as well.
I reset the MapSource angle to “let MapSource choose the projection angle” and it reset both MapSource and Basecamp to the thin display.
I then chose an angle of 85 degrees, both MapSource and Basecamp changed back to an acceptable view which does not look any different to the 50 degree angle?
I’m not sure what changing the angle does, why the 50 degree looks like the 85 degree, why the default looks so thin and why changing it in MapSource automatically affects Basecamp but it is much better so I guess that I will use it as it is :).
Thanks once again
Ken
PS A bit of searching showed that the projection angle change is written to the registry which is why changing it in MapSource also changes it in Basecamp.
Probably 85 wasn’t accepted, since it was outside map area. Press Alt-Ctr-A again and check what is current value. I think default value is middle of the map. If area of recent release was extended more to north, then map view could change. Pity Garmin is not able to provide better conformal projection in current programs, like it was done in Mapsource 6.13.
The latest maps (2012-12-02) have an error in one of the highways in Northern Teritory, Australia. At first I though the 17 kilometre piece of road had been deleted in OSM, so I checked the road in JOSM and found it fine. It is strange as the road is one continuous straight way with very few nodes and the missing chunk is in the middle.
Check it out, the bounding Box is min lat: -19.7279276 min lon: 135.736084 max lat: -19.4898967 max lon: 136.0107422. The road is the Tableland Highway and the missing 17 kilometre piece of road is between these two points:
<trkseg>
<trkpt lat="-19.643741520121694" lon="135.87752030231059"/>
<trkpt lat="-19.519570833072066" lon="135.9730189293623"/>
</trkseg>
When I check the OSM data, there is not even a node anywhere near one of the two points and it looks clean. What would have caused this piece of road to disappear? It has no nodes in a perfectly straight 30 kilometre stretch. Could this be the problem? I will add some intermediate nodes and see if the problem exists in the next set of Routable Maps. The problem shows up in Mapsource. I have not transferred the map to my GPS so I don’t know if the piece of road is missing on the GPS. This road was fine in the previous (2012-11-29) edition of the Routable Maps.
Thanks.
The lack of nodes was indeed an issue by the tile splitter. Tile borders may vary from update to update.
There were made some major improvements with the splitter lately to prevent this. Don’t know if Lambertus used the experimental splitter version in the latest update?