[GRASS-user] Correct import of a global grid (0E to 360E) to GRASS (-180W to 180E).

Dear all, I am pretty sure this must be easy, but I just can't find the correct answer. My grid is a netcdf geographic grid that spans from 0E to 360E and from 90N to -90S. I use r.in.gdal to import it, but it gets flipped since GRASS region spans from -180W to 180E. How to do it right?

Re: [GRASS-user] Correct import of a global grid (0E to 360E) to GRASS (-180W to 180E).

Hi Marcello, It sounds like you're trying to import your map into the wrong coordinate system. If you have the correct coordinate system of the NetCDF, you should be able to define a location with that CRS using either the correct EPSG code or a WKT string. If need be, you can always create a WKT

Re: [GRASS-user] Correct import of a global grid (0E to 360E) to GRASS (-180W to 180E).

Thanks for he fast response Daniel: you should be able to define a location with that CRS using either the correct EPSG code or a WKT string. I don't have the EPSG code. Only know that it isin lat long and that long is 0-360. If need be, you can always create a WKT string as well,

[GRASS-user] GRASS and the Python geospatial modules (Shapely, PySAL, ...)

One thing that is not enough highlighted is the ability to use the Python geospatial modules like Shapely of Sean Gillies ( http://pypi.python.org/pypi/Shapely/1.2.15 http://pypi.python.org/pypi/Shapely/1.2.15 ) or PySAL ( http://pypi.python.org/pypi/pysal/1.3.0

Re: [GRASS-user] GRASS and the Python geospatial modules (Shapely, PySAL, ...)

One thing that is not enough highlighted is the ability to use the Python geospatial modules like Shapely of Sean Gillies (http://pypi.python.org/pypi/Shapely/1.2.15) or PySAL (http://pypi.python.org/pypi/pysal /1.3.0) in GRASS GIS. It brings very interesting complementary treatments. thanks

Re: [GRASS-user] GRASS, ArcGIS, and Python incompatibilties

Don't you need to have the wxPython that GRASS was compiled with? And doesn't this wxPython have to match the Python version? Michael On Jun 29, 2012, at 1:49 PM, Glynn Clements wrote: Michael Barton wrote: I thought I'd seen this somewhere on the list, but I can't seem to find it. If

Re: [GRASS-user] GRASS, ArcGIS, and Python incompatibilties

Yes. That's great it is working for you. But in our case, it won't launch the wxPython GUI and generates a Python error that it cannot find the correct version of Python. This is the stock version of GRASS that works for you and others (so Python is OK there) and Python works fine in ArcGIS, so

Re: [GRASS-user] Correct import of a global grid (0E to 360E) to GRASS (-180W to 180E).

Which way does it get flipped? Most NetCDF files will import via r.in.gdal correctly, but they are displayed as (from L-R) as 0-180E/180W-0. This is the way that most climate model files are created and then stored. This presents some problems in displaying vector overlays (I've reported this

Re: [GRASS-user] GRASS, ArcGIS, and Python incompatibilties

What versions of Python are in the registry database ? What is the error message ? (detail of the version mismatch) You can compare the paths used by the Python versions in ArcGIS (from the Python console) and in GRASS GIS (from the msys shell) import sys print sys.path Normally the result

Re: [GRASS-user] GRASS, ArcGIS, and Python incompatibilties

Michael Barton wrote: Don't you need to have the wxPython that GRASS was compiled with? And doesn't this wxPython have to match the Python version? GRASS isn't compiled with any version of Python, i.e. it doesn't have any binaries which link against the Python DLL/DSO. At one time there

Re: [GRASS-user] Correct import of a global grid (0E to 360E) to GRASS (-180W to 180E).

Michael wrote: Which way does it get flipped?  Most NetCDF files will import via r.in.gdal correctly, but they are displayed as (from L-R) as 0-180E/180W-0. This is the way that most climate model files are created and then stored. note I've had some data in the past which either had bad

Re: [GRASS-user] GRASS, ArcGIS, and Python incompatibilties

Does this mean that we no longer *have* to bundle wxPython with the Mac binaries? That they will work with whatever wxPython is installed (assuming it is within the range of supported versions, of course) regardless of what it was compiled with? Michael On Jun 30, 2012, at 4:32 PM, Glynn