Ivan: I thnk the problem with using filenames is that it creates a
different de facto standard that doesn't necessarily suit everyone - eg,
what if the data have hours, minutes, and seconds? Also, it means that
moving files out of the directory loses temporal metadata,
Even: I like your suggestion
My experience with XMP was positive.
Some time ago I did a couple of PRs to store the XMP in the original TIFF
tag (not in GDAL metadata), and to copy it properly when creating(copying)
a COG.
GDAL is not parsing the XML content, it is your task. We are using exiv2,
but I hope there are other/bette
Hi,
this comes from https://trac.osgeo.org/gdal/ticket/4458
The full list of laundered field name is at
https://github.com/OSGeo/gdal/blob/94625cba3367c5709175e5b7a037febe737742f0/ogr/ogrsf_frmts/filegdb/FGdbUtils.cpp#L522
There's a hidden -lco LAUNDER_RESERVED_KEYWORDS=FALSE layer creation
Hello,
I am attempting to create an ogr.OFTDateTime field named "date", within a file
geodatabase table. However anytime a field definition is created with the name
"date", once the layer tries to create the field, I get receive a warning:
Warning 6: Normalized/laundered field name: 'date' to '
On Fri, 13 May 2022 at 14:29, Even Rouault wrote:
>
> The 3.5.0 release is a new feature release with the following highlights:
>
> * [RFC 84](https://gdal.org/development/rfc/rfc84_cmake.html):
>Addition of a CMake build system, which deprecates the existing
>autoconf/automake and nmake b
Simon,
metadata is a tricky subject. To my knowledge, up to know most data
producers of GeoTIFF files have used minimalist embedded metadata in the
TIFF file itself (mostly using the ImageDescription, Copyright field),
but rather using text or xml side car files to provide their own
metadata
Hi,
I am developing a raster service (WMS, OGC API Maps) using the Java bindings of
GDAL.
When I execute a translate (or a warp) to extract a portion of the original
photo, the result saves a new file by default. For performance purposes, I
would like the result to stay in memory from which I
Hi,
Osmconvert is non-Java http://m.m.i24.cc/osmconvert.c
OSM pbf does not support indexes
https://dev.openstreetmap.narkive.com/Z8cvwP7Y/osm-indexing-of-pbf-files
-Jukka Rahkonen-
Lähettäjä: gdal-dev Puolesta Schmetzer,
Tobias
Lähetetty: perjantai 13. toukokuuta 2022 15.30
Vastaanottaja: gda
Tobias,
please file an issue about that at https://github.com/OSGeo/gdal/issues/new
We can likely increase the limit and make it runtime configurable
Even
Le 13/05/2022 à 14:30, Schmetzer, Tobias a écrit :
Hello,
thanks for that helpful analysis and hints! So I get the planet.pdf
file
Hello,
thanks for that helpful analysis and hints! So I get the planet.pdf file is
read in entirely before any spatial or key-wise restrictions are applied to
narrow down the data that needs to be treated.
Of course using a 1°x1° area in a planet file doesn’t make much sense but this
tiny
Hi,
On behalf of the GDAL/OGR development team and community, I am pleased to
announce the release of GDAL/OGR 3.5.0. GDAL/OGR is a C++ geospatial data
access library for raster and vector file formats, databases and web
services.
It includes bindings for several languages, and a variety of com
I declare this motion passed with +1 from PSC members HowardB, JukkaR,
SeanG and me.
Even
Le 11/05/2022 à 11:36, Even Rouault a écrit :
Hi,
Things should be good enough with RC4.
Motion:
Adopt GDAL 3.5.0RC4 as final 3.5.0 release
Starting with my +1
Even
--
http://www.spatialys.com
My s
Hi,
The error comes from
https://github.com/OSGeo/gdal/blob/master/ogr/ogrsf_frmts/osm/ogrosmdatasource.cpp#L2067
and it happens before your SQL, when GDAL is reading the data in from the huge
planet.pbf file.
if( nNextKeyIndex >= 32768 ) /* somewhat arbitrary */
The error means that there ar
Dear GDAL dev team,
I am not sure if I am following a wrong approach, if there is an issue with the
osm driver, the distributed OSM file or if the error message is just ambiguous
and could be improved.
I used ogr2ogr to select 12 keys to be extracted as polygons along with
something around 40
14 matches
Mail list logo