The query to show a point at a time is explicitly skipping the repeated
last point by using
ST_npoints(geom)-1
I guess I will try upgrading Postgres and see if that fixes the problem.
Thanks!
- B
On 11/07/2012 02:00 PM, postgis-users-requ...@lists.osgeo.org wrote:
Looking more closely, you
Looking more closely, your node 2 polygon has 20 points and your node
1 polygon has 21. The point node 2 is missing is the closing vertex,
hence the unclosed error.
Now, how/why that could have happened seems a great mystery to me.
P.
On Mon, Nov 5, 2012 at 12:16 PM, Brian Peschel wrote:
> I am
On 11/06/2012 02:00 PM, postgis-users-requ...@lists.osgeo.org wrote:
You may have to upgrade to 1.5 (or perhaps just the latest 1.4
release) to get around an overly strict set of rules around geometry
validity that had a brief reign in the 1.4 series. The rules included
things like not accepting
You may have to upgrade to 1.5 (or perhaps just the latest 1.4
release) to get around an overly strict set of rules around geometry
validity that had a brief reign in the 1.4 series. The rules included
things like not accepting unclosed rings (fine) and not emitting
unclosed rings (whoa, nelly, tha
I am having a problem that I can't explain.
I have a 2 node Slony DB system.
Node 1: Ubuntu 10, Postgres 8.4.13-0ubuntu10.04, PostGIS 1.4.0-2,
libgeos 3.1.0-1
Node 2: Ubuntu 10, Postgres 8.4.3-1, PostGIS 1.4.0-2, libgeos 3.1.0-1
I have a polygon geometric in my database:
Table "public.tabl
