Create New Layer for selection - error

RobertRRobertR GlobalMapper Fan!Posts: 286Trusted User
edited November 2012 in Bug Report
Hello,

I noticed a strange thing when performing this operation. All I am doing is to select a bunch of features and move them into a new layer.

The problem is that in the Overlay Control Center I have a number of:
-original layer: 202482 features, 48433 Deleted (in my case, moved to a new layer);
-new created layer: 47963 (I was expecting 48433)

Where did the rest of them go? :)

Thank you,

Comments

  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited September 2012
    Did any of the areas have islands/holes? If so that could explain the discrepancy as each island could have been counted as deleted. I see where this can happen and will fix it.

    Thanks,

    Mike
    Global Mapper Guru
    gmsupport@bluemarblegeo.com
    http://www.globalmapper.com
  • RobertRRobertR GlobalMapper Fan! Posts: 286Trusted User
    edited October 2012
    Did any of the areas have islands/holes? If so that could explain the discrepancy as each island could have been counted as deleted. I see where this can happen and will fix it.

    Thanks,

    Mike
    Global Mapper Guru
    gmsupport@bluemarblegeo.com
    http://www.globalmapper.com

    Yes, it is possible that they had holes, indeed. I dunno, maybe it would be for the best to keep the same number, or not to count the holes in the first instance.

    I also ran into another error. As I am working with many features in a workspace (~3,000,000 polygon features split in several layers) I got the "the program needs to abort" message when I tried to move ~200,000 features into a new layer. I tried several times and the result is the same. Furthermore, probably because of the large amount of features, it takes a long time to actually save the workspace. An error occurred here as well. I got a massage which said something like "could not save layer feature" printed out 4 times. I will try to replicate the errors when I have time.
    (all this in GM13.2.2)

    Also, I am expecting to receive the new version of GM14 and will try there as well, to see how things pan out.

    Thanks Mike,
  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited October 2012
    Are you using the 32-bit version of Global Mapper? I would expect an error like that when running out of memory which you might do when moving that many features. You are actually marking the original features as deleted, then creating new copies of them in a new layer, so you would need memory for an additional 200,000 features. This could be using up all of your memory. The 64-bit version can use a lot more memory and not run into issues like this as easily.

    Let me know if I can be of further assistance.

    Thanks,

    Mike
    Global Mapper Guru
    gmsupport@bluemarblegeo.com
    http://www.globalmapper.com
  • RobertRRobertR GlobalMapper Fan! Posts: 286Trusted User
    edited November 2012
    Are you using the 32-bit version of Global Mapper? I would expect an error like that when running out of memory which you might do when moving that many features. You are actually marking the original features as deleted, then creating new copies of them in a new layer, so you would need memory for an additional 200,000 features. This could be using up all of your memory. The 64-bit version can use a lot more memory and not run into issues like this as easily.

    Let me know if I can be of further assistance.

    Thanks,

    Mike
    Global Mapper Guru
    gmsupport@bluemarblegeo.com
    http://www.globalmapper.com


    Hello,

    It is correct, I have the 32bit version. Will try with 64bit.

    Thank you,
Sign In or Register to comment.