[GRASS-dev] how to import NetCDF data??

I’m trying to help someone at NCAR import NetCDF data and we keep getting an illegal north latitude error. Looking at the GDAL info, I think we need to specify some additional metadata, but the GDAL page stops short of giving an example of how to do this. Has anyone imported climate data this way?

Thanks
Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

I had to import a bunch of SSURGO NetCDF data not too long ago Michael (I was going back and forth with GRASS and MATLAB). I don’t seem to remember having any trouble with gdal (which means that it must have worked!) Are you sure that the NetCDF is Lat Long?

What was your error exactly? Is the file too big to share? If not send it to me and I’ll take a look.

Best,

Kirk

Kirk R. Wythers
Department of Forest Resources
University of Minnesota
St. Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu

On Feb 7, 2012, at 12:33 PM, Michael Barton wrote:

I’m trying to help someone at NCAR import NetCDF data and we keep getting an illegal north latitude error. Looking at the GDAL info, I think we need to specify some additional metadata, but the GDAL page stops short of giving an example of how to do this. Has anyone imported climate data this way?

Thanks
Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu


grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Michael,

our experience with netCDF has been mixed, it very much depends what
is in the file.
Unless you find that this was a trivial error and everything works well,
it would be extremely valuable to test GRASS with various types of netCDF data,
document what works and what does not - perhaps set up a wiki page.
I have several atmospheric science students who work with netCDF so we can
provide some feedback too.
If there are still problems and if we can identify what needs to be
developed to make working with netCDF in GRASS more robust perhaps
this would be a good project for Google summer code
(hopefully OSGeo is participating this tear again)

Helena

On Tue, Feb 7, 2012 at 1:49 PM, Kirk Wythers <kirk.wythers@gmail.com> wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago Michael (I
was going back and forth with GRASS and MATLAB). I don't seem to remember
having any trouble with gdal (which means that it must have worked!) Are you
sure that the NetCDF is Lat Long?

What was your error exactly? Is the file too big to share? If not send it to
me and I'll take a look.

Best,

Kirk

Kirk R. Wythers
Department of Forest Resources
University of Minnesota
St. Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu

On Feb 7, 2012, at 12:33 PM, Michael Barton wrote:

I'm trying to help someone at NCAR import NetCDF data and we keep getting an
illegal north latitude error. Looking at the GDAL info, I think we need to
specify some additional metadata, but the GDAL page stops short of giving an
example of how to do this. Has anyone imported climate data this way?

Thanks
Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Helena Mitasova
Associate Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/

email: hmitaso@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802

On Tue, Feb 7, 2012 at 7:33 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

I'm trying to help someone at NCAR import NetCDF data and we keep getting an
illegal north latitude error.

The new GDAL 1.9.0 has an improved netCDF driver, see
http://trac.osgeo.org/gdal/wiki/Release/1.9.0-News

Markus

We had the same errors with a couple of files. We sent Tom the simplest and smallest of them. Once we figure out what is happening we can let everyone know. It would probably be good to begin a WIKI page on this once we have some info.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 7, 2012, at 1:20 PM, Helena Mitasova wrote:

Michael,

our experience with netCDF has been mixed, it very much depends what
is in the file.
Unless you find that this was a trivial error and everything works well,
it would be extremely valuable to test GRASS with various types of netCDF data,
document what works and what does not - perhaps set up a wiki page.
I have several atmospheric science students who work with netCDF so we can
provide some feedback too.
If there are still problems and if we can identify what needs to be
developed to make working with netCDF in GRASS more robust perhaps
this would be a good project for Google summer code
(hopefully OSGeo is participating this tear again)

Helena

On Tue, Feb 7, 2012 at 1:49 PM, Kirk Wythers <kirk.wythers@gmail.com> wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago Michael (I
was going back and forth with GRASS and MATLAB). I don't seem to remember
having any trouble with gdal (which means that it must have worked!) Are you
sure that the NetCDF is Lat Long?

What was your error exactly? Is the file too big to share? If not send it to
me and I'll take a look.

Best,

Kirk

Kirk R. Wythers
Department of Forest Resources
University of Minnesota
St. Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu

On Feb 7, 2012, at 12:33 PM, Michael Barton wrote:

I'm trying to help someone at NCAR import NetCDF data and we keep getting an
illegal north latitude error. Looking at the GDAL info, I think we need to
specify some additional metadata, but the GDAL page stops short of giving an
example of how to do this. Has anyone imported climate data this way?

Thanks
Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
grass-user Info Page

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page

--
Helena Mitasova
Associate Professor
Department of Marine, Earth and Atmospheric Sciences
North Carolina State University
1125 Jordan Hall
NCSU Box 8208
Raleigh, NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/

email: hmitaso@ncsu.edu
ph: 919-513-1327 (no voicemail)
fax 919 515-7802

Thanks Markus,

Once William comes out with a new GDAL framework, I'll be able to test this out. How does it work on Windows? Does GDAL come packaged with GRASS? Or is it installed separately?

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 7, 2012, at 5:27 PM, Markus Neteler wrote:

On Tue, Feb 7, 2012 at 7:33 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

I'm trying to help someone at NCAR import NetCDF data and we keep getting an
illegal north latitude error.

The new GDAL 1.9.0 has an improved netCDF driver, see
http://trac.osgeo.org/gdal/wiki/Release/1.9.0-News

Markus

Michael wrote:

We had the same errors with a couple
of files. We sent Tom the simplest and smallest of them.
Once we figure out what is happening we can let everyone
know. It would probably be good to begin a WIKI page on this
once we have some info.

there already is one: (albeit a bit empty)
   http://grass.osgeo.org/wiki/NetCDF

see also:
   http://grass.osgeo.org/wiki/GRASS_and_GMT

and the gdal_translate trick to extract the data layer into a geotiff,
then import the geotiff into GRASS. (probably a direct import is
possible, but the geotiff makes problems easier to understand)
that method is explained here:
   http://grass.osgeo.org/wiki/MODIS#Method_1

also in the above link is instructions for applying georef to the geotiff
using gdal_translate as GDAL wasn't doing so, which is I think the same
problem you'll be seeing.

you get the 'illegal latitude for north' error because it has no georef
(as far as gdal is reporting) and so falls back to 1 row per pixel. If
the image is more than 90 pixels high that exceeds 90 degrees N and is
illegal for a lat/lon location. You can override that in recent versions
of GRASS with the r.in.gdal -l flag, but then Must use r.region directly
after import to set the bounds to what they should be.

Helena wrote:

> If there are still problems and if we can identify what needs to be
> developed to make working with netCDF in GRASS more robust perhaps
> this would be a good project for Google summer code
> (hopefully OSGeo is participating this tear again)

hopefully :slight_smile:

anyway I think if there are georef problems they probably need to be
addressed at the GDAL side of things, not in GRASS per se.

Kirk wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago
Michael (I was going back and forth with GRASS and MATLAB).

any reason not to use r.in.mat, r.out.mat for that? i.e. any short-
comings in those tools which should be addressed?

regards,
Hamish

Thanks much Hamish
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 7, 2012, at 10:39 PM, Hamish wrote:

Michael wrote:

We had the same errors with a couple
of files. We sent Tom the simplest and smallest of them.
Once we figure out what is happening we can let everyone
know. It would probably be good to begin a WIKI page on this
once we have some info.

there already is one: (albeit a bit empty)
  NetCDF - GRASS-Wiki

see also:
  GRASS and GMT - GRASS-Wiki

and the gdal_translate trick to extract the data layer into a geotiff,
then import the geotiff into GRASS. (probably a direct import is
possible, but the geotiff makes problems easier to understand)
that method is explained here:
  MODIS - GRASS-Wiki

also in the above link is instructions for applying georef to the geotiff
using gdal_translate as GDAL wasn't doing so, which is I think the same
problem you'll be seeing.

you get the 'illegal latitude for north' error because it has no georef
(as far as gdal is reporting) and so falls back to 1 row per pixel. If
the image is more than 90 pixels high that exceeds 90 degrees N and is
illegal for a lat/lon location. You can override that in recent versions
of GRASS with the r.in.gdal -l flag, but then Must use r.region directly
after import to set the bounds to what they should be.

Helena wrote:

If there are still problems and if we can identify what needs to be
developed to make working with netCDF in GRASS more robust perhaps
this would be a good project for Google summer code
(hopefully OSGeo is participating this tear again)

hopefully :slight_smile:

anyway I think if there are georef problems they probably need to be
addressed at the GDAL side of things, not in GRASS per se.

Kirk wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago
Michael (I was going back and forth with GRASS and MATLAB).

any reason not to use r.in.mat, r.out.mat for that? i.e. any short-
comings in those tools which should be addressed?

regards,
Hamish

Michael,

I could not open the file in GRASS either. I have attached the errors I got. They look like the same that you were describing (I tried both with and without the -o flag). I did however remember the work around I used, which was to:

  1. import the .nc files into MATLAB
  2. Export as GeoTIffs
  3. Read the GeoTiffs into GRASS

This made sense for me partly because I needed to aggregate daily values to monthly means which I did in step 1, but then never thought much more about why I couldn’t import directly into GRASS . Your problem motivated me to look into why I needed this workaround in the first place (which is not much of a workaround unless you have access to MATLAB)… which appears to be that my gdal does not have GMT/netcdf support either (as Markus pointed out yesterday). I am also using WIlliams binaries and frameworks.

I agree that more detail in the wiki would be helpful, but I think the first step is to compile to update gdal with GMT/NetCDF support. Perhaps William would be interested?

===================================================================================================================================
GRASS ERRORS:

GRASS 6.4.1 (latlon):~ > r.in.gdal input=~/Desktop/ppt_SRESA2_mid_annual_down_anomaly.nc output=ppt_SRESA2_mid_annual_down_anomaly
ERROR: Projection of dataset does not appear to match current location.

Location PROJ_INFO is:
name: Lat/Lon
proj: ll
datum: nad83
ellps: grs80
towgs84: 0,0,0,0,0,0,0
no_defs: defined

Import dataset PROJ_INFO is:
cellhd.proj = 0 (unreferenced/unknown)

You can use the -o flag to r.in.gdal to override this check and use
the location definition for the dataset.
Consider generating a new location from the input dataset using the
‘location’ parameter.

GRASS 6.4.1 (latlon):~ > r.in.gdal -o input=~/Desktop/ppt_SRESA2_mid_annual_down_anomaly.nc output=ppt_SRESA2_mid_annual_down_anomaly
WARNING: Over-riding projection check
WARNING: G_set_window(): Illegal latitude for North
GRASS 6.4.1 (latlon):~ >

===================================================================================================================================

On Feb 7, 2012, at 9:10 PM, Michael Barton wrote:

Thanks Kirk,

Here is a copy of the smallest file we tried. The big ones gave identical errors.

Michael

<ppt_SRESA2_mid_annual_down_anomaly.nc>


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 7, 2012, at 11:49 AM, Kirk Wythers wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago Michael (I was going back and forth with GRASS and MATLAB). I don’t seem to remember having any trouble with gdal (which means that it must have worked!) Are you sure that the NetCDF is Lat Long?

What was your error exactly? Is the file too big to share? If not send it to me and I’ll take a look.

Best,

Kirk

Kirk R. Wythers
Department of Forest Resources
University of Minnesota
St. Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu

On Feb 7, 2012, at 12:33 PM, Michael Barton wrote:

I’m trying to help someone at NCAR import NetCDF data and we keep getting an illegal north latitude error. Looking at the GDAL info, I think we need to specify some additional metadata, but the GDAL page stops short of giving an example of how to do this. Has anyone imported climate data this way?

Thanks
Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu


grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Lack of NetCDF support would be a problem for sure. We wondered about that. Jennifer is trying on Windows and I’m on a Mac.

Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 8, 2012, at 9:16 AM, Kirk Wythers wrote:

Michael,

I could not open the file in GRASS either. I have attached the errors I got. They look like the same that you were describing (I tried both with and without the -o flag). I did however remember the work around I used, which was to:

  1. import the .nc files into MATLAB
  2. Export as GeoTIffs
  3. Read the GeoTiffs into GRASS

This made sense for me partly because I needed to aggregate daily values to monthly means which I did in step 1, but then never thought much more about why I couldn’t import directly into GRASS . Your problem motivated me to look into why I needed this workaround in the first place (which is not much of a workaround unless you have access to MATLAB)… which appears to be that my gdal does not have GMT/netcdf support either (as Markus pointed out yesterday). I am also using WIlliams binaries and frameworks.

I agree that more detail in the wiki would be helpful, but I think the first step is to compile to update gdal with GMT/NetCDF support. Perhaps William would be interested?

===================================================================================================================================
GRASS ERRORS:

GRASS 6.4.1 (latlon):~ > r.in.gdal input=~/Desktop/ppt_SRESA2_mid_annual_down_anomaly.nc output=ppt_SRESA2_mid_annual_down_anomaly
ERROR: Projection of dataset does not appear to match current location.

Location PROJ_INFO is:
name: Lat/Lon
proj: ll
datum: nad83
ellps: grs80
towgs84: 0,0,0,0,0,0,0
no_defs: defined

Import dataset PROJ_INFO is:
cellhd.proj = 0 (unreferenced/unknown)

You can use the -o flag to r.in.gdal to override this check and use
the location definition for the dataset.
Consider generating a new location from the input dataset using the
‘location’ parameter.

GRASS 6.4.1 (latlon):~ > r.in.gdal -o input=~/Desktop/ppt_SRESA2_mid_annual_down_anomaly.nc output=ppt_SRESA2_mid_annual_down_anomaly
WARNING: Over-riding projection check
WARNING: G_set_window(): Illegal latitude for North
GRASS 6.4.1 (latlon):~ >

===================================================================================================================================

On Feb 7, 2012, at 9:10 PM, Michael Barton wrote:

Thanks Kirk,

Here is a copy of the smallest file we tried. The big ones gave identical errors.

Michael

<ppt_SRESA2_mid_annual_down_anomaly.nc>


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 7, 2012, at 11:49 AM, Kirk Wythers wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago Michael (I was going back and forth with GRASS and MATLAB). I don’t seem to remember having any trouble with gdal (which means that it must have worked!) Are you sure that the NetCDF is Lat Long?

What was your error exactly? Is the file too big to share? If not send it to me and I’ll take a look.

Best,

Kirk

Kirk R. Wythers
Department of Forest Resources
University of Minnesota
St. Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu

On Feb 7, 2012, at 12:33 PM, Michael Barton wrote:

I’m trying to help someone at NCAR import NetCDF data and we keep getting an illegal north latitude error. Looking at the GDAL info, I think we need to specify some additional metadata, but the GDAL page stops short of giving an example of how to do this. Has anyone imported climate data this way?

Thanks
Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu


grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

This will be even more important with Soren's new temporal GIS framework. Many netcdf climate files are the equivalent of 'time-cubes'. Being able to read/write these easily would provide a very rich source of data to use in temporal GIS analyses.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 8, 2012, at 10:14 AM, Jennifer Boehnert wrote:

Thank you everyone for all the support, suggestions and feedback. I am
trying to create a course using GRASS which I would teach in Latin
America and eventually hopefully in Africa working on vulnerability
assessements using climate change model output from NCAR. My netCDF
data is from the CCSM which was in by the IPCC AR4, it is netCDF3 and
using the CF-convention. It is a pretty typical netCDF file and it
would be great if we could read it into GRASS directly without having to
convert it to a geotiff or any other format, if possible.
Thanks Jennifer

On 2/8/2012 10:05 AM, Michael Barton wrote:

Lack of NetCDF support would be a problem for sure. We wondered about
that. Jennifer is trying on Windows and I'm on a Mac.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Feb 8, 2012, at 9:16 AM, Kirk Wythers wrote:

Michael,

I could not open the file in GRASS either. I have attached the errors
I got. They look like the same that you were describing (I tried both
with and without the -o flag). I did however remember the work around
I used, which was to:

1. import the .nc files into MATLAB
2. Export as GeoTIffs
3. Read the GeoTiffs into GRASS

This made sense for me partly because I needed to aggregate daily
values to monthly means which I did in step 1, but then never thought
much more about why I couldn't import directly into GRASS . Your
problem motivated me to look into why I needed this workaround in the
first place (which is not much of a workaround unless you have access
to MATLAB)… which appears to be that my gdal does not have GMT/netcdf
support either (as Markus pointed out yesterday). I am also using
WIlliams binaries and frameworks.

I agree that more detail in the wiki would be helpful, but I think the
first step is to compile to update gdal with GMT/NetCDF support.
Perhaps William would be interested?

===================================================================================================================================
GRASS ERRORS:

GRASS 6.4.1 (latlon):~ > r.in.gdal
input=~/Desktop/ppt_SRESA2_mid_annual_down_anomaly.nc
output=ppt_SRESA2_mid_annual_down_anomaly
ERROR: Projection of dataset does not appear to match current location.

Location PROJ_INFO is:
name: Lat/Lon
proj: ll
datum: nad83
ellps: grs80
towgs84: 0,0,0,0,0,0,0
no_defs: defined

Import dataset PROJ_INFO is:
cellhd.proj = 0 (unreferenced/unknown)

You can use the -o flag to r.in.gdal to override this check and use
the location definition for the dataset.
Consider generating a new location from the input dataset using the
'location' parameter.

GRASS 6.4.1 (latlon):~ > r.in.gdal -o
input=~/Desktop/ppt_SRESA2_mid_annual_down_anomaly.nc
output=ppt_SRESA2_mid_annual_down_anomaly
WARNING: Over-riding projection check
WARNING: G_set_window(): Illegal latitude for North
GRASS 6.4.1 (latlon):~ >

On Feb 7, 2012, at 9:10 PM, Michael Barton wrote:

Thanks Kirk,

Here is a copy of the smallest file we tried. The big ones gave
identical errors.

Michael

<ppt_SRESA2_mid_annual_down_anomaly.nc>

____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
<Center for Social Dynamics and Complexity;

On Feb 7, 2012, at 11:49 AM, Kirk Wythers wrote:

I had to import a bunch of SSURGO NetCDF data not too long ago
Michael (I was going back and forth with GRASS and MATLAB). I don't
seem to remember having any trouble with gdal (which means that it
must have worked!) Are you sure that the NetCDF is Lat Long?

What was your error exactly? Is the file too big to share? If not
send it to me and I'll take a look.

Best,

Kirk

Kirk R. Wythers
Department of Forest Resources
University of Minnesota
St. Paul, MN 55108
tel: 612.625.2261
email: kwythers@umn.edu <mailto:kwythers@umn.edu>

On Feb 7, 2012, at 12:33 PM, Michael Barton wrote:

I'm trying to help someone at NCAR import NetCDF data and we keep
getting an illegal north latitude error. Looking at the GDAL info,
I think we need to specify some additional metadata, but the GDAL
page stops short of giving an example of how to do this. Has anyone
imported climate data this way?

Thanks
Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
<Center for Social Dynamics and Complexity;

_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org <mailto:grass-user@lists.osgeo.org>
grass-user Info Page

--
Jennifer Boehnert
GIS Coordinator
National Center of Atmospheric Research
PO Box 3000
Boulder, CO, 80307

Helena wrote:

If there are still problems and if we can identify what needs to be
developed to make working with netCDF in GRASS more robust perhaps
this would be a good project for Google summer code
(hopefully OSGeo is participating this tear again)

hopefully :slight_smile:

anyway I think if there are georef problems they probably need to be
addressed at the GDAL side of things, not in GRASS per se.

that is why I thought it would be a good candidate for OSGeo GSoC,
as it would involve two OSGeo projects.
Hamish, do you know whether there is anything that needs to be done from our side to help
OSGeo become participating organization or is somebody working on the application already?
Org applications are due in about two weeks
and I haven't seen much happening on OSGeo lists.

Helena

regards,
Hamish
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Helena wrote:

Hamish, do you know whether there is anything that needs to be done
from our side to help OSGeo become participating organization
or is somebody working on the application already?
Org applications are due in about two weeks
and I haven't seen much happening on OSGeo lists.

It's under control, stay tuned....

in the mean time, please everyone take some time to review and expand the
GRASS GSoC ideas page:

   http://grass.osgeo.org/wiki/GRASS_SoC_Ideas_2012

(don't mind the broken pic, new thumbnails are broken on the wiki today)

Hamish