[GRASS-user] Estimating import time for large data file

[Rich Shepard]

On Sun, 31 May 2020, Helmut Kudrnovsky wrote:

> is it
> EPSG:3857 [1] [2]
> ?

Helmut,

I've no idea. This dataset was downloaded from the Oregon Geospatial
Enterprise Office (clever name, eh?). The introductory page is here:
<https://www.oregon.gov/geo/Pages/sdlibrary.aspx>.

Oregon provides data in three projections:

# Oregon state standard:
EPSG 2838  NAD83(HARN) <http://www.spatialreference.org/ref/epsg/2838/>
proj4: +proj=lcc +lat_1=46 +lat_2=44.33333333333334 +lat_0=43.66666666666666 +lon_0=-120.5 +x_0=2500000 +y_0=0 +ellps=GRS80 +units=m +no_defs

# Oregon lon/lat in Lambert Conformal Conic:
EPSG 2992 +proj=lcc +lat_1=43 +lat_2=45.5 +lat_0=41.75 +lon_0=-120.5
+x_0=399999.9999984 +y_0=0 +ellps=GRS80 +datum=NAD83 +to_meter=0.3048
+no_defs

# Oregon lon/lat in WGS84.
EPSG 4326: +proj=longlat +ellps=WGS84 +datum=WGS84 +no_defs

I keep all Oregon spatial data using the first projection. But, sometimes a
dataset is in another projection. When I started importing it into
grass-7.9.dev I set the projection based on the .prj file and didn't see the
EPSG code it represented.

Regards,

Rich