The generic_new map is already updated, the other two are expected to come online in a day.
Edit: no, only the update for OFM lite is still running.
Thanx for the good work!!
I wasn’t able to post the question due to unstable internet connection and obscure links
We’ll be happy to relay your question
I’m getting some questions about installing more then one custom map alongside each other on Windows (BaseCamp). I’m not too familiar with this process, so I’d like feedback on the workflow so I can update the wiki FAQ.
This is what I’ve done:
- request a custom map using the website (OSM generic routable) and download the Windows installer.
- install the custom map
- run JaVaWa’s GMTK
3.1) select the map named ‘OSM generic routable’ and goto menu ‘Extra’ → ‘Change map name and ID’ - GMTK will show a form and the following values are changed:
4.1) Family ID: enter a unique number, e.g.: 2001
4.2) Name on computer: enter a good description of the map, e.g.: ‘OSM Central America’
4.3) Name on device: enter a good description, e.g.: ‘OSM Central America’
4.4) Folder name: enter a good (unique) folder name, e.g.: ‘OSM Central America’
4.5) Click on the ‘modify’ button
For every new custom map the same sequence of events is performed, each time using a new unique ID and name.
This process seems straightforward enough to me. However, when I install the second custom map, the map installer will warn that there is already a map installed. This warning can safely be ignored but it is confusing to a lot of users. What can be done to prevent this warning?
I think the problem is that GMTK doesnt remove the map installer when updating the map data.
So there are two options, adjust GMTK or adjust the custom map procedure by letting the user enter a unique FID and name before generating the map. Maybe contact Javawa by pm to discuss this?
Is it possible for you to provide the maps in two encodings? This way you have maintained compatibility with older devices while the users who need Unicode maps can download them from here. Unicode support is a serious issue and affects the bulk of OSM data being developed in Asia. Imagine local street names in Arabic, Persian, Chinese, Korean, Japanese, … Older and incompatible devices are unusable for these regions anyways.
Free Unicode maps won’t work in newer devices like Edge 1000, GPSMAP 64, some recent models of nuvi. It looks like Garmin decided, that all Unicode maps should be digitally signed, which can’t be done with 3-rd party tools.
Hi,
first of all: Thanks for the great maps!
I recently tried the “new style” on my Nüvi 1255. During daytime everything is very nice, but the night-mode looks ugly - there are many black areas along with even more almost white areas. Can I do something about this, maybe using a dedicated typ file?
Another remark: I’d appreciate a style with a few less details, e.g. I don’t need every single house in an urban area rendered. This would help with older and slower devices like mine.
The night mode is totally undeveloped so any volunteers who want to improve this feel free to help.
You can edit the typ file with tools like typviewer and typwiz.
The typ file you can find in the metadata folder of the download link.
In order to change the typ file of the map on your device, you can use typchanger
Mueschel, just set your device to day mode only and it will be fine. You may want to turn down the brightness at night…
typviewer seems to be a fairly easy tool to change colors. But, typchanger doesn’t work at all. After adding the files and clicking ‘change’, it just displays ‘Done’, but there is absolutely no change made to the map file. Do you have any advice how to debug this or another tool to accomplish the task?
Thanks, gmaptool works fine. I changed some of the colors for night mode. For sure the result is not perfect, e.g. I did not manage to remove the white outline of paths and unpaved roads in night mode - my device seems to ignore this setting. Anyways, the result seems much more pleasing than the default colors. I uploaded the changed typ-file in case anyone is interested: http://osm.mueschelsoft.de/24276.typ
Great:
The issue I reported on 13th of November (http://forum.openstreetmap.org/viewtopic.php?pid=463274#p463274) regarding address (house number) searches seems to be solved. In new downloaded maps, the address search really finds the relevant house number in its place.
Thanks once more
Sorry if I go back to your post of 2 weeks ago.
I wonder if you were referring to a generic update of the maps or to an update to solve the problem I asked about in my post, that is searching addresses.
I tried Garmux, a script that creates maps using a search index that includes also the last word in the name tag and it works fine. The code is similar to http://www.i-nis.com.ar/osm/garmin.
Thank you
maxx
No Maxx that is still not implemented, although mkgmap developers are working on it as well (see this thread).
Lambertus was replying post #2280.
I’m not sure if this kind of problem is supposed to be discussed in this thread, if I’m wrong suggest where to post it.
I downloaded the generic new file of Italy last week, gmapsupp.img and installed it on my garmin nuvi 205.
Yesterday I entered a destination for my wife. Unfortunately I didn’t check the path created by the nuvi and after a few minutes she called me upset because the navigator sent her to the wrong highway.
At this Osrm link you can see the right track: http://osrm.at/atS
This is the track suggested by nuvi: http://osrm.at/atV
I tried the same start-destination track with different navigators and only the nuvi 205 gives the wrong result.
OSM data seem to be ok.
What happened?
Thank you
maxx
Looking at the OSM data I can’t see any problem or any reason why any navigator should route you the long way. I have seen this kind of behaviour before and suspect it’s a firmware bug in the Nuvi, especially since you say that others work ok.
First step: check that your firmware is up-to-date. You should have the latest version loaded.
Also, check that you don’t have any other maps loaded covering the same area, e.g. Garmin CNNT. If you do have one, make sure it is unchecked (disabled) and if that is already the case you should disable it completely by renaming the map file and re-test.
Failing all that, you can try reporting this to Garmin, but since we are dealing with non-Garmin maps don’t hold your breath.
Cheers,
Peter.
Also, check to see if the settings on your Nuvi are preventing use of tollroads or other “avoidances” (U-turns, car pool lanes, etc.). I always un-check all of these in the routing profile on my Montana and then after the route is computed, check it carefully to see if there’s something I want to avoid or want to use a different highway. I don’t want the Montana to 'think" for me because it often makes bad decisions.
Cheers,
Dave