Global Mapper Pro

LAS File Script

eel
eel Global Mapper User
edited February 2014 in GM Script Language
Hello,
We are attempting to clip and re-project a batch of las files by creating a python script that will clip to the area needed and then output a gms file to process in Global Mapper. We have had success using this method for tif files, but are not quite sure if the approach is the same for Lidar/Las data. The python script needs to be written correctly so the gms file knows how to handle the las file. So far we have come up with the code below, my question is; is this the correct method for handling las files in Global Mapper, and are all these calls needed in the script below?

GLOBAL_MAPPER_SCRIPT VERSION=1.00
UNLOAD_ALL


IMPORT FILENAME=C:\Users\jkennamer\Desktop\Test\12TVL2400036000.las TYPE=LIDAR_LAS \
ELEV_UNITS="METERS" LOAD_FLAGS="0,0.000,0,4294967295~4294967295~4294967295~4294967295~4294967295~4294967295~4294967295~4294967295," \
SAMPLING_METHOD="NEAREST_NEIGHBOR" AUTO_CONTRAST="NO" CONTRAST_SHARED="YES" CONTRAST_MODE="NONE" \
CLIP_COLLAR="NONE" TEXTURE_MAP="NO"
LOAD_PROJECTION FILENAME=C:\Users\jkennamer\Desktop\Test\Test.prj
EXPORT_VECTOR FILENAME=C:\Users\jkennamer\Desktop\Outputs\grid_1.Las GLOBAL_BOUNDS=1530935,7525151,1532206,7526117 TYPE=LIDAR_LAS \
VERT_CITATION=VertCS_North_American_Vertical_Datum_1988_(GEOID12A) LAS_VERSION=1.2 SYSTEM_ID=WSI ELEV_UNITS=FEET INC_COLOR=YES

Comments

  • global_mapper
    global_mapper Administrator
    edited February 2014
    That looks pretty close, I would recommend putting quotes around the parameter values in the script, especially in the EXPORT_VECTOR command, like VERT_CITATION, otherwise the spaces will stop the value. If you also want to crop to a polygon rather than a bounding box you can use the POLYGON_CROP_FILE parameter, but GLOBAL_BOUNDS is great if you just want to crop to an area.

    Thanks,

    Mike
    Global Mapper Guru
    geohelp@bluemarblegeo.com
    Global Mapper
Sign In or Register to comment.