Hi all
I have been making my own custom maps with cGPSmapper for many years
I have 4 custom maps I update all the time and then reload them into the GPS
I have always used sendmap20 to load all 4 maps at one time into my Map76cs
10000000.img, 20000000.img, 30000000.img, 40000000.img
40000000.img is a huge topo map that I don't turn on until I need it.
In my Map76cs all four maps showed up as individual maps and I can uncheck a box to turn each one on and off.
I just got an Oregon 450 yesterday.
I loaded all 4 custom maps using the exact same method I use on the Map76cs.
The problem is that in the map setup screen, it only shows one big map, not 4 maps.
All four are always on in the Oregon.
Below you can see a screenshot of just one custom amp, even though I loaded 4 at the same time.
How do you load the maps so that they all show up as individual maps on the map setup screen?
Thanks for any help
I'm pretty sure that that is not going to work with the Oregon the same as the 76, the Oregon will group maps even when sent as separate files by map FID. You might have to build out installers for the separate layers.
Hi thanks,
I am not sure what this means?
Quotebuild out installers for the separate layers
It should be even easier on your Oregon and no software is even required. Just copy those four files exactly as shown to the Garmin folder on your Oregon. Do not use Sendmap. When the Oregon starts up, you should see each .img file separately and enable/disable it as you like.
Your old unit will only recognize an .img file named gmapsupp.img. The Oregon recognizes any file with an .img extension. When you use sendmap20 on the newer units, it behaves as you describe and groups them all into one item named "maps uploaded with Sendmap20".
BTW, you now need to change your terminology. Garmin has redefined the term "custom map" to mean raster imagery enclosed as .jpg files within a compressed .kmz archive. I know that many of us used this term previously to describe any map we made ourselves, but using it today will just confuse people.
Welcome to Garmin's new world. ;D
cool, going to try it right now
I'll be back :)
Quote from: Boyd on August 30, 2011, 12:29:30 PM
It should be even easier on your Oregon and no software is even required. Just copy those four files exactly as shown to the Garmin folder on your Oregon. Do not use Sendmap. When the Oregon starts up, you should see each .img file separately and enable/disable it as you like.
Yes, that might work. Give that a shot first and let us know how it works for you.
Ok, that worked
I had searched the web for a long time and did not see that info anywhere.
Ok, so Loading maps with sendmap combines all the maps and saves that as GMAPSUPP.IMG
Copying individual .img files to the Garmin folder lets you select them individually in the Oregon.
One thing I noticed is that the maps do not seem to combine on the screen into the same layer.
One of the maps I downloaded off the web lays on top of all my maps and covers them up.
I supposed that has to do with how that map was created?
All my maps merged onto the same layer in my Map76cs
Thanks so much for the info guys. (gals) :)
Each map has a draw order value between 0 and 31 that determines how they will stack (maps drawn later cover up the earlier drawn maps). Maps can also have transparent backgrounds, allowing you to see the one(s) underneath.
There are various ways to control this behavior. The program gmaptool is one way. Or you can set these parameters in the Properties dialog in gpsmapedit. You can probably also hand edit the header of the .mp file and put them there, although I haven't done it directly myself. For a quick fix, gmaptool might be the easiest way - do a google search for it. Actually it's probably the only way if you don't have the original source file.
The grouping of maps is controlled by the FID (Family ID) number, as Indrid alluded to. When you use Sendmap, it sets the same FID for every map it creates, so they get grouped. You could manually change this value also, in similar ways to what I described above.
Excellent info, thanks so much
I've got some things to sort out now I guess.
Another thing I noticed is that my topo map had thin black lines in my Map76cs and were easy to see against the light brown background.
The lines are white in the Oregon and hard to see against the light brown background.
I re-did the topo map in cGPSmapper with a different RGN40 type and they still are white.
In Mapedit my topo map lines show up as brown contour lines and can be seen very well.
???
The best way to control the appearance of the map elements is to use a custom .typ file. This will force the map to look virtually the same regardless of the device. It adds more complexity however because it involves bundling the .typ file the map file(s). Sendmap20 can do this. But for full mapsource compatibility you probably want to use MapsetToolKit. I found this all very confusing at first myself. :)
For the basic concept of custom types, see the tutorial here starting on page 33: http://cgpsmapper.com/download/GM8DocV2.pdf
After reading, you can forget all the stuff about creating the text file and compiling it. Instead, you can use the user-friendly online editor here: http://ati.land.cz/gps/typdecomp/editor.cgi
Click the Create tab to start with a "clean" file. Changing the background color and elevation contour appearance is very simple once you grasp the concept.
I am getting nowhere with creating a custom .typ file and having it work as expected in the Oregon 450.
I created a simple .typ file in the editor http://ati.land.cz/gps/typdecomp/editor.cgi
The .typ file only defines one thin contour line 0x20 that is used in my topo map.
I made the line color red and added some text (topo) so I could tell if the lines were different in the GPS
I created a combined .img + .typ file with sendmap20.
I loaded the .img file into the Oregon and enabled it. The topo map lines are still white. >:(
I loaded the same exact .img file into my Map76cs and the topo lines are red and my text shows up next to all the topo lines.
So there is nothing wrong with the .img file.
What the heck is the problem with the Oregon?
Does it not respond to .typ files?
It works fine on the Oregon, I have used custom type files extensively. But sometimes it doesn't work to do this with Sendmap 20. For example, this kind of file will sometimes make my Nuvi 3790 freeze and fail to complete the boot process. I have an Oregon 400t, and have not seen this problem, but since the 450 is newer it may share the odd behavior of the 3790. I suggest that you use any test maps on a card instead of internal memory, because if this happens with a file in internal memory you could have a big problem but with a card you can just remove it.
If I create a mapset using the "correct" method with mapsettoolkit, it always seems to work. That should probably be your next stop since it will also display your map in Mapsource with the custom types. http://sites.google.com/site/cypherman1/
It may take a little while to understand how this works initially, but here's a quick overview. Create a folder and put the .img file(s) and .typ file inside. Choose that folder using the Select IMG button. Click select all and Add so the files are listed on the upper right under Selected IMG files.
Choose this same folder in the Mapset Directory box. Give the mapset any name you like. Make up a number for Family ID an leave Product Code alone (defaults to 1). Version and copyright can be whatever you like. Draw priority was discussed above.
In the TYP file box, choose the file you created with the online editor. It is already compiled so don't click that button. Check the boxes that say Install in Mapsource and Blank Overview Maps. Now click Start and if you did everything correctly the mapset will be installed into Mapsource. You computer may give you a warning about the program trying to modify the registry, so you will need to approve that. Note that when the installation is successful you get the confusing message "Convert termined" (the program author is not a native English speaker :))
Now you can use mapsource to view the mapset and the results of your .typ file. If you like it, send it to your GPS as you normally would in Mapsource. If you make further changes to the mapset you will need to uninstall/reinstall.
Doing this will eliminate any of the weirdness related to Sendmap20. Others have also noted these issues here.
Hi Boyd and thanks
I don't have Mapsource
The only files I use to create maps cgpsmapper, mapedit and sendmap
I have tried uploading the map two ways and both are no go in the Oregon
Both methods still show white topo lines.
Using sendmap20 to create the GMAPSUPP.img in the Oregon
Copying the .img file directly into the Garmin folder on the Oregon.
Again, this same file works correctly in the Map76cs, so I know the .typ file is working.
the .typ file is part of the custom .img file, I can see that it is inside by loading the file back into sendmap
Mapsource is free and should be a basic program for everyone with a Garmin handheld. It is used to install almost all of the maps on this website. See this: http://www.gpsfiledepot.com/tutorials/how-to-install-mapsource-if-it-didnt-come-with-your-gps/
All I can do is share my own experience and tell you what has and has not worked for me. If it doesn't suit your needs, maybe somebody else can help.
Thanks,
It says this on the Garmin site about mapsource
Quote◦WARNING: This software will not work unless you already own a MapSource product.
Quote from: EL34 on August 31, 2011, 11:08:44 AM
I am getting nowhere with creating a custom .typ file and having it work as expected in the Oregon 450.
I created a simple .typ file in the editor http://ati.land.cz/gps/typdecomp/editor.cgi
The .typ file only defines one thin contour line 0x20 that is used in my topo map.
I made the line color red and added some text (topo) so I could tell if the lines were different in the GPS
I created a combined .img + .typ file with sendmap20.
I loaded the .img file into the Oregon and enabled it. The topo map lines are still white. >:(
I loaded the same exact .img file into my Map76cs and the topo lines are red and my text shows up next to all the topo lines.
So there is nothing wrong with the .img file.
What the heck is the problem with the Oregon?
Does it not respond to .typ files?
I had a similar color problem generating TYP files with cgpsmapper and sending them to my OR300 using Sendmap 2.0.
The problem went away when I used MapSetToolKit to bind the TYP to the mapset and MapSource to send the mapset to my OR.
Also, it might help to read the section on TYP files in the cgpsmapper manual.
Hi Seldom,
QuoteI had a similar color problem generating TYP files with cgpsmapper and sending them to my OR300 using Sendmap 2.0.
I generated my .typ file using the editor at the web link that boyd provided above, not cgpsmapper.
I
am not sending the .img file to the Oregon using sendmap, I am copying the file into the Garmin folder.
The file works fine in my Map76cs but not the Oregon, so I know the .typ file is bound to the .img file and works on one of my garmins.
I will check out MapSetToolKit.
I actually may have a very old mapsource disk that came with my first gps somewhere.
QuoteAlso, it might help to read the section on TYP files in the cgpsmapper manual
thanks, did that already. Printed out on paper and read it.
I'll get back on this in the morning and see what I can come up with.
The easy way to get MapSource to run is to download BaseCamp and install it first. Once you have BaseCamp, you don't really need MapSource unless you like the old interface.
Quote from: EL34 on August 31, 2011, 01:46:38 PMI am not sending the .img file to the Oregon using sendmap, I am copying the file into the Garmin folder.
This makes no difference one way or the other. The issue has something to do with the way Sendmap creates the gmapsupp.img file and not how it was sent to the device.
QuoteThis makes no difference one way or the other. The issue has something to do with the way Sendmap creates the gmapsupp.img file and not how it was sent to the device.
Yes, that's my thought also.
But, something must be different between Garmins, because the file works fine on one Garmin but not the Oregon.
I am thinking that it has to do with the Oregon charcter sets/bitmaps or something.
My custom maps all look different in the Oregon
The tracks, the lines, the water, etc all look slightly different.
Will not be able to mess with it again until tomorrow -thursday.
Ah, well if this is your first new Garmin product since the 76 series, a lot has changed. ;D
I have found best way to get consistent results across many different models is to use bitmapped custom types. Things like text style are hardcoded into the devices and can't be altered by the maps we make, although you can choose text size in the online editor.
Here's the project I'm working on now on the Oregon, 60csx (like your 76) and Nuvi 205. Aside from font style and screen resolution, I think the results are pretty consistent. The older models like the 60csx only have 8 bit color depth which also leads to some variation.
(http://stephencreek.com/gpsfd/2012typ.png)
You do NOT need a typ file on the OR 450 for contour lines. The default without a typ file is a brown line that shows up good on the map.
Take a look at the screen shots for My Trails (link on the main page under most downloaded). The topo lines in those screen shots are the default display on the OR 450/550). The screen shots show what you get without a typ file. If your topo lines are showin white, something else is messed up. Maybe you have the wrong type assigned to them.
Hmmm, ok, but they are brown in my Map76cs and white in the Oregon using the same exact file
This is why I am scratching my head - see screen shot from Oregon
see the full list of RGN40 types down below from the cgpsmapper RGNtype.txt file
I am using this element for topo lines
RgnType=0x40
Type=0x20 - Land Contour (thin)
Here is a sample text file that is used to create the topo line maps using cgpsmapper
[IMG ID]
ID=40000000
Name=Topo....
Datum=W84
TreSize=2000
RgnLimit=1024
Levels=4
Level0=24
Level1=23
Level2=20
Level3=18
[END-IMG ID]
;RGN40 Topo, Land Contour (thin)
[PLT]
RgnType=0x40
Type=0x20
Label=
EndLevel=0
FILE0=Y:\My Documents\GPS\Data\NC\Topo\TopoB5.plt
[END-PLT]
From the cgpsmapper RGNtype.txt file
[RGN40 types]
0x01 Major HWY thick
0x02 Principal HWY-thick
0x03 Principal HWY-medium
0x04 Arterial Road -medium
0x05 Arterial Road-thick
0x06 Road-thin
0x07 Alley-thick
0x08 Ramp
0x09 Ramp
0x0a Unpaved Road-thin
0x0b Major HWY Connector-thick
0x0c Roundabout
0x14 Railroad
0x15 Shoreline
0x16 Trail
0x18 Stream-thin
0x19 Time-Zone
0x1a Ferry
0x1b Ferry
0x1c Political Boundary
0x1d County Boundary
0x1e Intl. Boundary
0x1f River
0x20 Land Contour (thin) Height in feet
0x21 Land Contour (medium) Height in feet
0x22 Land Contour (thick) Height in feet
0x23 Depth Contour (thin) Depth in feet
0x24 Depth Contour (medium) Depth in feet
0x25 Depth Contour (thick) Depth in feet
0x26 Intermittent River
0x27 Airport Runway
0x28 Pipeline
0x29 Powerline
0x2a Marine Boundary (no line)
0x2b Marine Hazard (no line)
[END-RGN40 types]
Haaa... , nailed it
I changed some things in my cgpsmapper header file and now the topo lines are brown.
Although I don't quite understand which setting is responsible.
Maybe someone with a better understanding of it all can explain?
Before header
[IMG ID]
ID=40000000
Name=Topo....
Datum=W84
TreSize=2000
RgnLimit=1024
Levels=4
Level0=24
Level1=23
Level2=20
Level3=18
[END-IMG ID]
After header
[IMG ID]
ID=60000000
Name=Topo....
Datum=W84
Preprocess=G
TreSize=1000
TreMargin=0.00000
RgnLimit=1024
Transparent=Y
POIIndex=Y
Copyright=Doug Hoffman
DrawPriority=1
Levels=4
Level0=24
Level1=23
Level2=20
Level3=18
Zoom0=0
Zoom1=1
Zoom2=2
Zoom3=3
[END-IMG ID]
Before and after screen shots
MapSource will recognize the map included with BaseCamp as a MapSource product.
Try setting the OR450 to not display elevation data. This changes the background from tan to off-white. Garmin is doing some 'weird' things with the newer units - some feature colors are different on the newer units than what was used on the older units. Also some feature types seams to be 'fixed' in the GPSr and a custom .typ file will not change these.
Also check you profile to be sure it is on recreational - some of the included profiles make unexpected changes to the display.
Hi,
As was said above, I don't use mapsource, don't really need it.
All my custom maps come from usgs dem24k data and also Ozi-Exporer track and waypoint files.
cgpsmapper works just fine for creating those type of maps from raw data.
It is all ok now , see my post and screen shots right above this one.