>
> On a related note... is there any tricks in the GDAL API which can be
> used to "force" a geometry type for created tab files? E.g. if I
> create a tab file, specifying Point geometry type, the initially empty
> result layer has no fixed geometry type. This makes it unusable in
> QGIS, since Q
On 10 December 2017 at 00:58, Even Rouault wrote:
> As underlined by Alvaro and Ari, the format doesn't distinguish PointZ and
> PointZM in the header.
>
> GDAL has a logic to look by default at the first geometry
> (ADJUST_GEOM_TYPE=FIRST_SHAPE open option) and see if it has a non nodata M
> valu
Nyall,
As underlined by Alvaro and Ari, the format doesn't distinguish PointZ and
PointZM in the
header.
GDAL has a logic to look by default at the first geometry
(ADJUST_GEOM_TYPE=FIRST_SHAPE open option) and see if it has a non nodata M
value, if
so it exposes PointZM, otherwise PointZ
But
Nyall Dawson kirjoitti 09.12.2017 klo 18:04:
Hi all,
I'm trying to track down some odd behaviour in QGIS, and determine
whether this is a qgis bug, gdal bug, or shapefile limitation.
If I create a new shapefile layer using GDALDatasetCreateLayer, with a
geometry type of wkbPoint25D (actually a
between both types reading the Mmin and Mmax
values of the header file.
De: Nyall Dawson
Para: gdal dev
Enviado: Sábado 9 de diciembre de 2017 8:05
Asunto: [gdal-dev] Shapefiles and z dimensions
Hi all,
I'm trying to track down some odd behaviour in QGIS, and determine
whe
Hi all,
I'm trying to track down some odd behaviour in QGIS, and determine
whether this is a qgis bug, gdal bug, or shapefile limitation.
If I create a new shapefile layer using GDALDatasetCreateLayer, with a
geometry type of wkbPoint25D (actually any of the 25D) types, then the
resultant layer A
