Ah, easy 😊
From: Even Rouault
Sent: Monday, July 22, 2024 8:30 PM
To: Joaquim Manuel Freire Luís ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Extracting data from a parquet file
Le 22/07/2024 à 21:10, Joaquim Manuel Freire Luís a écrit :
Even,
Thanks for the explanation. But how did you
Le 22/07/2024 à 21:10, Joaquim Manuel Freire Luís a écrit :
Even,
Thanks for the explanation. But how did you find the name of the
geometries (geo_point_2D and geo_shape)? Loading the
“world-administrative-boundaries.parquet” in a binary editor I can see
them there, but that’s certainly not
Even,
Thanks for the explanation. But how did you find the name of the geometries
(geo_point_2D and geo_shape)? Loading the
“world-administrative-boundaries.parquet” in a binary editor I can see them
there, but that’s certainly not the way to find these things.
Joaquim
From: Even Rouault
Sen
Thanks Even
Then I think that the awk command is enough if anybody (including me) needs
it.
(note for future users: if step size is different in both directions, use
dx and dy keys. Check AAIGrid code)
On Mon, 22 Jul 2024 at 19:15, Even Rouault
wrote:
> Javier,
>
> yes I've came across similarl
Javier,
yes I've came across similarly looking grid files occasionally. I'm not
quite sure which ancestor format is behind. This is a bit similar to the
IGN France ASCII grid .mnt format documented at
https://geodesie.ign.fr/contenu/fichiers/documentation/grilles/notices/Grilles-MNT-TXT_Format
Hi
I have seen some raster files with this format
-4.98 14.98 -79.98 -66.016667 0.0
0.0
-5.258 -5.301 -5.345 -5.393 -5.444 -5.499 -5.555 -5.615 -5.682 -5.752
-5.823 -5.886 -5.938 -5.986 -6.036 -6.093 -6.157 -6.226 -6.296 -6.358
-6.413 -6.462 -6.516 -6.5
Merci Even,
I can confirm that the workaround you suggested works correctly.
>From the performance I was getting beforehand, I strongly believe that the
mixup happening on the overview levels was causing my hat/lr dataset to
never be used at all.
Thank you for the quick response,
Thomas
On Mon, Ju
Joaquim,
The GeoPackage format only supports one geometry field per layer. and
the QGIS OGR provider doesn't know currently how to handle several
geometry fields per layer too
To do what you want, you need to explictly select the desired geometry
field name with:
ogr2ogr out.gpkg world-adm
Salut Thomas,
There were actually 2 issues:
- contrary to what the documentation stated, OVERVIEW_0_ metadata
items were simply ignored, hence you only got overviews starting at the
1/4 reduction
- and the documentation also lied when implying that it would
automatically add overviews o
Hi list,
I'm experimenting with the GTI driver and hitting an issue when trying to
add overviews.
I'm compiling a large number of adjacent non-overlapping tiles, each of
which has is own bundled overviews:
gdalinfo /*snip*/tile-1377-471.tif
Size is 32768, 32768
Origin = (3.057607090103000,48.4207
10 matches
Mail list logo
