Geometry reading from Sde GDB

Question

HI,

I need to get geometry from Sde Geodatabase (Oracle 11g) stored in BLOB and write into csv or XML to other system to progess specially line and polygon.

What is the best way to get the data out either in xml or csv including geometry column? This has to be done outside ArcMAP or Arccatalog.

I know inside ArcMap using Arc Object, we can write read geometry but that will be slow and have dependancy of ArcMap instance. Anyway other easier and faster way to read geometry..

Thanks Manoj

ManojGarg · Answer

Thanks Vangelo.. let me try this as well. No particular DTD/XSD as long as I can get complete geometry's . I am using ESRI 9.3.1 SP2 There are an infinite number of XML formats -- did you have a particular DTD/XSD in mind? I doubt it would be easier or faster, but it would be simple and fast to use 'sdequery' to dump the data to ASCII (comma, tab, or pipe-delimited strings with Well-Known Text geometries).D: \>sdequery ArcSDE 10.0 Generic Query Tool Thu May 24 07:05:22 2012 ------------------------------------------------------------------------ sdequery -h sdequery [-C ] [-t ] [-w <'where clause'>] [-# ] [-l ] [-V ] [-q] [-A] [-v] [-N] [-vI ] [-d ] [-B ] [-P {UTM | ALBERS | LAMBERT | proj_code}] [-S ] [-Q {ATTR | JFA | JSF | JSFA | V3}] [-L ] [-R ] [-O ] [-a ] [-Fn ] [-E ] [-s ] [-i {instance | port#}] [-D ] [-u ] [-p ] D: \>sdequery -t table -d table.txt,'|' -s server -u user -p userspassword ... Line and polygon data tend to be very large in Well-Known Text, which will be the prime contributor to runtime performance. 'sdequery' is part of the se_toolkit tool suite. I've got "to-do" tasks for SQL, CSV, and KML export, but no time to do them in. - V

VinceAngelo · Answer

There are an infinite number of XML formats -- did you have a particular DTD/XSD in mind? I doubt it would be easier or faster, but it would be simple and fast to use 'sdequery' to dump the data to ASCII (comma, tab, or pipe-delimited strings with Well-Known Text geometries).D: \>sdequery ArcSDE 10.0 Generic Query Tool Thu May 24 07:05:22 2012 ------------------------------------------------------------------------ sdequery -h sdequery [-C ] [-t ] [-w <'where clause'>] [-# ] [-l ] [-V ] [-q] [-A] [-v] [-N] [-vI ] [-d ] [-B ] [-P {UTM | ALBERS | LAMBERT | proj_code}] [-S ] [-Q {ATTR | JFA | JSF | JSFA | V3}] [-L ] [-R ] [-O ] [-a ] [-Fn ] [-E ] [-s ] [-i {instance | port#}] [-D ] [-u ] [-p ] D: \>sdequery -t table -d table.txt,'|' -s server -u user -p userspassword ... Line and polygon data tend to be very large in Well-Known Text, which will be the prime contributor to runtime performance. 'sdequery' is part of the se_toolkit tool suite. I've got "to-do" tasks for SQL, CSV, and KML export, but no time to do them in. - V