Welcome, Guest. Please login or register.

Login with username, password and session length
Forums Search:  


Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - -Oz-

Pages: 1 2 [3] 4 5 ... 106
31
Map Making Support / Re: Questions regarding Part 9 Setup Files
« on: March 24, 2016, 06:03:14 PM »
It is still whatever you are opening it in most likely? I open and edit all these nsi files in notepad++. If you copy/past it to a new text document it should go away.

32
That map should have opened this tutorial: https://www.gpsfiledepot.com/tutorials/how-to-open-maps-in-garmin-basecamp/

Try following that and let us know if you have an issue.

33
Map Making Support / Re: No Interstate or US Hwy Symbols
« on: March 20, 2016, 05:29:47 PM »
Good call; based on your suggestion I read the cgpsmapper directions.

Turns out I had to change LBLcoding=9 (left the codepage=1252 because that allows lowercase letters) then also switched my shields to ~[0x01] and ~[0x02].  I'll be updating the default dictionary that comes with the tutorial to allow for this and also adjusting the tutorial to automatically handle interstates and US Hwys.

34
Map Making Support / No Interstate or US Hwy Symbols
« on: March 19, 2016, 06:17:21 PM »
Hoping someone out there can explain this.  So i'm trying to improve my maps and make the interstates have the shield as well as the US Hwys.  Here is a sample from the mp file:
Code: [Select]
[POLYLINE]
Data0=(33.658058,-107.095794),(33.658102,-107.095731),(33.658565,-107.095055),(33.658599,-107.095006),(33.659987,-107.093034),(33.660111,-107.092855),(33.660622,-107.092119)
Label=~[0x2a]25
Type=0x01
[END]
However, as you can see in this picture from BaseCamp it doesn't seem to work:

The I-25 is shown as *25 and the US Hwy 380 is shown as +380.

Ideas?

My dictionary header has:
LBLcoding=6
Codepage=1252

35
Using The Maps/Garmin Software / Re: Question about the Arizona Topo
« on: March 17, 2016, 07:53:30 PM »
I agree on unintuitive; if you figure out an efficient way just let me know and I'll start downloading.

36
Using The Maps/Garmin Software / Re: Question about the Arizona Topo
« on: March 17, 2016, 06:10:21 PM »
The trails shown on the map are from the USGS or National Forest Service. The multiple trail problem likely means other trails exist or used to exist per those sources.  A few of the locations have trails based on people hiking it but the Chiricahua's are not one of those locations. 

If Hike Arizona would release all the trail data in one lump sum I would delete every single trail on the Arizona Topo and replace it with their data since it is likely more accurate.  However, I can find a quick way to download them all or anything like that.

If someone is willing to download all the trail files I would take them and add them in immediately.

37
General Discussion / Re: No maps in BaseCamp or Mapinstall
« on: March 17, 2016, 06:03:15 PM »
Exactly which map and do you see them in BaseCamp in the map products drop down menu at all?

I'd also suggest installing the Arizona Topo and see if that works?  If so, then try to install the WI Topo again and see if it shows correctly.

The other option is to install it to C:\Garmin\witopo11 and see if that works.

38
Yea I debated that since I have the installer script already created. My problem is I feel that whole thing is "antiquated" since it does require you to load the maps to the C: drive which is not a great plan if you do a small(er) SSD for C: and store data in another location.

39
General Discussion / Re: Az Topo not appearing in Basecamp
« on: March 15, 2016, 06:44:42 PM »
I just posted a new version of the Arizona Topo installer that should not have this problem. You won't even have to modify the location of the map.

40
Map Making Support / Re: Questions regarding Part 9 Setup Files
« on: March 15, 2016, 06:43:49 PM »
Note: There is a new map install file. You definitely want to re-compile with the new version. Updated version here.

41
Alright so I wiped a computer and spent some time experimenting. It turns out Windows 10 changed how the NSIS installer works to it "doubled" the registry and loaded it into the wrong spot. This meant that it wouldn't work. The weird catch was if you had previously installed one prior to the upgrade for some reason it installed correctly. Additionally, it doesn't appear to matter what directory it is installed in so for now i left Program Files (x86); if anyone has an issue let me know.

Either way I fixed the map install nsi file. Updated version here. Rather than trying to experiment and find the right place in the registry it is now coded in correctly.

Thus far I've updated the Arizona Topo install but I'll begin chugging through all my maps in the coming days to get the right version.

42
Map Making Support / Re: map_install_x64-x86.nsi
« on: March 15, 2016, 06:40:47 PM »
Alright so I wiped a computer and spent some time experimenting. It turns out Windows 10 changed how the NSIS installer works to it "doubled" the registry and loaded it into the wrong spot. This meant that it wouldn't work. The weird catch was if you had previously installed one prior to the upgrade for some reason it installed correctly. Additionally, it doesn't appear to matter what directory it is installed in so for now i left Program Files (x86); if anyone has an issue let me know.

Either way I fixed the map install nsi file. Updated version here. Rather than trying to experiment and find the right place in the registry it is now coded in correctly.

Thus far I've updated the Arizona Topo install but I'll begin chugging through all my maps in the coming days to get the right version.

43
I believe the Name is case sensitive (but I'm not sure). Use NAME next time. However, for now change the script from NAME to Name and it should work.

From the word doc Windsor Pond should actually have a label in basecamp if you zoom in enough. The 0x07 type does not though.

44
How big is one of your .mp files if you zip it? I'd like to take a look at the file. My guess at this point is that in QGIS the column name was not NAME and thus it didn't convert any of the labels from the .shp file over to the .mp file.

Quick way to test is open the  Lines_0000.0001.shp file. Now open the attribute table and see if the column with the labels is called NAME or something else? If it is something else that is the issue. Thankfully you can fix this with a three modifications in ConvertSplit2mp.bat:
Code: [Select]
if "!filename:~0,4!" == "Line" (
%gpsfdshp2mpfolder%\gpsfdshp2mp.exe %%f "MP_TYPE" "NAME" n %dictionary_file% !initialmapid! !finalmapname!
)
if "!filename:~0,5!" == "Point" (
%gpsfdshp2mpfolder%\gpsfdshp2mp.exe %%f "MP_TYPE" "NAME" n %dictionary_blank% !initialmapid! !finalmapname!
)
if "!filename:~0,7!" == "Polygon" (
%gpsfdshp2mpfolder%\gpsfdshp2mp.exe %%f "MP_TYPE" "NAME" n %dictionary_blank% !initialmapid! !finalmapname!
)
Change the NAME to whatever your column is called in the shapefile.

45
Map Making Support / Re: Questions regarding Part 9 Setup Files
« on: March 12, 2016, 12:06:54 PM »
Create a new text file and copy and paste all the content into it. Save that then rename it as a .nsi file and try to compile. It sounds like an encoding error. I'd attach a new one but I can't do it from this device so that won't be until Monday.

Pages: 1 2 [3] 4 5 ... 106
anything