.mp conversion to .img

lonewatie

When I convert my .mp files (mainly contours for now) to .img using the export to .mp then using cgpsmapper, and subsequently import them into my mapsource using mapsettoolkit, and then view them in mapsource, there are a lot of square grid lines which are unsightly. Any suggestions on getting rid of these as they are not part of the original export to mp then img. Also, when I create polygons such as the outline of an airport, the polygon doesn't ultimately show up in mapsource, leading me to believe that its because of the zero value in the shape file not being converted .img properly. The polygon shows up in gpsmapedit, but doesn't convert to .img using cgpsmapper. I'm having trouble finding any threads on this topic, any suggestions would be great. Thanks.

Roger Edrinn

Global Mapper exports everything you see, including grid lines. So turn off the grid line before exporting to MP.

Using the Configuration dialog do either:
- General tab check "No Grid" or a cool GM feature,
- Vector Display tab > Filter > create and save custom Areas, Lines, Points filters as to which are on/off prior to export to MP or any other export type.

global_mapper

I think Roger covered the grid issue. For the polygons not showing up, make sure that you either assign your new area features to a type in Global Mapper that either has a built-in conversion to an MP_TYPE or that you have explicitly added a MP_TYPE attribute value for in the default attribute list for that type. Otherwise Global Mapper won't know how to convert the feature to a Garmin classification on export.

You might also read the great tutorial on creating maps with Global Mapper and cGPSMapper at http://www.globalmapper.com/helpv9/cGPSMapper.pdf. It covers this issue.

Let me know if I can be of further assistance.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

lonewatie

I did what you suggested concerning turning off the grid, which, far as I can tell, is the default. I still came up with the grids in mapsource. I attached a pdf of the three screen shots, starting with global mapper, then mapedit, then lastly, mapsource final product. Thanks for the quick reply earlier, I'm sure there's an easy explanation for what I'm doing wrong here, and can't wait to find out.


I want to add, for troubleshooting this, the procedures I'm using. I'm downloading US Elevation Data 30m resolution for 1 mile within a zip code I used. I then generate the contours with the default interval of 10 feet for that zip code. The no gridding tab is checked in the contour generation options 'gridding' tab, and no gridding is again checked for the export to polish. For the export/conversion to img, I am using the drag and drop of the file onto the command prompt box, but even when I use the windows mapedit box, I get the same results. For the export to mapsource, I am using mapset toolkit, and simply following the directions on that. Thanks in advance for any help/suggestions.

Roger Edrinn

Not sure, but some thoughts from your post:

What/why is Mapedit? The GM MP file can be directly processed by cgpsmapper to an img file.

When you speak of grid lines in the img file and gridding the export in GM, two totally different uses of the term grid. For the term gridding GM output,it simple means to output into smaller blocks, usually via rows and columns vs. a single export block. These smaller blocks are necessary mostly for memory constraints. When I create contours for an entire state, the PC would never finish if I did not grid into small enough blocks. Even then it takes days.

global_mapper

The grid lines that you mentioned are not what I was expecting. Both the original Global Mapper display and the GPSMapedit do not have those artifacts, so I suspect that something is happening either during the generation of the map with cGPSMapper or with the 'mapset' toolkit that you are using. If you can send me the .mp file and the .img that it generates I can take a look and see what is up.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

lonewatie

Roger Edrinn wrote: »

Not sure, but some thoughts from your post:

What/why is Mapedit? The GM MP file can be directly processed by cgpsmapper to an img file.

When you speak of grid lines in the img file and gridding the export in GM, two totally different uses of the term grid. For the term gridding GM output,it simple means to output into smaller blocks, usually via rows and columns vs. a single export block. These smaller blocks are necessary mostly for memory constraints. When I create contours for an entire state, the PC would never finish if I did not grid into small enough blocks. Even then it takes days.

The mapedit really has nothing to do with the process, I simply added the screen shot to show that the grids weren't there. Sorry for the confusion, I do, in fact, convert using cgpsmapper to img. gpsmapedit is a 'free' program that allows manipulation of the zoom levels. Mike, i'll post the files for you to look at. I appreciate the quick responses.

lonewatie

Mike, I emailed the files to you.

global_mapper

Thanks for the files. I took a look at both the MP and IMG files, and neither contained the grid artifacts that you are seeing. This means that the problem is either in MapSource's rendering of your data file or in something that the 'mapset' application is doing to get the data into MapSource. Can you try putting your .img file on your Garmin unit and see if it looks ok there?

Thanks,

Mike
Global Mapper Support
support@globalmapper.com