Global Mapper v24.1

Screen pick move

txrpls
txrpls Global Mapper UserTrusted User
in Suggestion Box
Make the move function work by picking the from and to location without having to compute an X/Y offset or  azimuth/distance. Just pick the from location and then the to location.

Answers

  • bmg_bob
    bmg_bob Global Mapper Programmer
    Hello,

    Select your feature, right-click and choose Move Feature.  Then you can move the feature using drag and drop -- no need to calculate offset or azimuth/distance.

    Cheers,

    Bob
  • txrpls
    txrpls Global Mapper User Trusted User
    Thanks alot. That will save me a ton of time.
  • txrpls
    txrpls Global Mapper User Trusted User
    Hello Bob,

    That does not work for LAS data. I want to shift the whole point cloud.
  • tjhb
    tjhb Global Mapper User Trusted User
    Why?
  • bmg_bob
    bmg_bob Global Mapper Programmer
    txrpls said:
    Hello Bob,

    That does not work for LAS data. I want to shift the whole point cloud.
    To move the entire point cloud:
    1. Open the Overlay Control Center
    2. Select your point cloud layer in the list
    3. Right-click and choose SHIFT - Shift Selected Layer(s) a Fixed Distance or Transform Coordinates
    You will still need to put in the distance and azimuth, but you only need to enter it once.

    Cheers,

    Bob
  • txrpls
    txrpls Global Mapper User Trusted User
    Thanks Bob, but I know that. I would like to be able to use screen picks hence the original suggestion.
  • tjhb
    tjhb Global Mapper User Trusted User
    edited June 2016
    Why on Earth would you want to do this with LiDAR data?

    Supposing that it's bad data--say you were sure that the georeferencing or georegistration had gone wrong--why would you imagine that clicking and dragging the dataset as a whole would make it more accurate?

    I imagine what you're trying to do might be to make the LiDAR data "line up" with a stack of existing data layers which themselves are either wrongly registered, wrongly projected, or both.

    Could this be a case where the difficulty of what you're trying to do is actually your best friend? The difficulty might mean you should be doing something else.
  • txrpls
    txrpls Global Mapper User Trusted User
    edited June 2016
    Hi Bob,

    This is mainly for comparing data derived from a UAV that is non-controlled vs controlled. Probably not something one would do in the normal operations. What I was doing is checking the errors on the data (quite considerable) in controlled vs non controlled UAV derived LAS data. I registered the non-controlled data to a common point in the controlled LAS data (flown with an RTK unit) and then compared. While I agree this is not "normal," I think GM should work consistently across all vector formats as far as selecting and moving vector objects along with being able to snap tho the LAS points as well.

    All the best.

    Edit: The more I thought about it, probably not a good idea for the average user. I still think you should be able to snap to a LAS point. You guys may want to discuss in house. There are going to be more and more users of GM for processing UAV derived data.
  • tjhb
    tjhb Global Mapper User Trusted User
    edited June 2016
    That's very interesting, thanks for explaining.

    You may know Manifold System? It might be ideal for this workflow (among many others of course). The paradigm is a Map comprised of a stack of Layers, which can be drawings (vector), images, surfaces (rasters) or other things. Any layer can be nudged using the keyboard, in fine or coarse increments, to adjust the registration of that layer alone. It's then easy to read out the delta X and Y you have applied, and fix this into the current projection parameters, or undo it, or whatever.

    Drop me a line if you want help with that approach.

    (Maybe this is something GM could consider adopting as well--as a manual, visual alternative to entering X and Y shifts by value.)

Categories

In this Discussion