Messages

Never mind, I figured out that I had a couple of Highlight option checked, that was the problem.

Hi,

I just upgraded from version 1 to version 2.1, and my types are not displayed correctly.
- for any POI icon, the background appears red instead of transparent;
- all lines are only basic single lines.
All types appear correctly in the selection box, but not on the map.
Any idea?

Thanks, this is quite clear.

Hi,

I have designed a new map using GPSMapEdit, and uploaded it in my Nuvi 1370 using BaseCamp, etc.
Now I can see my map in a subdirectory map/gmapsupp.img

If I want to give this map to some friend, can I just send him the file so he can copy it into his Nuvi, or do I have absolutely to use BaseCamp again on his unit?

Thanks.

Go to the following tutorial and scroll down to the GPSMapEdit header for the instructions:

Ok, I will try this. Thanks.
The tutorial also shows instructions for Global Mapper.
Which one is the best?

>>define the other levels and add a dictionary header is the easiest way.

I'm using GPSMapEdit, I don't see support for dictionnaries.
I can define levels, that's it.

>>or you can let cgpsmapper do it if you can live with it's algorithm.

I have about 5000 roads and land contours, So I thing I'll let it do it.
Then, how do I get cgpsmapper to do it ?

Hi,

I have a map in GPSMapEdit, export it in Garmin format, install it in BaseCamp with cGPSMapper, finally install it into my Garmin with BaseCamp.
All elements are defined in level 0.

Question: who is in charge in this process for defining simplified version of lines and polygons to be used for levels 1, 2,...?
- Myself im GPSMapEdit?
- GPSMapEdit?
- cGPSMapper?
- BaseCamp?

>>Why are you defining in gpsmapedit?

I don't define them in GPSMapEdit, I define them in a text file. I use them in GPSMapEdit which I use to design my map.
I found the problem: there was errors in my type definition, the problem with GPSMapEdit is that if there is anything wrong with the type declaration, it just ignores it, no erreor message no nothing.
Also, when I copied an example from the pdf manual, I didn't notice that a space was represented by a tab character, another detail that GPSMapEdit did not like.

To get GPSmapedit to resemble (not very well) the TYP file you have created you need to have GPSmapedit associate with a "skin". 

This is exactly what I do, I know what to do, if I'm asking questions here, it is because it doesn't work.
I've generated a txt file which contains what I have quoted in my first message, associated the file to a skin in GPSMapEdit. Unfortunately, the program does not make the type available for edition.

You should read the section on TYP files in the cgpsmapper manual.  TYP files are the accepted way of customizing polylines, polygons, and points.

I've read, and done exactly like it says. I even picked up the example, but GPSMapEdit won't display the example as it should.
Another thing I noticed:
One can define new types to be used in GPSMapEdit, they will work, but once evrything transfered in Garmin, the elements having those types wont show.
Only modified existing types can be see in Garmin.

Hi,

Has anyone been succesful in defining custom types for polylines in GPSMapEdit ?
For instance, I have the following declaration:

Code Select Expand

[_line]
Type=0x2c
UseOrientation=Y
String1=0x04,Unpaved
String2=0x01,Chemin VTT
XPM="8 8 4 1"
" c none"
", c #ffffff"
". c #000000"
"X c #ff0000"
" "
" "
"........"
"XXXX,,,,"
"XXXX,,,,"
"........"
" "
" "
[end]

Problems:
1º it seems that no definition is accepted if the image is not in a sqare (same nb of pixels for X and Y)
2º Here, the transparent color is not transparent but white
3º no rotation of the image is performed (see image)


Mod note: please use the code tags when posting code, K?

>> jbensman talked about Alt-0.

Sorry, I didn't notice. He may have reassigned his keys.

but I can't get Alt-0 to work w/ my version of GPSmapedit

We talked about Ctrl-0 here, not Alt-0.

What are you doing?

As I said, I just added a polyline with type Boundary, nothing special.
But I think I see the problem.
If one zoom out the map while in level 0, it remains at level 0, fine.
However, when you close and re-open the map, the map opens at the same zoom factor, BUT the level is not set the same as when the map was closed: the level is set at a value depending on the zoom factor.
Another thing to know:
When the file is opened, the zoom level adjusts automatically to the zoom factor.
But when a specific level is selected (ie: Ctrl-0), it remains set whatever the zoom factor is.

SO: always set the zoom level to the desired level after opening a map.