Global Mapper v26.0

Disappearing Area Features from Copy / Paste

Roger Edrinn
Roger Edrinn Global Mapper UserTrusted User
edited June 2010 in Bug Report
Today I've been working with two "identical" data sets downloaded from the USGS 3-years apart.

I one case I did a copy/paste of line elements -> User Created Features, then I moved the UCF to the proper line layer and after checking that the UCF layer was empty I deleted the UCF layer.

I short while later, did the same thing with two different area features. After checking that the UCF layer was empty, I deleted it. Then I did subsequent splitting of these areas.

After then doing more editing, I saved the entire workspace. Just now reopened my workspace and all copy/paste areas and sub-areas have disappeared, whereas all the copy/paste lines are intact. I checked Render Deleted Features, not there because my areas had names associated, the areas I found did not.

What happened???

Upon subsequent testing I can replicate the bug. Whether the splitting of the area is key, I know not. I just followed my copy/paste drill from above and the pasted area disappears after saving and reopening the workspace.

Comments

  • global_mapper
    global_mapper Administrator
    edited June 2010
    I was able to reproduce your issue and get it fixed. The problem was introduced with the recent change to keep split features in the same layer they were in rather than adding them to the UCF layer. I have placed a new build at http://www.globalmapper.com/global_mapper11.zip with the change for you to try. Simply download that file and extract the contents into your existing v11.xx installation folder to give it a try. If you are using the 64-bit version, there is a new build available at http://www.globalmapper.com/global_mapper11_64bit.zip .

    Let me know if I can be of further assistance.

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited June 2010
    This is turning into "my issue" from hell. With the latest build (June 1), GM seems incapable of now saving any changes to area features and loosing some from edit sessions days ago. I have split numerous areas and associated text names and area features types, all lost.

    This may/not be related to this thread.

    I've lost all confidence in GM to save an edit session in workspace format and am wondering how far back I have to go to recover lost work.

    From my perspective, saving correctly and completely is a crucial requirement of any software. You may brush this off as my issue but to me this is a Major Bug!!!
  • global_mapper
    global_mapper Administrator
    edited June 2010
    I think this is definitely related to your other thread, although I haven't yet been able to reproduce the issue. Do you always get the error from the other thread, or do they sometimes appear to save ok, but the changes don't come through? I agree this is a major bug and am working hard to fix it, but need to be able to reproduce it first.

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • global_mapper
    global_mapper Administrator
    edited June 2010
    As a possible workaround until I can reproduce and fix this issue, you should be able to export your data to a Global Mapper Package file in addition to saving as a workspace file so you'll have a separate backup copy.

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • global_mapper
    global_mapper Administrator
    edited June 2010
    I have been able to reproduce the issue and think it is now fixed. It was related to splitting areas in an existing layer that had islands. I have placed a new build at http://www.globalmapper.com/global_mapper11.zip with the change for you to try. Simply download that file and extract the contents into your existing v11.xx installation folder to give it a try. If you are using the 64-bit version, there is a new build available at http://www.globalmapper.com/global_mapper11_64bit.zip .

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited June 2010
    While your post says 6-5, the file said 6-8, perhaps that's just a generic link pointing to the latest build? Either way, a split and save resulted in the area being there upon open. That helps.

    Yes all my split areas likely have islands and it looks like I'll have to redo everything from the last two weeks. I have no idea how to find the all the split objects that were not saved. Unless I can undelete just these specific areas somehow? Interestingly, the original area is returned upon undelete, not the split segments.

    Any recovery suggestions would be appreciated.

    If I have to redo all those extents, then this request would sure help.
  • global_mapper
    global_mapper Administrator
    edited June 2010
    When you split an area the original area and islands should stay behind as a deleted feature, so you could enable the display of deleted features on the Vector Display tab of the Configuration dialog, then you will likely see the deleted areas showing through as the missing split areas wouldn't be there to cover them up. You can then select and undelete them.

    I'll try and get the other feature added today, not sure how that slipped through the cracks.

    Thanks,

    Mike
    Global Mapper Support
    support@globalmapper.com
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited June 2010
    Undelete certainly works, it was finding the deleted areas that was the issue. Needle in a hay stack. Turns out I can turnoff the line layer which removes 90% of the clutter. Can I change the deleted feature color too? That would help a lot.
  • Roger Edrinn
    Roger Edrinn Global Mapper User Trusted User
    edited June 2010
    I was able to change an existing area to make its border the same color as the fill, that eliminated the visual conflict with undeleted areas. So coupled with the turning off of lines, I now have a workable recovery process. Best of all, save works. :)