UNIQUE_ID_BASE problem

jpul
jpul Global Mapper User
edited August 2012 in Bug Report
When the option
UNIQUE_ID_BASE=1
is set on a EDIT_VECTOR query
the value set on the ID does not start in 1 because the index in layer
value is added to the result

Comments

  • global_mapper
    global_mapper Administrator
    edited August 2012
    Hmmm I'm not seeing that. It looks like the first matching item (index 0) should be set that the ID value. The code basically takes your unique ID value and adds the 0-based index of the matching feature. The feature index reported in the search dialog starts at 1, but internally it is 0 based.

    Thanks,

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

Categories

In this Discussion