PM, Lee Eddington <
>>> lee.w.edding...@gmail.com> wrote:
>>>
>>>> Roger,
>>>>
>>>> Thank you for the info and link. Using a modified version of your code
>>>> I was able to create and import into GRASS a GeoTIFF with the
oreferencing. The coordinate system units are in meters though, and I'd
>>> prefer to have them in degrees lat/lon. Do you know if there's a way to
>>> specify that using the oar or gdal routines in your code?
>>>
>>> Thanks,
>>> Lee
>
>
>> Forwarding to the list and others...
>>
>> -- Forwarded message --
>> From: Roger Veciana i Rovira
>> Date: Mon, Nov 25, 2013 at 9:35 AM
>> Subject: Re: [gdal-dev] WRF NetCDF import
>> To: Etienne Tourigny
>>
>>
>>
at 9:35 AM
> Subject: Re: [gdal-dev] WRF NetCDF import
> To: Etienne Tourigny
>
>
> As Etienne told you, the geotransform and projection from your files is
> not in the format that GDAL can understand.
> I wrote a script that reads the projection and calculates the geotransf
The "georeferencing info" you refer to is non-standard, and GDAL cannot use
that. It (and presumably the grass provider, although I don't know) use the
CF standard for encoding lat/lon information. what is the output of
gdalinfo NETCDF:test_full.nc:HGT
I don't know how the grass provider deals wit
I'm trying to use r.in.gdal in GRASS GIS to import Weather Research &
Forecasting (WRF) model NetCDF output. There have been some tips provided
by the GRASS users list, but none have worked for me. I can import the
data as a simple x,y array with no georeferencing, but information about
georefere