You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Opening a GeoPackage leaves out rows with no geometry, without a notice #1675
I searched the existing issues and did not find a duplicate.
This is a bug report, not a usage question.
What happened?
Opening a GeoPackage leaves out rows whose geometry is NULL, and says nothing. A table of two rows, one with a polygon and one with no geometry, opens as a layer of one feature. The row and its attributes are gone, with no notice.
A GeoPackage table can hold a row without geometry, and RustGIS writes one: exporting a layer with a feature that has no geometry keeps that row in the file. So a round trip through GeoPackage quietly loses those features.
rustgis-cli run --data nullgeom.geojson --cmd 'share.exportLayer={"layer":"nullgeom","path":"n.gpkg"}'
sqlite3 n.gpkg 'SELECT name, geom IS NULL FROM nullgeom;'
rustgis-cli info n.gpkg
sqlite3 shows both rows (area|0 and none|1). rustgis-cli info reports the layer with "features": 1 and prints no warning.
Expected behavior
The row without geometry opens as a feature with no geometry, as it does from GeoJSON, or the reader says how many rows it left out.
How are you running RustGIS?
Command line (rustgis-cli)
Version
Checked with a build of #1572's branch, which doesn't change how GeoPackages are read.
Activity
pick2510 commentedon Nov 10, 2026
Fixed by #1673: GeoPackage rows without geometry are now kept, in both the desktop and the browser reader.