Thank's for your reply. I think we'll go same ways as you describe - use two main tables `polygons` and `points` and couple supporting tables which handle relationships and additional content.
Michal K. On Mon, Apr 9, 2012 at 3:05 PM, Andrea Peri <[email protected]> wrote: > >My question is how to design database for this system? I was thinking of 2 > >tables polygons and points, but I'm not sure if it's good way of thinking. > > > Hi, > we chhose by desing to use two table for the geometries (lines and > polygons). > And many tables to link the geometries inside these two tables. > The two tables with geometries was called ""elementary_lines" (arcs) and > "soil" (polygons). > > The main rule is that every element of the "elementary lines" is a linear > object and it is also a segment on the boundary of one or two element > polygons of the "soil" . > Another rule is that the "soil" will give a "full cover of the soil". And > every point has one and only one polygon to cover it. > > Every object of the "elementary lines" and of the "soil" as an unique > alphanumeric universal identifier. > It allow to have others table without geometry that allow to have distinct > and specific attributes for every specific kind of object. > > This choice was need to grant a full topology for all the objects of the > db. > > Also we develope a profile of "GML topological" to allow the exchange of > out database. > > -- > ----------------- > Andrea Peri > . . . . . . . . . > qwerty àèìòù > ----------------- > > > _______________________________________________ > postgis-users mailing list > [email protected] > http://postgis.refractions.net/mailman/listinfo/postgis-users > >
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
