<html>
<head>
</head>
<body>
<pramsey@opengeo.org>Hallo<br />
<br />
><br />
>Yep, like other companies developing propietary software. The point is<br />
>I don't understand why using a mix of numbers and arrays whose<br />
>elements index tables to simply represent a polygon. Saving storage<br />
>space? I don't know. The PostGIS way, closer to OGC standard, is much<br />
>easier, IMHO.<br />
>
<jorge.arevalo@deimos-space.com><br />
<br />
I don't know what this Oracle representation looks like but from above it sounds like it might be about some topological model. <br />
In PostGIS representation I guess it is difficult to describe two neighbor polygons without repeating the shared vertexes for both polygons?<br />
<br />
/Nicklas<br />
<br />
<br />
</jorge.arevalo@deimos-space.com></pramsey@opengeo.org>
</body>
</html>