Hello, I installed an 4589 map onto my Etrex 20, and all the Waypoints and routes were somehow deleted. The Waypointsxxx.gpx and other gpxfiles were still still present. As I have seen this problem before after updating firmware, I found that I could get the Etrek to re-read the Waypoint (and Route) gpx files by renaming them. There are more details on this blog post: https://hyperentang.wordpress.com/2018/04/16/lost-waypoints-on-garmin-etrek-... Presumably there is something in the img file which is somehow altering the Waypoint status? Here are the commands that I used: java -Xmx10g -jar ../splitter-r597/splitter.jar ../great-britain-latest.osm.pbf Then I compiled the mapnik.txt from version 4589: java -Xmx13g -jar ../mkgmap-r4589/mkgmap.jar ../mkgmap-r4589/examples/typ-files/mapnik.txt Finally I compiled the img file with java -Xmx12g -jar ../mkgmap-r4589/mkgmap.jar --route --add-pois-to-areas --bounds=../bounds --precomp-sea=../sea/ --index --gmapsupp --remove-ovm-work-files mapnik.typ -c template.arg Did I do something wrong, or is this a known problem? ael
Hi ael, I have no idea how mkgmap could be related to this problem. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von ael <witwall3@disroot.org> Gesendet: Montag, 21. Dezember 2020 18:07 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: [mkgmap-dev] Lost Waypoints with version 4589 Hello, I installed an 4589 map onto my Etrex 20, and all the Waypoints and routes were somehow deleted. The Waypointsxxx.gpx and other gpxfiles were still still present. As I have seen this problem before after updating firmware, I found that I could get the Etrek to re-read the Waypoint (and Route) gpx files by renaming them. There are more details on this blog post: https://hyperentang.wordpress.com/2018/04/16/lost-waypoints-on-garmin-etrek-... Presumably there is something in the img file which is somehow altering the Waypoint status? Here are the commands that I used: java -Xmx10g -jar ../splitter-r597/splitter.jar ../great-britain-latest.osm.pbf Then I compiled the mapnik.txt from version 4589: java -Xmx13g -jar ../mkgmap-r4589/mkgmap.jar ../mkgmap-r4589/examples/typ-files/mapnik.txt Finally I compiled the img file with java -Xmx12g -jar ../mkgmap-r4589/mkgmap.jar --route --add-pois-to-areas --bounds=../bounds --precomp-sea=../sea/ --index --gmapsupp --remove-ovm-work-files mapnik.typ -c template.arg Did I do something wrong, or is this a known problem? ael _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Mon, Dec 21, 2020 at 05:37:58PM +0000, Gerd Petermann wrote:
Hi ael,
I have no idea how mkgmap could be related to this problem.
That does not surprise me :-) I forgot to say that attempts to route also failed with something like "no routeable ways in this area". After I had restored the Waypoints, the map becaime routeable again. Perhaps more important and just as mysterious... ael
Hi. I have a GPSMAP 66st and have observed the same case. But i can assure you that (at least my case) had nothing to do with any map file. I also had to rename all waypoint files, or even remove all of them (make a backup), restart the unit, add the files back, and then restart the unit again. The issue seamed to occur when a one or a few waypoint files where changed outside of the unit (say from a computer). The unit did not understand how to re-build its internal database. In my case i also had a "database error" message from time to time. After some firmware upgrade and a full reset this issue looks to have stopped. I cannot say for the message "no routeable ways in this area", but i have created maps over almost half of europe with mkgmap 4589 just a few days ago, have added them to two devices and both works fine with routing. Regards Karl On måndag 21 december 2020 kl. 18:44:33 CET ael wrote:
On Mon, Dec 21, 2020 at 05:37:58PM +0000, Gerd Petermann wrote:
Hi ael,
I have no idea how mkgmap could be related to this problem.
That does not surprise me :-)
I forgot to say that attempts to route also failed with something like "no routeable ways in this area". After I had restored the Waypoints, the map becaime routeable again. Perhaps more important and just as mysterious...
ael
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Mon, Dec 21, 2020 at 07:45:22PM +0100, 7770 wrote:
I have a GPSMAP 66st and have observed the same case. But i can assure you that (at least my case) had nothing to do with any map file.
I have seen this in the past mentioned in that blog. Those cases did not seem to be associated with the map. But in this recent case, nothing else except the map was changed. All was working; I changed the map; then the Waypoints & routes were gone, and routing had stopped working. Could be a bug in the Garmin firmware, of course.
I cannot say for the message "no routeable ways in this area", but i have created maps over almost half of europe with mkgmap 4589 just a few days ago, have added them to two devices and both works fine with routing.
As I say, routing is now working, at least in the few tests that I have done so far. ael
participants (3)
-
7770 -
ael -
Gerd Petermann