Suggest Name Be Changed To Undefined

kbelliskbellis Global Mapper UserPosts: 518Trusted User
edited October 2013 in Suggestion Box
change-name-to-undefined.png

The word Unclassified becomes muddled as we see it first properly linked with Class Code [1] and then incorrectly conjoined to [19].

Therefor suggest this Feature Type: be changed to LIDAR, Undefined.

Comments

  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited October 2013
    Actually this is related to the relation of Lidar classifications to built-in GM point types. Normally you would use the Lidar classification, but there is still a point feature type also assigned, there just isn't a separate one for every Lidar class. So the Lidar unclassified codes (0 & 1) and any of the undefined Lidar classes or really any Lidar class that a special point type wasn't made for all dump into the Lidar unclassified bin.

    This is one of those things that would be much cleaner if there wasn't the history of Lidar points just being regular points, but the legacy issues require a bit of muddling here.

    Thanks,

    Mike
    Global Mapper Guru
    geohelp@bluemarblegeo.com
    Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation
  • kbelliskbellis Global Mapper User Posts: 518Trusted User
    edited October 2013
    Is that partly related to the reason why it appears that Blue Marble Geo in response to a GM v13 user's question is saying?:
    We are no longer supporting access to your legacy version of Global Mapper.

    I guess we all have end-of-life issues to deal with :(
Sign In or Register to comment.