Dear list,
I found a unexpected behavior of the SQLITE dialect. See this example
where I access ten features of a remote GeoJSON:
ogr2ogr \
-dialect SQLITE \
-sql "SELECT * FROM chapters LIMIT 10" \
-f GPKG output.gpkg \
https://raw.githubusercontent.com/maptime/maptime.github.io/master/_data/chapters.json
The resulting layername with SQLITE dialect is "SELECT". In contrast,
with OGRSQL dialect, the resulting layername is "chapters" - which is
more logical to me.
Any ideas why this behavior is different between SQLITE and OGRSQL dialect?
Thanks in advance and best wishes,
Jakob
--
Jakob Miksch
www.jakobmiksch.eu
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
