I'm trying to import a LiDAR data set. I've used EPSG:6559 while the data
source manager tells me it imports into ARC/gis using EPSG:6557. I've tried
both and grass doesn't work for me regardless of which code I use.
I create a location:
grass -c EPSG:6557 /data1/grassdata/Metro_LiDAR
Then import the data set (N.B. a copy of the data source tarball is on the
fileconvoy.com web site; see below):
r.in.gdal in=Bare_Earth/be45122f8/hdr.adf out=topo_2010 mem=2000 --o
GRASS returns:
ERROR: Projection of dataset does not appear to match current location.
Location PROJ_INFO is:
name: NAD83(2011) / Oregon GIC Lambert (ft)
datum: nad83_2011
ellps: grs80
proj: lcc
lat_0: 41.75
lon_0: -120.5
lat_1: 43
lat_2: 45.5
x_0: 399999.9999984
y_0: 0
no_defs: defined
Dataset PROJ_INFO is:
name: unnamed
ellps: grs80
proj: lcc
lat_0: 41.75
lon_0: -120.5
lat_1: 43
lat_2: 45.5
x_0: 400000
y_0: 0
no_defs: defined
Difference in: datum
In case of no significant differences in the projection definitions,
use the -o flag to ignore them and use current location definition.
Consider generating a new location from the input dataset using the
'location' parameter.
I added the -o option to r.in.gdal and this is the result:
r.in.gdal -o
in=$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8/hdr.adf
out=topo_2010 mem=2000 --o
Over-riding projection check
Importing raster map <topo_2010>...
ERROR 1: Block is corrupt, block size was 21532, but expected to be 16384.
ERROR 1:
/home/rshepard/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8,
band 1: IReadBlock failed at X offset 15, Y offset 308: Block is corrupt,
block size was 21532, but expected to be 16384.
ERROR: Unable to read row 4928
If the file loads into ARC/gis why not into grass?
I do not see why this isn't working here. I've uploaded the Bare_Earth
directory to
http://www.fileconvoy.com/dfl.php?id=g4e3d18b830b60bef10004916731ceed9a68e0d28c3.
It's a 474M file.
I need to learn why I have problems importing the data using either EPSG
code, ignoring the data project by override or not.
Regards,
Rich
_______________________________________________
grass-user mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/grass-user
