Problems with lasvdatum64

96 views
Skip to first unread message

Malcolm Williamson

unread,
Jul 30, 2025, 2:03:55 AMJul 30
to last...@googlegroups.com

Hi,

I'm having strange problems with lasvdatum64:

lasvdatum64 -i USGS_LPC_AR_Benton_2015_15SVA155110.laz -vgrid ..\Grids\us_noaa_g2012a.gtx -backward -o test.laz
ERROR: no overlap between long/lat bounding boxes of vgrid and file 'USGS_LPC_AR_Benton_2015_15SVA155110.laz'.

As you can see in the screenshot below, the dreaded ArcGIS Pro happily finds the two areas to be overlapping (the red box is the bounding box of the LAS file; the pixelated gray background is the .gtx grid). As I change coordinate systems of the map, the data layers are remaining correctly oriented. The screenshot was done in WGS84. So, I'm not understanding why lasvdatum64 is insisting they don't overlap. I have successfully used lasmerge on the same data files with no errors or complaints.

The grid and sample laz file  can be found here:

https://uark.box.com/s/e4h7ja3330dgmm84p8nlgggapz83rsei

Thanks for any help you can provide.

-- 
-Malcolm
--------------------
Malcolm D. Williamson
Fayetteville, AR
479-790-2748  mal...@cast.uark.edu

LAStools - efficient tools for LiDAR processing

unread,
Jul 30, 2025, 8:40:14 AMJul 30
to LAStools - efficient tools for LiDAR processing
Hi Malcom,
the LAZ file has this header
ver:            LAS 1.4 [pnt=6|len=30]
point count:    1,130,319
scale x y z:    0.01 0.01 0.001
offset x y z:   0 0 0
min x y z:      357,000.00 4,011,000.00 285.500
max x y z:      358,499.99 4,012,499.99 378.470
range x y z:    1,499.99 1,499.99 92.970
WKT:
COMPD_CS[NAD83(2011) / UTM zone 15N + NAVD88 - Geoid12B (Meters),
  PROJCS[NAD83(2011) / UTM zone 15N,
    GEOGCS[NAD83(2011),
      DATUM[NAD83 (National Spatial Reference System 2011),
        SPHEROID[GRS 1980,6378137,298.257222101,
          AUTHORITY[EPSG,7019]],
        AUTHORITY[EPSG,1116]],
      PRIMEM[Greenwich,0,
        AUTHORITY[EPSG,8901]],
      UNIT[degree,0.0174532925199433,
        AUTHORITY[EPSG,9122]],
      AUTHORITY[EPSG,6318]],
    PROJECTION[Transverse_Mercator],
    PARAMETER[latitude_of_origin,0],
    PARAMETER[central_meridian,-93],
    PARAMETER[scale_factor,0.9996],
    PARAMETER[false_easting,500000],
    PARAMETER[false_northing,0],
    UNIT[Meter,1,
      AUTHORITY[EPSG,9001]],
    AXIS[X,EAST],
    AXIS[Y,NORTH],
    AUTHORITY[EPSG,6344]],
  VERT_CS[NAVD88 - Geoid12B (Meters),
    VERT_DATUM[North American Vertical Datum 1988,2005,
      AUTHORITY[EPSG,5103]],
    UNIT[Meter,1,
      AUTHORITY[EPSG,9001]],
    AXIS[Up,UP],
    AUTHORITY[EPSG,5703]]]

Converted to long/lat this is somewhere at
  -94.5°/36.2°
but the GTX file reports this header (using lasvdatum64 with -v argument):
grid dimensions [ll lat, ll long, delta lat, delta long, rows, cols] = [24.000000,172.000000,0.016667,0.016667,2881,7681]
which results into a bounding box of
    lat: 24..24+0,0.016667*2881 == Range: 24..72
    long: 172..172+0.016667*7681 == Range: 172..300
which is far away from your area.

Are you sure you the GTX file is correct?
If so: What grid dimensions do you think the GTX is covering?

Cheers,

Jochen @rapidlasso

Malcolm Williamson

unread,
Aug 1, 2025, 8:54:17 AMAug 1
to last...@googlegroups.com

Hi Jochen,

As you stated, the LiDAR file is around -94.5, which is equivalent to 265.5, yes? That definitely puts us between 172-300, the longitude range of the GTX grid. Full extent of the grid below, along with a tiny red outline for the .laz file.

-Malcolm
--------------------
Malcolm D. Williamson
Fayetteville, AR
479-790-2748  mal...@cast.uark.edu
--
Download LAStools at
https://rapidlasso.de
Manage your settings at
https://groups.google.com/g/lastools/membership
---
You received this message because you are subscribed to the Google Groups "LAStools - efficient tools for LiDAR processing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lastools+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lastools/fa2fba54-63c2-4948-9a0b-06d6a95e15c0n%40googlegroups.com.

LAStools - efficient tools for LiDAR processing

unread,
Aug 1, 2025, 9:09:31 AMAug 1
to LAStools - efficient tools for LiDAR processing
Hi Malcolm,
yes, that's right, of course - we'll fix that quickly.
We will release a new version covering this within the next days.

Cheers,

Jochen @rapidlasso

Malcolm Williamson

unread,
Aug 4, 2025, 12:28:33 PMAug 4
to last...@googlegroups.com

Much appreciated, Jochen - I'll use it as soon as I get it.

-Malcolm
--------------------
Malcolm D. Williamson
Fayetteville, AR
479-790-2748  mal...@cast.uark.edu

rapid...@gmail.com

unread,
Aug 8, 2025, 10:52:37 AMAug 8
to LAStools - efficient tools for LiDAR processing
Hi Malcolm,
thank you for your patience, we did not finish all tests with this version, but want to give you the option to test with your dataset since you are waiting for this fix.
This beta of lasvdatum64 should cover the situation where we have boundaries out of a -180 - 180° range or a range overflow where the upper range is absolute lower than the lower range.

Cheers,

Jochen @rapidlasso

Malcolm Williamson

unread,
Aug 8, 2025, 10:57:55 AMAug 8
to LAStools - efficient tools for LiDAR processing

Ah, was looking at my laz file and realized that it's in UTM - so whatever library you're using (PROJ?) is returning the longitude of -93.940407, converted from the UTM coordinates in the file. Then it's comparing it to the non-negative longitude from the geoid grid file (which, because it crosses 180 degree line, has to be all positive numbers) and makes the incorrect conclusion.

-Malcolm
--------------------
Malcolm D. Williamson
Fayetteville, AR
479-790-2748  mal...@cast.uark.edu
On 8/8/2025 9:34 AM, Malcolm Williamson wrote:

Hi Jochen,

As I hadn't heard about a new release yet, I downloaded the lastest, which appears to be the date of our conversation below. If so, the checking is still incorrect:

D:\Projects\InSAR\USGS_LiDAR_Fayetteville\Fayetteville_LiDAR>lasvdatum64 -i USGS_LPC_AR_Benton_2015_15SVA155110.laz -vgrid ..\Grids\us_noaa_g2012a.gtx -backward -o test.laz
ERROR: file [USGS_LPC_AR_Benton_2015_15SVA155110.laz] exceed vgrid lower longitude boundary (-93.940407 < 172.000000).

This currently has me at a standstill - can you help me out?

Thanks,

-Malcolm
--------------------
Malcolm D. Williamson
Fayetteville, AR
479-790-2748  mal...@cast.uark.edu

Malcolm Williamson

unread,
Aug 8, 2025, 11:03:28 AMAug 8
to last...@googlegroups.com

Great, I think that's got it! I'll do a bit more testing and checking.

Thanks very much,

-Malcolm
--------------------
Malcolm D. Williamson
Fayetteville, AR
479-790-2748  mal...@cast.uark.edu
Reply all
Reply to author
Forward
0 new messages