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. It's not a climate model, but that's exactly the way

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,

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] 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