I need to re-organize locations within ~/data/grassdata and transform all
projections to a single one. Locations now are by the states in which I have
(or had) projects, but there are other locations within them that I want to
collect into a single PERMANENT mapset.
For example, in ~/data/grassdata/Oregon the PERMANENT mapset's projection
is that of the former state standard:
name: Lambert Conformal Conic
proj: lcc
datum: nad83
ellps: grs80
lat_1: 43
lat_2: 45.5
lat_0: 41.75
lon_0: -120.5
x_0: 400000.00000000
y_0: 0
no_defs: defined
nadgrids: WO
and I want to transform that to the current state standard:
name: NAD83(HARN) / Oregon North
datum: nad83harn
ellps: grs80
proj: lcc
lat_1: 46
lat_2: 44.33333333333334
lat_0: 43.66666666666666
lon_0: -120.5
x_0: 2500000
y_0: 0
no_defs: defined
towgs84: 0.000,0.000,0.000
Looking at the general commands I don't find one that will allow me to
transform a location's projection while there are modules to convert a
mapset's projection. The g.rename module renames mapsets so it seems that it
cannot be used to rename locations.
Pointers needed.
Rich
On Fri, 22 Jun 2018, Rich Shepard wrote:
I need to re-organize locations within ~/data/grassdata and transform all
projections to a single one. Locations now are by the states in which I have
(or had) projects, but there are other locations within them that I want to
collect into a single PERMANENT mapset.
Never mind. I'll create a new location using EPSG 2838, then transform all
other data to its PERMANENT mapset by reprojecting it.
Rich
On Fri, Jun 22, 2018 at 2:52 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
On Fri, 22 Jun 2018, Rich Shepard wrote:
I need to re-organize locations within ~/data/grassdata and transform all
projections to a single one. Locations now are by the states in which I have
(or had) projects, but there are other locations within them that I want to
collect into a single PERMANENT mapset.
Never mind. I’ll create a new location using EPSG 2838, then transform all
other data to its PERMANENT mapset by reprojecting it.
g.proj.all might be helpful in that.
https://grass.osgeo.org/grass74/manuals/addons/g.proj.all.html
On Fri, 22 Jun 2018, Vaclav Petras wrote:
g.proj.all might be helpful in that.
https://grass.osgeo.org/grass74/manuals/addons/g.proj.all.html
Vaclav,
Thank you. My data directory is an unorganized mess now but I will see if
g.proj.all will help.
Best regards,
Rich