[GRASS-user] Finding EPSG code based on prj.adf; importing with v.in.gdal

rshepard · July 4, 2018, 10:44pm

The ESRI GRID formatted LiDAR raw data file can be imported using
r.in.gdal using the appropriately defined location. Running 'gdalinfo
<filename> | less' on the prj.adf file reports:

Coordinate System is:
PROJCS["unnamed",
     GEOGCS["Unknown datum based upon the GRS 1980 ellipsoid",
         DATUM["Not_specified_based_on_GRS_1980_ellipsoid",
             SPHEROID["GRS 1980",6378137,298.257222101,
                 AUTHORITY["EPSG","7019"]],
             AUTHORITY["EPSG","6019"]],
         PRIMEM["Greenwich",0,
             AUTHORITY["EPSG","8901"]],
         UNIT["degree",0.0174532925199433,
             AUTHORITY["EPSG","9122"]],
         AUTHORITY["EPSG","4019"]],
     PROJECTION["Lambert_Conformal_Conic_2SP"],
     PARAMETER["standard_parallel_1",44.33333333333334],
     PARAMETER["standard_parallel_2",46],
     PARAMETER["latitude_of_origin",43.66666666666666],
     PARAMETER["central_meridian",-120.5],
     PARAMETER["false_easting",8202099.737532808],
     PARAMETER["false_northing",0],
     UNIT["user-defined",0.3048]]
Origin = (7719274.500000000000000,628402.500000000000000)
Pixel Size = (3.000000000000000,-3.000000000000000)

Looking up EPSG:4019 on the web shows me that it's an "Unknown datum based upon the GRS 1980
ellipsoid."

I created a new location, named EPSG4019, selected that code for the
projection, and ran 'r.in.gdal -o
in=$HOME/path_to/data/topography/LDQ-45122C3/2009_OLC_Hood-to-Coast/Bare_Earth/\
be45122c3/hdr.adf out=dem2009 --overwrite' (Entered on one line; split here
for MUA accommodation.) grass75 responds,

WARNING: Datum <Not_specified_based_on_GRS_1980_ellipsoid> not recognised
by GRASS and no parameters found
Over-riding projection check
ERROR: Illegal latitude for North: 628402

Please show me what I've done incorrectly.

TIA,

Rich

Markus_Metz · July 5, 2018, 7:00am

On Thu, Jul 5, 2018 at 12:44 AM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

The ESRI GRID formatted LiDAR raw data file can be imported using
r.in.gdal using the appropriately defined location. Running ‘gdalinfo
| less’ on the prj.adf file reports:

Coordinate System is:
PROJCS[“unnamed”,
GEOGCS[“Unknown datum based upon the GRS 1980 ellipsoid”,
DATUM[“Not_specified_based_on_GRS_1980_ellipsoid”,
SPHEROID[“GRS 1980”,6378137,298.257222101,
AUTHORITY[“EPSG”,“7019”]],
AUTHORITY[“EPSG”,“6019”]],
PRIMEM[“Greenwich”,0,
AUTHORITY[“EPSG”,“8901”]],
UNIT[“degree”,0.0174532925199433,
AUTHORITY[“EPSG”,“9122”]],
AUTHORITY[“EPSG”,“4019”]],
PROJECTION[“Lambert_Conformal_Conic_2SP”],
PARAMETER[“standard_parallel_1”,44.33333333333334],
PARAMETER[“standard_parallel_2”,46],
PARAMETER[“latitude_of_origin”,43.66666666666666],
PARAMETER[“central_meridian”,-120.5],
PARAMETER[“false_easting”,8202099.737532808],
PARAMETER[“false_northing”,0],
UNIT[“user-defined”,0.3048]]
Origin = (7719274.500000000000000,628402.500000000000000)
Pixel Size = (3.000000000000000,-3.000000000000000)

Looking up EPSG:4019 on the web shows me that it’s an "Unknown datum based upon the GRS 1980

ellipsoid."

EPSG:4019 is not the EPSG code of the SRS, but of one of its components (there are 5 different EPSG codes within this SRS). The SRS itself does not have an EPSG code, therefore you can create a new location with g.proj georef= or r.in.gdal location=

Markus M

I created a new location, named EPSG4019, selected that code for the
projection, and ran ‘r.in.gdal -o
in=$HOME/path_to/data/topography/LDQ-45122C3/2009_OLC_Hood-to-Coast/Bare_Earth/
be45122c3/hdr.adf out=dem2009 --overwrite’ (Entered on one line; split here
for MUA accommodation.) grass75 responds,

WARNING: Datum <Not_specified_based_on_GRS_1980_ellipsoid> not recognised
by GRASS and no parameters found
Over-riding projection check
ERROR: Illegal latitude for North: 628402

Please show me what I’ve done incorrectly.

TIA,

Rich

grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

rshepard · July 5, 2018, 12:46pm

On Thu, 5 Jul 2018, Markus Metz wrote:

EPSG:4019 is not the EPSG code of the SRS, but of one of its components
(there are 5 different EPSG codes within this SRS). The SRS itself does
not have an EPSG code, therefore you can create a new location with g.proj
georef= or r.in.gdal location=

Markus,

I wondered about 4019; most SRS reports have a legitimate EPSG code as the
final one and I was uncertain about this one.

So I'll have grass figure out the appropriate projection from the prj.adf
file.

Thanks,

Rich

Daniel_Victoria · July 6, 2018, 11:32am

The prj.adf says you have a Lambert Conformal Conic. Since you are working with data from oregon, a quick search in Spatialreference.org resulted in this:
Oregon State Plane
http://spatialreference.org/ref/sr-org/7327/

Thake a look at the HUman readable OGC WKT. Looks the same.
I don’t think there is a EPSG code for this but, as Markus wrote, you can use r.in.gdal to create a location based on your file

Cheers
Daniel

On Thu, Jul 5, 2018 at 9:46 AM Rich Shepard <rshepard@appl-ecosys.com> wrote:

On Thu, 5 Jul 2018, Markus Metz wrote:

EPSG:4019 is not the EPSG code of the SRS, but of one of its components
(there are 5 different EPSG codes within this SRS). The SRS itself does
not have an EPSG code, therefore you can create a new location with g.proj
georef= or r.in.gdal location=

Markus,

I wondered about 4019; most SRS reports have a legitimate EPSG code as the
final one and I was uncertain about this one.

So I’ll have grass figure out the appropriate projection from the prj.adf
file.

Thanks,

Rich

grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user