I think it is a false positive, these things happen. You can check yourself by testing the website using online virusscanners like http://www.virustotal.com
Ligfietser, I have a first test map that includes a small installer in the _tiles.zip. BaseCamp shows the map alright.
Only difference is that this installer does not move+install the map in \Garmin\maps but simply in the directory where you unpacked the zip file. Do you think this a problem for end-users?
I know the tiles are just a random selection, this test is purely about the _tiles.zip file and the small install.exe
I understand this new approach takes a little more effort for the user than just click on the exe installer and let the installer do the job.
As long as we give them good instructions about the changes (perhaps in the wiki?) I dont think its a problem?
The only big difference is that the users need to do an extra step,
unpack it to the location where you want to put the map
look for the install.exe file and execute this
BTW another problem, the install.exe might be detected as false positive by some scanners
newbee question:
How can I give the maps in BaseCamp meaningful names?
I composed two maps for two trips. Now I get the osm_generic_new_gmapsuppā¦exe file, I use the Windows Version and execute it. After that I have one map in my basecamp. But now I want to install a second map of a different Region. How can I do this having meaningful names in the Basecamp Dropdown box???
I also installed the map on my Germin device copying the map to a SD Card and rename the .img file, this works fine.
With best regards
Gerhard
PS: Want end up with the tracks of all my trips and having all maps used for that trips in basecamp
The other thing, in basecamp a lot of the islands in Greece are rendered with hatching, If i look at the data in the editor there is not anything defined.
So for instance next to the reservoir there is ānothingā while the whole of Rhodes is hatched, including the reservoir.
And something else that i noticed while walking around in the old city of Rhodes with my gps is that those streets are rendered as very thin white lines against a light background on even the maximum zoom in level. Making it almost impossible to see the roads inside the old town. https://www.openstreetmap.org/#map=18/36.44260/28.22540
That removed the hatching for the Islands and made the map more readable with basecamp.
This map is installing on my gps as we speakā¦ but this always takes a long time with my macā¦ And if I donāt install them and just copy the gmap image from the website every time I open basecamp it will load the map from gps and I have two identical maps as a choice in basecamp (one from gps and one already on pc).
By the time I was done checking and changing Crete I could also check my gps where the old town and the lake are both rendered correctly now.
Crete is a different matter though. I already noticed that the hatching was much bigger then the Island, partly 10km GISCO buffer zone and the other side is Crete/south aegean periphery.
I Assume this is a data problem at osm and I am willing to change it except I have no idea what is wrong scratch that I think I know what is the problem and I hope I fixed it.
ā¦ I assume it is the multipolygon ĪĻĪ®ĻĪ· (Crete) 453129 and then in particularly the fact it was tagged place=island , which I just removed.
Correct, the tag place=island is rendering the whole boundary as island. Iād better make this polygon invisible instead of rendering it as land (hatched pattern if you dont use a typ file), because I fear more mistakes are made with this tag.
Search for the city of Suphan Buri, located at N14.46762 E100.11834. In Mapsource and the GPS all places in Suphan Buri province that I have seen so far are shown as located in the neighbouring province:
Suphan Buri
Phra Nakhon Si Ayutthaya Province, THA
Suphan Buri is capital of the province with the same name.
I notice something strange as I point my mouse at the provincial boundaries. W of Node: 2902644726 it shows both province names, E of this only one. At this point the boundary for a national park splits off. I donāt understand enough about relations to troubleshoot this, so I would be glad if somebody could take a look. I donāt even know whether this is related or not.
Peter, could be a broken boundary problem in OSM, maybe it is fixed in the next update because it was edited recently: http://www.openstreetmap.org/relation/1908824 (seems not broken now)
Thanks for noticing it Mafketel, because I now see that this place=island polygon is causing more issues, like covering too many details (like covering other landuse types) so I have to made it invisible in the TYP file anyway. Now it will only render the island names. Land area is already rendered by the coastline tags so there is no need to do this with a place=island tag.
I notice that the front page of the garmin.openstreetmap.nl site shows a map based on 2014-07-07 data. Is it no longer on a weekly update cycle, or did this weekās update just fail to happen as planned?