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
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.
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
To view this discussion visit https://groups.google.com/d/msgid/lastools/646a02b6-63e5-4152-b007-c46654055e32n%40googlegroups.com.
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
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
To view this discussion visit https://groups.google.com/d/msgid/lastools/646a02b6-63e5-4152-b007-c46654055e32n%40googlegroups.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
To view this discussion visit https://groups.google.com/d/msgid/lastools/ee5f399a-6a11-4fd7-9c62-2e6c7e715cb2n%40googlegroups.com.