Cannot Delete Error 3912
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 05 Oct 2016 21:42:40 GMT by s_hv997 (squid/3.5.20)
delete slivers (or gaps) Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Fri, Oct 31, 2014 at 10:17:48AM -0400, Guillaume Drolet wrote: > I created a topology for 2290 polygons and populated cannot delete files error 0x80070570 a topogeom column [...] > I need to fix 1) extra nodes along edges 0x80070570 error repair tool that are not at an > intersection and 2) sliver polygons. [...] > For cases in 2, I can remove some cannot delete the file or directory is corrupted and unreadable slivers with 'ST_RemEdgeModFace' but > some of them I just can't delete: > > I get either: > > ERROR: TopoGeom 1123 in layer 1 (de_20k_topo_tests.LAYER1.) cannot be > represented healing faces 1514 and 1502 This http://answers.microsoft.com/en-us/windows/forum/windows_vista-update/error-0x80070570-cannot-delete-file/3344a66d-5d2b-4001-a77e-531cc62be951 error means that a TopoGeometry object exists (with id=1123) that's defined as containing only one of the faces separated by the edge you're trying to remove. The fix here would be to find faces that take part in the composition of multiple TopoGeometry objects and those NOT taking part in the composition of any TopoGeometry object. I've seen GRASS GUIs referring to those 2 classes as "polygon0" and "polygon2", enough that http://lists.osgeo.org/pipermail/postgis-users/2014-October/039734.html I've been thinking it could be useful to have them shown as layers in the QGIS viewer for PostGIS Topology. You should be able to extract those faces with a query to the relation and the layers tables. So basically you first have to fix the TopoGeometry objects and then can safely drop the no-more-needed edges. > Or, when trying with remove a node with 'topology.ST_NewEdgeHeal': > > ERROR: SQL/MM Spatial exception - other edges connected (3912) > > In this particular example, two edges are connected two the same two > nodes, similar to what was discussed here: > > http://postgis.17.x6.nabble.com/PostGIS-1955-Exception-when-2-edges-passed-to-ST-ModEdgeHeal-that-are-attached-to-the-same-2-nodes-td4999383.html > > But according to that discussion thread, this was fixed in an earlier > version (I'm using topology version 2.1.3). > > Maybe my problem is different but I'll need your help to get it > sorted. Here's an example showing the small face (1502) I want remove: > > https://dl.dropboxusercontent.com/u/5196336/example1.bmp Which edge ids did you pass to ST_NewEdgeHeal ? Is the topology in a good state according to topology.ValidateTopology ? --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html Previous message: [postgis-users] Topology: cannot delete slivers (or gaps) Next message: [postgis-users] Topology: cannot delete slivers (or gaps) Messages sorted by: [ date ] [ thread ]
files into Postgis db (windows)? Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Fri, Oct 31, 2014 at 12:19:31PM -0700, Guillaume Drolet wrote: > Hi Sandro, > > Thanks for your help! > > http://lists.osgeo.org/pipermail/postgis-users/2014-October/039741.html topology.ValidateTopology gives this: > > error id1 id2 > character varying integer integer > ------------------ ----------- ---------------- > face has no rings 1831 > > If I calculate the area of face 1831 > (st_area(st_getfacegeometry('de_20k_topo', face_id))), I get a NULL value. I suggest you take a look at edges having face 1831 on either the right or left edge. Do any edge exist ? > I also find I have some 650 cannot delete of these slivers with an area below 75 m2 while > most of my correct polygons have an area above 300 000 000 m2. The correct procedure to drop those slivers would be to assign those small areas to the (closest|biggest|leftmost|youpickit) TopoGeometry object, to one and only one, and then, if you really need it, drop the edge internal to the TopoGeometry. I made a QGIS plugin which may help you do some the file or of these things manually, which is useful in some cases, mainly to understand the issues. > Re the edges passed to ST_NewEdgeHeal, in the example I sent it was edges > 3908 and 3909. So the error was right about there being another edge attached to the node: ERROR: SQL/MM Spatial exception - other edges connected (3912) I'm guessing 3912 and 3908 are the two parallel edges in the picture you attached: https://dl.dropboxusercontent.com/u/5196336/example1.bmp Again, QGIS may help you getting more info out of the visual, enable the DBManager core plugin, select your topology schema and select Schema->TopoViewer from the menu. > PS. Forgot to mention that in the first topology I had created, I used a > tolerance of 2.0 meters instead of 1e-4 meters. While that yielded much less > slivers, I was getting way more of those nodes not located at an > intersection. What is best? It's probably easier to clean up nodes for an areal topology than to clean up faces. With my QGIS plugin (PostGIS Topology Editor) you can select all nodes and click on a button which will drop all the ones that are safe to drop. --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html Previous message: [postgis-users] Topology: cannot delete slivers (or gaps) Next message: [postgis-users] Import gpx files