Thank you for these scenarios Paul. I will include them in my article. Do you mind if I mention you in the credits?
The Sunburned Surveyor On 8/29/07, Paul Austin <[EMAIL PROTECTED]> wrote: > One reason would be precision and scale. Consider a building small > buildings could be 1m sq so these we would encode as points and larger > buildings we would use polygons. > > On a related note why would I want to have two geometries on the same > feature, consider a two sided river I may want to have the polygon of > water boundary and a MultLineString to represent the banks of the river. > This would allow be to render the river in light blue and the banks in > darker blue but not have the darker blue lines where another river joins > in with this one. > > Paul > > > Sunburned Surveyor wrote: > > I'm writing a short article about working with layers that contain > > Features represented by different Geometry types. One of the questions > > that I am trying to answer in the article is: > > > > "When is it appropriate to store features represented by different > > geometry types on the same layer?" > > > > I must say that I'm having a difficult time answering this question, > > since this is not something I do in OpenJUMP. Instead of trying to > > guess at a reason, I thought I would ask other users. > > > > Why do you have layers that contain features represented by different > > geometry types? > > > > Thanks, > > > > The Sunburned Surveyor > > _______________________________________________ > > jump-users mailing list > > [email protected] > > http://lists.refractions.net/mailman/listinfo/jump-users > > > > _______________________________________________ > jump-users mailing list > [email protected] > http://lists.refractions.net/mailman/listinfo/jump-users > _______________________________________________ jump-users mailing list [email protected] http://lists.refractions.net/mailman/listinfo/jump-users
