{{ message }}
Repository navigation
BeginBinaryImportAsync doesn't import Altitude #6567
Description
I'm trying to import points and lines, with altitude, using BeginBinaryImportAsync, however the altitude doesn't seem to get imported.
The easiest way to verify this, is to change the TestData in GeoJSONTests to look like this:
new()
{
Geometry = new Point(
new Position(longitude: 1d, latitude: 2d, altitude:3d))
{ BoundingBoxes = [1d, 2d, 1d, 2d] },
CommandText = "st_makepoint(1,2)"
},
and run the 'Import_geometry' test..... It'll fail
also if you check the db, you see a point with only longitude and latitude:
POINT (1 2)
TIA
/Søren
Activity
smolesen commentedon May 8, 2026
Playing around with 'NpgsqlNetTopologySuite' instead, it turns out that the column has to be defined as 'POINTZ', however if I change the above mentioned test to use POINTZ
I get this error:
Not quite sure what that means... or how to move on from here, except use 'NpgsqlNetTopologySuite' instead
vonzshik commentedon May 13, 2026
Well, geometry explicitly documented as two-dimensional spatial object, so yeah, no z coord.
xfischer commentedon May 14, 2026
@smolesen, adding to @vonzshik. There is maybe a confusion between builtin postgres geometry (2 dimensions only) and the PostGIS ones.
Using PostGIS, when you open Npgsql connection you should ask to handle Z coordinates this way:
await using var conn = await OpenConnectionAsync(handleOrdinates: Ordinates.XYZ);xfischer commentedon Jun 9, 2026
Regarding the first issue (GeoJSON with altitude), there's a bug in the converter: reading Z values is supported but writing isn't.
Will submit a PR.
npgsql#6567 write geojson with Z
npgsql#6567 write geojson with Z
npgsql#6567 write geojson with Z
npgsql#6567 write GeoJSON with Z values