Messages

Thank you, Red90, I am going to read the manual again tomorrow

Horse Rider, I will try that with my next install... I have been checking that box 'Just to be sure'

Is the map transparent?  If so, they will only route on the GPS.

Yes, it is! Can you please elaborate further on this behavior? How did you learn about this?

Recently, I have started to play with adding routing information to my maps using GPSMapEdit:

I will save my map in current configuration (*.mp) and select 'Tools > Verify Map...'. I will get a list of several hundred errors, and I will spend hours correcting each error until the 'Verify Map' process no longer returns a single error. I can then save the map (*.mp) as is, and run the map verification at will, returning zero errors each time.

However, If I re-run the 'Tools > Generate Routing Graph' function, and then re-run the map verification, I will again be presented with hundreds of errors, many of which appear to be duplicates from the previous verification.

After about the third time around, I did not save the new *.mp mapset, and undid ('ctrl-Z') the new routing graph. Now verification result sin zero errors.

Why do all these errors reappear after running the 'Routing Graph Generator' again? I have not changed any data in the map between.

I assume I must run the 'Routing Graph Generator' after any map edits for the map to be exported with complete and accurate routing information.

If any of GPSFileDepots master map makers familiar with this process would be so kind as to offer advice, i would be very grateful!

I have been slowly building several mapsets over the past few months, learning everything by trial and error, with the help and support of a few expert map makers here at GPSFileDepot.

Using GPSMapEdit, I have verified, corrected thousands of irregularities, generated routing graphs, and tested routing graphs on some of my maps. All of my map data is at Level 0, which is set to 24 bit detail.

I then export from GPSMapEdit to *.img file (with *.idx), and use MSTK to load the mapset into BaseCamp/MapSource. ALL the cGPSmapper routing settings are enabled in the map information tab in GPSMapEdit.

I have been able to routinely install/uninstall maps for BaseCamp with MSTK without issue for some time, so I feel I have this figured out.... but:

BaseCamp/MapSource refuse to recognize any routing capabilities in my maps. That is to say, I can not get BaseCamp/MapSource to use trails/roads/etc regardless of routing settings. Sending the map to my GPSr, MapSource allows me to check the 'Send Routing Data' box, so I assume it knows routing data is present, but the resulting mapset on my GPSr also refuses to allow routing along streets/trails/etc.

Do any of our expert map makers know how/where the routing information is stored/enabled? I know a couple map makers here have routable maps available, so I assume they may have overcome this issue already.

Yes, I do have the routable version of cGPSmapper. In fact, looking around the cGPSmapper website for potential answers, I found the SendMap20 application provided there, and installed it for testing purposes.

The reason I use MSTK to install my map into BC/MS is twofold: 1> To review map content and accuracy, and 2> MSTK allows me to apply my custom TYP to the map during installation. When everything looks good in BC, I then send the mapset to my GPSr, where I also review for content and accuracy on the device.

Combining my GPSMapEdit/cGPSmapper *.img file with the desired TYP file in SendMap20, I can produce a new *.img file for use with the GPSr. This map, when loaded onto my Garmin GPSr, ALLOWS ROUTING along the streets/trails/etc in my map. I even went so far as to remove all other maps from my GPSr to ensure the routing was indeed occurring based on the data in my mapset.

So, is MSTK not capable of sending routing information along when present?

I adjusted the mapset on my GPSr to be available in BaseCamp, enabled it in BaseCamp (read directly from the connected GPSr), and BaseCamp still refuses to allow routing, while the GPSr can and does use the routing information in the mapset.

I have not yet constructed a full BaseCamp installer for my mapset, and perhaps this is the only way to get routing data into BC/MS? Or maybe I am just missing something somewhere else along the way.

scdiscdi, under what circumstances will 0x11 0x12 0x13 crash Mapsource?

Thank you!

This opens up more options to me

If I use known types for my map, will that change how other maps loaded on the same GPSr show that line, or do my TYP files only affect my maps?

I have opened GDB files with BaseCamp in the past.

One site says the .KMZ should simply be copied to the \Garmin\Custom Maps folder on the device...which I've tried, but see no results.

...but so far nothing makes them show up on the GPS itself.

Can anyone give me advice?

Thanks, J

Try \Garmin\Custommaps\ (no space)

Thank you, Popej, this is fantastic information!

How so, did the op finally disable his City Navigator and discover his TOPO maps?

Well now, I don't think we will know that until the OP tells us.

Meanwhile, another user posted some very useful information, and I thanked them for it.

Thank you, Popej, this is fantastic information!

Anyone familiar with any potential conflicts with custom TYP 0x17 polylines?

I am using them for bridle trails in my maps, and they are displayed properly on my various Garmin GPS receivers, but they do not display properly in BaseCamp or MapSource.  When I mouse over them in BC/MS, the trail name is displayed, so the trail is present, but BC/MS both refuse to display my custom TYP 0x17. I have checked to be sure the colors used are 'Garmin Colors', and as I said, they show just fine on my Garmin GPSr.

Any and all input much appreciated.

However, besides SD county what of trail data sources for the other 3,233 county or county equivalents in the US states and territories?

Between Jon Stanley's Northwest Trails, Jim Bensman's My Trails (covers complete Eastern US), and my Southwest Trails, I believe any user in the US looking for trail maps will find the coverage they desire.

Unfortunately 6 years of experience has shown that there is no way that a mapset will satisfy everyone's needs.  As Boyd's posts have mentioned for the past two years, even Garmin's own mapsets can display radically differently depending on which of their GPSr models it is displayed on.

Agreed! No single map can satisfy every user!

How about 30-40 users becoming active map authors for one or two states each?

Well, I have begun the incredible learning curve to do just that. I am working on trail maps for the Southwest USA (very hard to get good data), which will be followed by a topo version of the same. So I guess you could say I am putting my money where my mouth is

http://www.gpsfiledepot.com/maps/view/715

Montana will function with uSD cards up to 64GB in size. The issue is not your Montana, but your uSD card. I suspect it is not properly formatted in FAT32 (not exFAT).