Global Mapper Pro Coming Soon

EDIT_LIDAR is not reading the lidar_filter command

Hello, I am trying to select lidar by distance from a shapefile I have attached my script for that and I keep getting the error pasted below. I feel like it is just an order of operations thing, but I have used this script previously and it worked.                            //call global mapper script and version
GLOBAL_MAPPER_SCRIPT VERSION=1.00

SET_LOG_FILE FILENAME="C:\Users\jxm0as3\OneDrive - NEE\Global_mapper_scripts\logfile_SelectLidarbyDistance2.txt" APPEND_TO_FILE=NO LOG_TO_COMMAND_PROMPT=YES

LOG_MESSAGE 1- Script <%SCRIPT_FILENAME%> started at %DATE% %TIME%

UNLOAD_ALL 

//Time stamp
LOG_MESSAGE 2- %TIMESTAMP%:

DIR_LOOP_START DIRECTORY="C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground" FILENAME_MASKS="*.las" RECURSE_DIR=YES

// Importing a Directory
IMPORT_DIR_TREE DIRECTORY="C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground" RECURSE_DIR=YES


// Imports each file into loop
IMPORT FILENAME="%FNAME_W_DIR%"
LOG_MESSAGE 3- Loaded file <%FNAME%> at %DATE% %TIME%

LOG_MESSAGE 4- Importing <%FNAME%> took: %TIME_SINCE_LAST_LOG% 
//Select Lidar by Distance

DEFINE_LIDAR_FILTER NAME= "Noise_Ground" LIDAR_FILTER="ALL,-2,-7,-18"

EDIT_LIDAR FILENAME="%FNAME_W_DIR%"\
LIDAR_FILTER_NAME="Noise_Ground"\
MAX_DIST=1.5\
USE_3D_DIST=NO\
FILENAME_NEAR="C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Part9_KML_Orangdale.shp"\
NEW_LAYER_NAME="%FNAME%_CROPPED"
EXPORT_ANY TYPE=LIDAR_LAS EXPORT_LAYER="%FNAME%_CROPPED" FILENAME="C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground\Select_by_Dist\%FNAME%_CROPPED"

DIR_LOOP_END                                                                                                                                                                                                                                                                                                                                                                                This is the log message:                                                                                                                                                         Running Script <C:\Users\jxm0as3\OneDrive - NEE\Global_mapper_scripts\Select_Lidar_by_distance2.txt> at: 9/7/2021 1:06:19 PM
Global Mapper v22.1 (b030821) (131) [64-bit] [+LIDAR]
WARNING: Unknown parameter <APPEND> ignored for SET_LOG_FILE command.
WARNING: Unknown parameter <TO> ignored for SET_LOG_FILE command.
WARNING: Unknown parameter <FILE> ignored for SET_LOG_FILE command.
1- Script <C:\Users\jxm0as3\OneDrive - NEE\Global_mapper_scripts\Select_Lidar_by_distance2.txt> started at 9/7/2021 1:06:19 PM
Removed all loaded overlays.
2- 9/7/2021 1:06:21 PM:
Starting loop over files in directory <C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground\> that match '*.las'...
Importing directory <C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground>...
Importing file <C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground\Orangedale_01_LIDAR_Part09.las_Noise_Ground.las>...
3- Loaded file <Orangedale_01_LIDAR_Part09.las_Noise_Ground.las> at 9/7/2021 1:18:40 PM
4- Importing <Orangedale_01_LIDAR_Part09.las_Noise_Ground.las> took: 741 s
Defined Lidar filter <Noise_Ground>
Editing loaded Lidar data...
WARNING: All Lidar points to search were also in the list of Lidar points to search near. Lidar ignored.

ERROR: Error running script command EDIT_LIDAR FILENAME="C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Collect_1\Noise_Ground\Orangedale_01_LIDAR_Part09.las_Noise_Ground.las" FILENAME_NEAR="C:\Users\jxm0as3\OneDrive - NEE\Orangdale\Part9_KML_Orangdale.shp" LIDAR_FILTER_NAME="Noise_Ground" MAX_DIST="1.5" NEW_LAYER_NAME="Orangedale_01_LIDAR_Part09.las_Noise_Ground.las_CROPPED" USE_3D_DIST="NO" in C:\Users\jxm0as3\OneDrive - NEE\Global_mapper_scripts\Select_Lidar_by_distance2.txt
Read access violation at data address 0x0000000000000000,
program address 0x000000014075D32F.

Version: v22.1.1 (131) (64-bit)
Build Time: Mar  8 2021 00:18:30
Thread: Main UI Thread




Stack Trace:

000000014075D32F (global_mapper)

0000000141020F6F (global_mapper)

000000014105E5E6 (global_mapper)

0000000140FEE40B (global_mapper)

00000001405B0A3C (global_mapper)

0000000140BD72A6 (global_mapper)

00007FFA966C1072 (mfc140)

00007FFA966C1304 (mfc140)

00007FFA966EAE92 (mfc140)

000000014057D10B (global_mapper)

00007FFA967728F5 (mfc140)

00007FFA9652035D (mfc140)

00007FFA96771B09 (mfc140)

000000014057D76B (global_mapper)

00007FFA96771A5F (mfc140)

... (51 Additional Stack Items Hidden)



If anyone has any insight into why I am receiving this error, it would be appreciated. 

Answers

  • bmg_bobbmg_bob Global Mapper Programmer Posts: 2,328
    Hello,

    This appears to be a bug. My first suggestion is to get the latest Global Mapper daily build to see if this problem has already been fixed.

    If that does not resolve the error, please contact Blue Marble Support directly via email (geohelp@bluemarblegeo.com) so they can address the issue. Please include your script and a sample file that causes the error message. Thank you.

    Cheers,
    Bob
Sign In or Register to comment.