I have a whole set of line segments or tracks that represent real tracks or, in some case, boundaries between areas.
These segments form a network of lines on the map.
I have a number of GIS layers, e.g. walking tracks, vehicle tracks and a variety of zones (areas delimited by a set of segments) with a many to many relationship between segments and layers.
I figure the best way to deal with this is to put all the segments into a postgis table as individual features and then create a link table for each layer that lists then segments needed for that layer.
That way I have just one copy of each segment to maintain.
Is there a better way of doing this? Can anyone point me to some tutorial material in this area.
Indeed, views (or sql queries - which amount to the same thing) were what I was assuming that I would use to build the layers. I am pretty sure I know how to do what I want.
My questions was more along the lines of "Is the approach sound?". As a GIS novice but with a extensive IT background it seems to me that this must be a common situation i.e. having features that are used in multiple layers where you only want to maintain one copy of the feature. I was wondering if the obvious approach (from a relational database point of view) was what people used in practice or if there were other approaches.