Group, It appears when using "-unscale" during a gdal_translate conversion, the defined NoData value is used when the offset/scale are applied. Not sure if this is intentional?Let me set up an example:note: It is understood that scale/offset are not applied to values during gdalinfo for -mm> gda
I don't understand the question (you didn't put any question in your
message), but I tried the mif/mid files provided. The first time I got
an error:
"Not enough CoordSys parameters specified for projection 8." (which
means State plane 1983).
You provided this:
CoordSys Earth Projection 8, 74, 'm',
Dear devs,
I'd like to draw attention to a bug in the rasdaman dataset (to be more
specific: its GetGeoTransform method). I created a new ticket [1] and
also added a resolving patch. I hope it will be applied to the trunk soon.
Thanks,
Fabian
[1] http://trac.osgeo.org/gdal/ticket/4341
__
Koszonom nagyon szepen.
(and that's the limit of my written Hungarian - I was 3 years old when
we came to South Africa)
Big thanks,
Zoltan
On 2011/11/11 10:53, Luca Sigfrido Percich wrote:
Hi Zoltan,
tessek. (If i remember the little hungarian I used to know)
Converted with MapInfo 7.5 Ta
Hi,
I am trying to get some ogr2ogr and mitab issues regarding NULL values
in MID & TAB files, resolved.
My (no longer so trusty) MapInfo v4.52 doesn't seem to recognize the
dongle in Windows 7 (I have tried different Sentinal drivers, but no luck).
The thread of the problem can be found at: