I could not find any. There is a similar bug in DODS driver (it assumes
'lat' and 'lon' names for dimension variables), but fixing requires
large update/debugging.
On 08/07/2012 04:01 PM, Etienne Tourigny wrote:
yes please! are there any other areas which could require a similar fix?
Etienne
What version are you using? I seem to remember something like this in a
ticket I filed. I thought it was fixed in 1.9.1.
kss
On Tue, Aug 7, 2012 at 5:38 AM, Etienne Tourigny wrote:
> Hi,
>
> km units are supposed to work...
>
> Here is the code where "km" units are detected, which set the WKT
Hi Kyle,
Anton identified the problem, the driver assume that x dimension is
named "x", and in his dataset it is named "xc". The fix you refer to
probably would not work in this case either.
Etienne
On Tue, Aug 7, 2012 at 10:59 AM, Kyle Shannon wrote:
> What version are you using? I seem to r
Hi,
km units are supposed to work...
Here is the code where "km" units are detected, which set the WKT
units to 1000m.
/* add units to PROJCS */
if ( pszUnits != NULL && ! EQUAL(pszUnits,"") ) {
if ( EQUAL(pszUnits,"m") ) {
oSRS.SetLine
Dear Etienne,
I faced the following problem with the NetCDF driver:
Units of the dimension variables are 'km' and values in the SRS are in
meters, of course (e.g. Earth radius). Hence the calculated GeoTransform
is 1000 times less than should be and the calculate latlons are incorrect.
However
