MP_TYPE not "Sticking"?

Roger Edrinn
Roger Edrinn Global Mapper UserTrusted User
edited May 2009 in Vector Data
I'm having problems with the 095a compiler failing because GM is exporting MP code as a literal instead of a hex value.

More details:
I've got an infrequent Ftype = DamWeir, I've selected all of these features and given them a Feature Type = Dam. Using the Search Vector Data dialog, I've Selected ALL, Edit Selected, in Feature Attributes I added a new attribute: MP_TYPE with a value of 0x13.

I can select any of the 100's of features in the search dialog and sure enough they all have an MP_TYPE feature set to 0x13. This statement is incorrect, if I select an individual line, the MP_TYPE attribute is not there, What the ...???

However, if I use the Feature Info Tool and select the same feature on the map, the Feature Info dialog shows no MP_TYPE attribute.

When I do an MP export, Type is set to: Type=Dam, [not Type=0x13] which causes the compiler to error.

What causes the difference between the two search dialogs? What am I doing wrong?

Comments

  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited May 2009
    Looks like we've been down this road before and I might be using the wrong GM version. This Thread.

    I dealing with areas now, whereas the older thread was dealing with MP points. I'm using a much later version of GM than that thread.
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited May 2009
    I suspect that my problem is related to the fact? that GM has a default area type defined for "Dam" and I'm trying to overwrite it with a new MP_TYPE attribute. I'll do some testing.
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited May 2009
    Totally clueless as to why, but ......

    I deleted the MP_TYPE atribute from Dam, tested the MP export, still got Type=Dam. I then selected all the dam Dams again, re-added the MP_TYPE attribute, 0x13, and it worked. MP export is now Type=0x13.

    Go figure!!!
  • global_mapper
    global_mapper Administrator
    edited May 2009
    I'm not sure what is going on, but I would suggest rather than editing your 'Dam' type features individually, simply go to the appropriate Styles type of the Configuration dialog, selecting your 'Dam' type, pressing Attributes, then adding the MP_TYPE attribute with a value of 0x13 there. This will provide a default MP_TYPE assignment for your type so you don't need to add it to your individual features (unless you want to override the default assignment).

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited May 2009
    I've tried that with another feature type and it didn't work. It could be related to the "confusion" of having a few set but not all. Seems deleted all the attributes then re-entering them in mass had benefits.

    I've re-exported my package files for the dozenth time and am now processing with the compiler the new .mp files from all the layers. So far - so good. :)

    Thanks

Categories

In this Discussion