After a little digging, it appears that the netCDF driver does not support the tag:<br><br>Lambert_Conformal:standard_parallel<br><br>it supports:<br>Lambert_Conformal:standard_parallel_1 <br>and: <br>Lambert_Conformal:standard_parallel_2<br>
<br>I am not sure if the tag is out of specification, or if the driver needs to be updated. I also notice OGRSpatialReference has a separate function for setting a Lambert Conformal Conic with single parallel:<br><br>OGRErr SetLCC1SP( <span class="code-type"><b>double</b></span> dfCenterLat, <span class="code-type"><b>double</b></span> dfCenterLong, ...<br>
<br>but this is not referenced in the netCDF driver.<br><br>So, my next question is:<br>Can you specify the value of SP_1 and SP_2 as the same parallel in the standard LCC, or do you have to set LCC1SP<br clear="all"><br>
Thanks everyone for your patience,<br><br>kss<br><br># ===================<br>Kyle Shannon<br>Physical Science Technician<br>RMRS Fire Sciences Lab<br>Fire, Fuels & Smoke - RWU 4405<br>5775 Highway 10 W.<br>Missoula, MT 59808<br>
(406)646-6577<br><a href="mailto:kshannon@fs.fed.us">kshannon@fs.fed.us</a><br><a href="mailto:ksshannon@gmail.com">ksshannon@gmail.com</a><br># ===================<br>
<br><br><div class="gmail_quote">On Tue, Jan 12, 2010 at 11:26 AM, Christopher Barker <span dir="ltr"><<a href="mailto:Chris.Barker@noaa.gov">Chris.Barker@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Kyle Shannon wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
ncdump -h reports the same correct standard parallels (25) whereas Coordinate System reports 0 for both standard parallels. It appears the projection is a Lambert Conformal Conic with 2 standard parallels, but they are the same effectively making it a lcc with 1 standard parallel.<br>
</blockquote>
<br></div>
It looks like GDAL doesn't understand those parameters:<br>
<br>
from: <a href="http://www.gdal.org/frmt_netcdf.html" target="_blank">http://www.gdal.org/frmt_netcdf.html</a>:<br>
<br>
"""<br>
Georeference<br>
There is no universal way of storing georeferencing in netCDF files. The driver first tries to follow the CF-1 Convention from UNIDATA looking for the Metadata named "grid_mapping". If "grid_mapping" is not present, the driver will try to find an lat/lon grid array to set geotransform array. The NetCDF driver verifies that the Lat/Lon array is equally space.<br>
<br>
If those 2 methods fail, NetCDF driver will try to read the following metadata directly and set up georefenrencing.<br>
<br>
* spatial_ref (Well Known Text)<br>
...<br>
"""<br>
<br>
So to get the spatial reference right, the netcdf file needs a proper spatial_ref parameter in WKT format. What does ncdump tell you it has? If it's not right, you can either get whoever is running your server to fix it, or you can fix it yourself by processing the nc file with something:<br>
ncdump-> filter -> ncgen<br>
NCO utilitites<br>
python (or perl, or ???) scripts.<br>
<br>
<br>
good luck!<div><div></div><div class="h5"><br>
<br>
-Chris<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
Christopher Barker, Ph.D.<br>
Oceanographer<br>
<br>
Emergency Response Division<br>
NOAA/NOS/OR&R (206) 526-6959 voice<br>
7600 Sand Point Way NE (206) 526-6329 fax<br>
Seattle, WA 98115 (206) 526-6317 main reception<br>
<br>
<a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a><br>
</div></div></blockquote></div><br>