Montana - Max User-Defined Line Styles

[CantGetLost]

What is maximum number of user defined linestyles Montana can handle?
I have been developing my custom line styles in Mapwel and I really like how it works but it gives me only 8 templates. I have seen somewhere that the device determines how many I can use. I need to make 12 custom types for current project. It would be great if Mapwel would expand the number just a bit.

[Boyd]

I was an early Mapwel adopter and have the advanced version but don't use it much. Mapwel's version of custom types, which they call "user defined styles" was what originally intereste me in Mapwel. Unfortunately, it is not completely compatible with all Garmin devices. IIRC, the problem is that they use non-standard types beyond the generally accepted (lowest common denominator) set. And the problem is made worse by the fact that Mapwel will not let you re-define a standard Garmin type, only the ones which are not pre-defined.

If you have the advanced version of Mapwel and want more control, I suggest saving your project without the custom styles. See "How to use IMG file from Mapwel with MapsetToolkit" here:

http://www.mapwel.net/manual/5000troublesht.htm

Use main menu >File >Properties > Map ID of Mapwel software tab to set user defined ID to map. Check 'User Defined' option and insert some 8 digits map ID number. This number must be unique among all maps in GPS. Check the 'Use as a file name' option.

On the same tab check the 'User Defined' map set data option. Select some Map Family ID and Product ID.

Uncheck 'User Defined Styles' in the map parameters tab in the same window to avoid merging of user styles file to the main map file.

Now you can use either TypWiz 3 or the online typ editor to create your custom types. They will let you redefine all of the standard typ's. You will find Typwiz3 to be very user-friendly, sort of like the Mapwel style editor.

http://pinns.co.uk/osm/ostyp.html
http://ati.land.cz/gps/typdecomp/editor.cgi

I think you need to stick with line types 0x01 through 0x2b. If Mapwel won't allow you to use some of these, the other solutions I mentioned will. See pages 117-118 of the cgpsmapper manual here for standard line definitions:

http://cgpsmapper.com/download/cGPSmapper-UsrMan-v02.5.pdf

(edited to fix bad URL's)

[CantGetLost]

Thanks. I do use TypWiz to compile custom POI's. POI developed in Mapwel (advanced) doesn't seem to work right in my Montana but I have never had problem with those out of TypWiz. Since I develop my *.img's out of Mapwel I was hoping to be able to have additional UDlines available through it to keep everything compact as possible. Maybe Mapwel can be badgered into giving us a few more definable linetypes.

[Boyd]

I don't think so. The standard linetypes are the ones I mentioned in the cgpsmapper manual. The additional ones are all non-standard (such as marine) and are usually a problem from my experience. But of course, the best way to know for sure is to make a small test map containing all the custom types you want to use. My experience is that the Mapwel custom type file is "weird". In the past, the most reliable and full-featured way to create custom types was the online editor that I linked to. Recently, typwiz has improved a lot though.

As I said, the real problem with Mapwel is that it doesn't allow you to redefine the standard types that you don't need. Typwiz doesn't have the limitation. If you are already using typwiz for POI's, I don't see why it would be any harder to also use it for lines.

[CantGetLost]

Thanks much. I will try your suggestions.