Good evening data modelers, this mail is to let you know that the topological support in the upcoming PostGIS 2.0 has been improved thanks to the input from an early tester, feeding topology constructor functions with pretty dirty data.
The outcome of that experience is reported here: http://strk.keybit.net/blog/2011/11/21/topology-cleaning-with-postgis/ Following this example I'd like to call you for further testing as I know you're all willing to keep your data in a safe and clean way and are thus looking forward to the new support. The specific example reported in the article had to do with the sole building of low-level topology (nodes, edges, faces), but there's more to PostGIS topology than that. The PostGIS topology lets you express your features as a composition of those primitives, embedded into a new data type (TopoGeometry) which you can use wherever you would use your good old Geometry values. >From the Zurich hackfest you can now also _see_ your TopoGeometry based layers in QGis w/out having to create an ad-hoc view for it. The hardest step for you to test use of TopoGeometry objects so far would be converting your Geometry layers to TopoGeometry layers. This is what ticket #1017 is willing to address [1]. The ticket is open looking for co-funders. [1] http://trac.osgeo.org/postgis/ticket/1017 Please keep in mind that feature-freeze for PostGIS-2.0 will happen in a couple of week so any _new_ feature would need to be started before that. Thank you. --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
