Marcello:
N: 89:55:00.138825N S: 89:55:00.138825
E: 179:55:00.069428E W: 179:55:00.069428W
>>> This inf looks very suspicious, the latlon vector extents very
>>> probably too large and could not be represented in the
>>> projection of the target location.
>> Too muc
Hamish said:
> It is impossible to reproject from a simple XY location to a
> projected location, or vice versa. Simple XY is just like graph
> paper, with no Earth-based geo-* part to it. It is most commonly
> used for imagery where x,y are measured in pixels, and manual geo-
> referencing must
> Projection: x,y
It is impossible to reproject from a simple XY location to a
projected location, or vice versa. Simple XY is just like graph
paper, with no Earth-based geo-* part to it. It is most commonly
used for imagery where x,y are measured in pixels, and manual geo-
referencing must be
On Mon, Jul 2, 2012 at 9:03 AM, Marcello Gorini wrote:
> Makus:
>
>>
>> What are the extents of the vector in latlon before projecting into
>> the mercator location? Note that regions spanning 180 degrees
>> longitude or more can not be reprojected to mercator locations due to
>> mathematical cons
Makus:
> What are the extents of the vector in latlon before projecting into
> the mercator location? Note that regions spanning 180 degrees
> longitude or more can not be reprojected to mercator locations due to
> mathematical constraints.20037508.34278924
>
>
That's the result of v.info of the
Thanks for the suggestions.
Markus:
> Please post
> g.proj -p
-PROJ_INFO
-
name : Mercator
proj : merc
datum : wgs84
ellps : wgs84
lon_0 : 0
k : 1
x_0: 0
y_0: 0
no_defs: defined
-PROJ_UNITS---
On Sun, Jul 1, 2012 at 9:17 AM, Marcello Gorini wrote:
> Dear all,
>
> After importing a netCDF file and correcting its bounds using
> r.region so that it spans from -180/180 instead of 0/360, a tried to
> reproject it in the way I always do, following the GRASS book.
>
> I use v.in.region to get
Markus:
> ...
> > |
> Projection: x,y
>
> ... this looks suspicious! Above output may help us to find
> the problem.
probably he was following my tutorial at
http://grass.osgeo.org/wiki/Global_datasets#ETOPO1_.28DEM.29
which uses a nasty hack to get around the original grid-registered
Marcello wrote:
> I use v.in.region to get the region as a vector, v.proj in a
> mercator location and then g.region to the projected vector,
> before applying r.proj to my raster.
note r.proj in current versions of GRASS has some new flags
which mean you don't need to do the location switching an
Hi Marcello,
On Sun, Jul 1, 2012 at 9:17 AM, Marcello Gorini wrote:
...
> But when trying to do g.region I get
>
> ERROR: Invalid region: Invalid coordinates
Please post
g.proj -p
...
> Now, the new grid is within accepted bounds, but the error persists and
> the result of v.info of the projec
Dear all,
After importing a netCDF file and correcting its bounds using
r.region so that it spans from -180/180 instead of 0/360, a tried to
reproject it in the way I always do, following the GRASS book.
I use v.in.region to get the region as a vector, v.proj in a mercator
location and then g.reg
11 matches
Mail list logo
