<pre>>Do you have any answer to Jorges initial question why the Oracle geometry representation (sdo_geometry) seems so complicated if it is not about topology? <br><br>It not seem complicated it is complicated :)<br><br>
1)<br>almost in the 10g version, oracle don't support EPSG definition of SRS,<br>but use another coding.<br><br>2)<br>define a new table is easy:<br><br>create table table-1 ( id number, poi_name varchar2(32), location sdo_geometry);<br>
<br>but when need to insert in it is a bit more complex then in postgis.<br><br>insert into table-1 values<br>( 1, <br> 'aaaa', <br> sdo_geometry(<br> 2001, // sdo_gtype attribute: "2" in 2001 mean 2-dimensionality<br>
NULL, // this was the SRID (SRS) code<br> sdo_point_type (<br> xx, // first coordinate,<br> yy, // second coordinate,<br> NULL, // third coordinate<br> ),<br> NULL,<br>
NULL<br> ),<br>);<br><br>as you can see insert a point is more complex then a simple WKT use from postgis.<br><br>Too complex again if you want store a Linestring or a polygon beacause must use a structure like an array.<br>
<br>sdo_geometry (<br> 2001, // again use 2001 because you polygon or linestirng is 2-dimensional<br> 8307 , // srid code<br> NULL, // sdo_pont attribute set to null<br> sdo_elem_info_array (<br> ...<br> ),<br>
sdo_ordinate_array (<br> ....<br> )<br>)<br><br>etc....<br clear="all"></pre><br>-----------------<br>Andrea Peri<br>. . . . . . . . . <br>qwerty אטלעש<br>-----------------<br><br>