Opened 11 years ago

Closed 11 years ago

#4140 closed defect (fixed)

Set CoordinateDimension on Geoms from ShapeBuffer

Reported by: pramsey Owned by: Even Rouault
Priority: normal Milestone: 1.9.0
Component: OGR_SF Version: unspecified
Severity: normal Keywords: fgdb


I found this patch remaining in my working tree, which might explain the differing results we're getting in 3D objects?

Attachments (2)

pgeo_z.patch (2.5 KB ) - added by pramsey 11 years ago. (4.6 KB ) - added by Even Rouault 11 years ago.

Download all attachments as: .zip

Change History (4)

by pramsey, 11 years ago

Attachment: pgeo_z.patch added

comment:1 by Even Rouault, 11 years ago

No, it doesn't really help. I'm attaching the prototype for an autotest suite for the fgdb driver and I get failure on the wkbPoint25D and the other 25D tests.

$ python 
  TEST: ogr_fgdb_init ... success
  TEST: ogr_fgdb_1 ... OGRFeature(point25D):1
  str (String) = foo
  int (Integer) = 123
  real (Real) = 4.56
  POINT (1.0 2.0 -nan)

  TEST: ogr_fgdb_cleanup ... success

by Even Rouault, 11 years ago

Attachment: added

comment:2 by Even Rouault, 11 years ago

Resolution: fixed
Status: newclosed

Patch applied in r22628. Closing the ticket. The issues about 3D geometries is discussed there ( ) and is totally unrelated to the serializing/deserializing of shape buffers.

Note: See TracTickets for help on using tickets.