MP Export Error

[Roger Edrinn]

I've attached two shape files: Cities and Public Lands. No matter how I combine them, import into GM, export to a single shapefile, combine in a GM package file, use in a workspace, these two files only render the city areas when exported to MP.

In opening the MP file, one sets the TYPE= as State, City i.e. some alpha string, while the other sets TYPE=0x02 a hex string.

In looking at the MP_Type attribute, all are vacant, hence GM should default to its MP_TYPE values. Correct?

Suggestions?

Thanks

[global_mapper]

Roger,

The problem is that the Shapefiles do not have an inherent classification, so unless the LAYER attribute found in those Shapefiles matches the name of an area type in Global Mapper, the areas are assigned the type 'Unknown Area Type'. Any types that do not have a built-in default MP_TYPE mapping (such as 'Unknown Area Type') just write out the description for the type/feature as the TYPE= value in the exported MP file so that users can modify their RgnType.txt file to add new type assignments for cGPSMapper. If cGPSMapper does not find a text match, I believe that they now discard the features (I think they use to write them out as an unknown type which some units would still render).

What I would suggest is using the Search->Search by Attributes menu command to search on the different LAYER attributes found in the public lands file and edit the matching features for a particular LAYER value to either be of some built-in type with an automatic MP_TYPE assignment (like one of the park types) or manually add your own MP_TYPE attribute to those features to provide the type assignment that you want.

Let me know if I can be of further assistance.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

[Roger Edrinn]

Mike,

Thanks for straightening me out. Now at least I know what is wrong. The fix is actually fairly easy.

Thanks again

[Roger Edrinn]

Still puzzled by why GM did not assign the correct MP_TYPE to some of the areas. For example, GM knows what a National Forest and National Park is. What happened?

I did as you suggested and assigned an MP_TYPE to all know areas, any unknown area was deleted. The net result, all the areas showed correctly. However, a little mystery. Rocky Mtn NP, a very large area only showed when zoomed in, strange.

Another benefit, 095a no longer errors. Apparently it doesn't want to see TYPE=text, needs to see a hex string.

Thanks for the help.

[global_mapper]

If there are already area types with a name that match the LAYER attribute from the Shapefiles, then those types will be automatically assigned. Since there is a 'National Park' area type, any features with a LAYER attribute value of 'National Park' got auto-assigned. You can set up auto-assignment on load this way simply by adding new custom area types with names matching the LAYER attribute value from the Shapefiles.

Let me know if I can be of further assistance.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

[Roger Edrinn]

I think you're not understanding me.

I opened the raw shapefile and went through every area and assigned both the correct name <Feature Name> and <Feature Type> selecting the default area for each type. For non-standard area types, new ones I created, each had been previously assigned a specific unique MP_TYPE.

I then exported those area vectors to a new shapefile, the one attached. I used the same process for the cities, it worked.

So I wasn't looking for GM to auto assign anything. I had already done the heavy lifting, yet GM didn't retain that knowledge and export the hex TYPE= value.

What am I missing?

Thanks

[global_mapper]

What options did you select when exporting the Shapefile from Global Mapper? Did you select the option to 'Add Feature Type (LAYER) Attribute to DBF'?

Here again I might recommend using Package files as it has built-in support for all of the type and styling information used in Global Mapper and doesn't have to base everything off a generic set of attributes, which may be ambiguous in some cases.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

[Roger Edrinn]

I used the default Shapefile export settings and selected export all, no cropping.

I have one problem with the package file export. When I open it, rather than seeing the name of the package file in the Control Center, I see all the source files. FWIW, I'd much rather see just the package file name and use the options menu to see the source files.

Thanks

[global_mapper]

If you check the box to 'Add Feature Type' when exporting your Shapefile then the types should be maintained perfectly. This option is not checked by default.

Let me know if I can be of further assistance.

Thanks,

Mike
Global Mapper Support
support@globalmapper.com

[Roger Edrinn]

Originally Posted by global_mapper

If you check the box to 'Add Feature Type' when exporting your Shapefile then the types should be maintained perfectly. This option is not checked by default.

On the File Selection tab of the Shapefile Export Options dialog, the third of four switches reads:
Add Feature Type (LAYER) Attribute to DBF
That box is checked when I open the dialog, not so with your version?
I have v9.03 April 27

So assuming the actual version I used, a least a half-dozen upgrades in the last two weeks, was also checked? Then if I understand correctly, the problem I experienced should not have happened?

Thanks