Andrew,
>
> I'm passing a WKT CRS into GTIFSetFromOGISDefn(). The WKT is valid in that
> it conforms to the OGC representation v1.0 (12-063-r5). The function
> mentioned above parses the WKT into nodes properly, but the code that tries
> to interpret the actual WKT can't deal with the new
Hi,
I'm passing a WKT CRS into GTIFSetFromOGISDefn(). The WKT is valid in that
it conforms to the OGC representation v1.0 (12-063-r5). The function
mentioned above parses the WKT into nodes properly, but the code that tries
to interpret the actual WKT can't deal with the new specification.
On vendredi 9 décembre 2016 12:10:25 CET Even Rouault wrote:
> Hi,
>
> There have been some good remarks, one regarding integration with GEOS that
> I've taken into account in the implementation, another one regarding the
> possibility to get indexed TIN that I think can be later added if needed.
Hi Jukka,
Thanks for the report. Should now be fixed per r36849. This was introduced on
Nov 24th.
Crazy that the hundreds of existing tests didn't catch that, so I added a new
one :-)
Even
> Hi,
>
> This has worked for me and still works with GDAL version GDAL 2.0dev,
> released 2011/12/29
Sorry, what i said makes no sense at all. You shouldn't multiply the offset
with the y-resolution, although you should take the sign, like you did. Its
a bit strange that they provide the offset as a positive value.
Regards,
Rutger
--
View this message in context:
Hey,
Yes, that looks good. Although instead of using the -1, i think its meant to
be the actual y-resolution as provided in the metadata, but i'm never 100%
sure on those things. Its tempting to ignore it in this case, since its so
close to 1, but imagine what will happen if they increase the
Thanks again Rutger for your observation.
The bounding box was sent to me and I was already very happy the tiff is
located in The Netherlands ;)
I did a closer look at the meta data and with your explanation I come up
with this 'formula':
The ul is 0.0, -1 * geographic_geo_row_offset
lr is
Hi,
This has worked for me and still works with GDAL version GDAL 2.0dev, released
2011/12/29
gdaladdo -r average -ro --config COMPRESS_OVERVIEW JPEG --config
PHOTOMETRIC_OVERVIEW YCBCR --config INTERLEAVE_OVERVIEW PIXEL input.tif 2 4 8
16 32 64
However, GDAL 2.2.0dev, released 2016/99/99
Thank you, I was not aware of the -preserve_fid qualifier, it works as
expected when I use it.
Sorry about the noise.
César Martínez
2016-12-09 9:36 GMT+01:00 Bo Victor Thomsen :
> Have you tried to use the -preserve_fid qualifier ??
>
> ex.
>
> ogr2ogr -preserve_fid
Hey,
Based on the metadata from the file you posted i would guess the
x-coordinate of the right edge (lrx) should be about ~700km or ~70m.
The column offset is 0, and there are 700 columns in the file which are
slightly over 1km. How would you end up with 800?
You can calculate the other
Thanks Rutger,
You are completely right. I assumed the coordinates were in the same
projection as the project string.
Menno van Scheers replied me directly and suggested I should use 0.0,
-3650.000, 800.000, -4415.000 as ullr coordinates.
I tried it and now the GeoTiff is where I expect it to
Hey Paul,
If you assign the RD projection with 'a_srs', you should also assign the
'ullr' coordinates in that same projection, not in lat/lon degrees like you
do now.
Regards,
Rutger
--
View this message in context:
I'm trying to use the precipitation accumulations from our national weather
agency: https://data.knmi.nl/datasets/radar_tar_corr_accum_03h/2.0
The data is in HDF5 with two subsets.
I only need one subset and I need the data in WGS84.
I'm using GDAL v2.2 from GisInternals.com
I tried using
13 matches
Mail list logo