ecodiv
March 29, 2017, 8:36am
1
Dear devs
When using r.proj with the g flag, I would expect an output that can be used directly in g.region. However, running from a latlon location, the following:
r.proj -g location=nc_spm_08_grass7 mapset=PERMANENT input=cfactorbare_1m
gives me the n-s-w-e coordinates in d:m:s, which doesn't work for g.region.
n=35:44:22.382841N s=35:43:57.972871N w=78:40:57.865683W e=78:40:29.910034W rows=750 cols=700
Wouldn't it be better and more consistent with the use of the g flag with g.region to have as output the coordinates in degrees?
Cheers,
Paulo
On 29/03/17 10:36, Paulo van Breugel wrote:
Dear devs
When using r.proj with the g flag, I would expect an output that can be
used directly in g.region. However, running from a latlon location, the
following:
r.proj -g location=nc_spm_08_grass7 mapset=PERMANENT input=cfactorbare_1m
gives me the n-s-w-e coordinates in d:m:s, which doesn't work for g.region.
n=35:44:22.382841N s=35:43:57.972871N w=78:40:57.865683W e=78:40:29.910034W rows=750 cols=700
Why doesn't this work. It should.
Testing here with
g.region n=35:44:22.382841N s=35:43:57.972871N w=78:40:57.865683W e=78:40:29.910034W rows=750 cols=700 -p
I get:
projection: 3 (Latitude-Longitude)
zone: 0
datum: wgs84
ellipsoid: wgs84
north: 35:44:22.382841N
south: 35:43:57.972871N
west: 78:40:57.865683W
east: 78:40:29.910034W
nsres: 0:00:00.032547
ewres: 0:00:00.039937
rows: 750
cols: 700
cells: 525000
Moritz
ecodiv
March 29, 2017, 8:50am
3
On 29-03-17 10:46, Moritz Lennert wrote:
On 29/03/17 10:36, Paulo van Breugel wrote:
Dear devs
When using r.proj with the g flag, I would expect an output that can be
used directly in g.region. However, running from a latlon location, the
following:
r.proj -g location=nc_spm_08_grass7 mapset=PERMANENT input=cfactorbare_1m
gives me the n-s-w-e coordinates in d:m:s, which doesn't work for g.region.
n=35:44:22.382841N s=35:43:57.972871N w=78:40:57.865683W e=78:40:29.910034W rows=750 cols=700
Why doesn't this work. It should.
Good question, it does.. not sure what I did wrong before, but it works without problem now. Sorry for the noise and thanks for the quick reply.
It would still be nice to have an option to get the output in degrees, but that is another issue.
Testing here with
g.region n=35:44:22.382841N s=35:43:57.972871N w=78:40:57.865683W e=78:40:29.910034W rows=750 cols=700 -p
I get:
projection: 3 (Latitude-Longitude)
zone: 0
datum: wgs84
ellipsoid: wgs84
north: 35:44:22.382841N
south: 35:43:57.972871N
west: 78:40:57.865683W
east: 78:40:29.910034W
nsres: 0:00:00.032547
ewres: 0:00:00.039937
rows: 750
cols: 700
cells: 525000
Moritz
On Wed, Mar 29, 2017 at 10:50 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
On 29-03-17 10:46, Moritz Lennert wrote:
On 29/03/17 10:36, Paulo van Breugel wrote:
When using r.proj with the g flag,
...
It would still be nice to have an option to get the output in degrees, but
that is another issue.
... that's decimal degrees... please open a ticket for it.
Markus
ecodiv
March 29, 2017, 1:49pm
5
On 29-03-17 11:48, Markus Neteler wrote:
On Wed, Mar 29, 2017 at 10:50 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
On 29-03-17 10:46, Moritz Lennert wrote:
On 29/03/17 10:36, Paulo van Breugel wrote:
When using r.proj with the g flag,
...
It would still be nice to have an option to get the output in degrees, but
that is another issue.
... that's decimal degrees... please open a ticket for it.
Yes, that's what I meant. Created a ticket (#3323 )
Markus