Opened 17 years ago

Closed 14 years ago

#1918 closed defect (fixed)

PGEO: Missing geometry types (ie. type 9/19/29)

Reported by: warmerdam Owned by: warmerdam
Priority: normal Milestone:
Component: OGR_SF Version: unspecified
Severity: normal Keywords: pgeo
Cc: flavio, hobu

Description (last modified by warmerdam)

Some personal geodatabases contain geometries that are type "19" which is not recognised by the personal geodatabase driver. This might be a mixed geometry type of lines and polygons or something like that.

Change History (4)

comment:1 by warmerdam, 17 years ago

Description: modified (diff)
Status: new → assigned

comment:2 by warmerdam, 15 years ago

There is also much discussion on this and related topics in #1484.

comment:3 by warmerdam, 15 years ago

Cc: hobu added

The file is quite large (76MB) so I'm not able to attach it.

A debug report from it looks like: 

PGeo: Translation shape binary to OGR geometry failed (FID=1)
PGEO: Unsupported geometry type:19
13000000B2439BC761C751C094C06B9EA03346409E257F805AC751C08717F4F6AE33464001000000
070000000000000044E66F815FC751C094C06B9EA0334640B2439BC761C751C0F19234AAAD334640
D64433445FC751C0BF8318C9AE3346409E257F805AC751C08717F4F6AE334640883BCA7F5BC751C0
E51AEBE9A0334640044B55E25EC751C07A47913BA133464044E66F815FC751C094C06B9EA0334640
00000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000

Some of the features have substantially larger geometries like: 

PGeo: Translation shape binary to OGR geometry failed (FID=7)
PGEO: Unsupported geometry type:19
130000002A75BD7383C751C03BE7F31C32704640DCDA081456C751C0554343C85170464001000000
1400000000000000180626D181C751C0CD6E1065367046402A75BD7383C751C0F322D3FE3A704640
A8FCD2E17CC751C045D56B453C704640447C868974C751C0670FBFD23F7046404A1EB3976DC751C0
7EB1578F41704640C46BC47762C751C036A174B44B704640EC058FBF59C751C0554343C851704640
00C63CE957C751C03CF177154E704640DCDA081456C751C0B048E9644A7046400247AF695DC751C0
A8300591417046406E32B79461C751C0BC66E1223D70464068316E1763C751C0CAE2E2293B704640
2E3ACA5B64C751C0A89B8A0C39704640A2872E4267C751C0268BB62C37704640E2219B8F6BC751C0
33AEF0E63770464064AB95FE6FC751C0BF1870BC3770464012921DB578C751C068D30B9B34704640
7C0B02C57EC751C03C656E7632704640FC9D5B4B80C751C03BE7F31C32704640180626D181C751C0
CD6E1065367046400000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000

Howard, if I provided the .mdb file do you think you could do that conversion to XML thing you did for the cirtest database?

comment:4 by chaitanya, 14 years ago

Resolution: → fixed
Status: assigned → closed

Type 9 and 19 are fixed in #2991. So is type 20.

Didn't find a reference to type 29 (typo perhaps). ​http://resources.esri.com/help/9.3/ArcGISDesktop/ArcObjects/esriGeometry/esriShapeType.htm

Note: See TracTickets for help on using tickets.