Hi Thanks for sending these comments on.
> - no poi nor city index That's right, and I am working on on adding cities at the moment. I'm not sure how long it will take or what it takes to make them searchable, but it seems to be possible with what is publicly known about the format. > - severely jagged lines (i know it comes from your compiler...), I had > a go at the osm compiler; it's fast! Which version did you use to create the map? If was 388, then you find that that the latest version (506 or above) is very much better in that respect. > - why a transparent map? sorry-osm compiler. on some units you can't > turn off the base map so your map will interfere with garmins base > map. It is not intentionally transparent, and indeed is not transparent on my GPSr. I'll try adding background polygons to the main maps, some units may need them. > - size of 3013 is too high for older garmin units, they won't be > able to redraw fast enough It might be possible to make this configurable to some extent. However mkgmap does not have one 'size' - the areas vary in size according to how much detail there is on them and so looking at the largest size is deceptive. On the other hand the newer version of mkgmap is better able keep the divisions smaller where there are large elements, so it may be better here too. > - automate installation process to GPS unit. This is outside the scope of mkgmap, although I would be happy to include or publicize solutions developed by others. ..Steve _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
