On Wed, Feb 25, 2015 at 12:14 PM, Joseph Spenner joseph85...@yahoo.com
wrote:
DBD::Pg::st execute failed: ERROR: Error performing intersection:
TopologyException: Input geom 1 is invalid: Self-intersection at or near
point -381688.06935935974 -1206669.4272876547 at -381688.06935935974
On Mon, Feb 9, 2015 at 6:25 AM, Sandro Santilli s...@keybit.net wrote:
First of all I confirm it still happens with GEOS=3.5.0dev-CAPI-1.9.0
r4038.
Second, I took a look at a random set (geom_set_id=1) and I found it pretty
big. That's to say you could probably further reduce the dataset for
On Sun, Feb 8, 2015 at 9:31 PM, John Abraham j...@hbaspecto.com wrote:
Well I could say that using PostGIS ST_Intersects with messy data always
seems to give me TopologyExceptions. I've had luck with various
combinations of ST_SnapToGrid and ST_Buffer(0), but with messy data there
always
On Tue, Feb 3, 2015 at 11:28 AM, BladeOfLight16 bladeofligh...@gmail.com
wrote:
I'm trying to create a polygon overlay. The basic process is relatively
simple: 1) Get the boundaries 2) Union the boundaries to node the
linestrings 3) Polygonize the noded outlines 4) Filter out holes using
I have double checked my code 'layer_id' is coming straight from calling
$dbh-primary_key( undef, undef, 'layer');
Your table doesn't even have a layer_id column. Try this query to be
sure: SELECT
layer_id FROM layer;. It should error out saying that the column doesn't
exist. It definitely
On Tue, Feb 3, 2015 at 11:41 PM, Puthick Hok hputh...@gmail.com wrote:
I use Perl DBI to connect to Postgresql. If I create the postgis
database using 'CREATE EXTENSION' method, Perl DBI returns 'layer_id' as
the primary key of my layer table. If I create the postgis database using
the old
I'm trying to create a polygon overlay. The basic process is relatively
simple: 1) Get the boundaries 2) Union the boundaries to node the
linestrings 3) Polygonize the noded outlines 4) Filter out holes using a
contains or intersects test. The problem I'm running into is that I'm
getting
On Fri, Jan 9, 2015 at 6:16 PM, Paul Ramsey pram...@cleverelephant.ca
wrote:
Yes, I could see that as a reasonable interpretation. Just another in
the large collection of corner cases opened up by allowing typed empty
(my fault). The code probably just tests for empty and reflects the
input
Ran across some behavior that seems odd to me:
SELECT ST_AsText(ST_Boundary(geom))
FROM (VALUES ('POLYGON EMPTY'::GEOMETRY),
('MULTIPOLYGON EMPTY'::GEOMETRY),
('LINESTRING EMPTY'::GEOMETRY),
('MULTILINESTRING EMPTY'::GEOMETRY)
) g (geom);
results in:
On Wed, May 21, 2014 at 10:10 AM, Nahum Castro pedro1...@yahoo.com wrote:
When I save a poligon on z0_poligono_corte, use that polygon to intersect
with polygons on layer a_n_p_13 capa and save the result on z0_a_n_p_13
but don't work and there are not errors on postgresql.log.
You'll need
On Sat, Nov 9, 2013 at 12:39 AM, John Smith jayzee.sm...@gmail.com wrote:
looks like mapserver 6.4.0 can't create geom with postgis 2.1.0. can
someone confirm that before i rollback to ms 6.2.1 or before :( is there
any other solution?
just trying to connect ms 6.4.0 with pg 2.1.0 but
On Sun, Oct 27, 2013 at 5:20 PM, Paul Ramsey pram...@cleverelephant.cawrote:
Wow, that page really goes out of its way to make sure you don't want
to use PostGIS! All those notes and caveats in the PostGIS boxes!
Yeah. ESRI doesn't want you to find out how good PostGIS is. It might cut
into
On Sun, Nov 3, 2013 at 10:12 PM, Paul Ramsey pram...@boundlessgeo.comwrote:
Coming back to this a bit late (hah!) ... what PostGIS version is this on?
2.0.4. Haven't tested with 2.1 yet, but I think it persists. There's a nice
script in my original report to test with if you have 2.1
On Fri, Oct 25, 2013 at 11:27 AM, Basques, Bob (CI-StPaul)
bob.basq...@ci.stpaul.mn.us wrote:
Sorry, I guess I should have looked just a little more before posting
the question . . . .
** **
http://support.esri.com/en/knowledgebase/techarticles/detail/40553
You may want to
I was looking at this page today:
http://postgis.refractions.net/docs/using_postgis_dbmanagement.html#OGC_Validity
This is a wonderfully simple explanation of what constitutes validity and
simplicity with regards to geometries. However, I noted that this page
doesn't seem to address problems
On Mon, Oct 21, 2013 at 2:32 PM, Pierre Racine
pierre.rac...@sbf.ulaval.cawrote:
Again why do ST_Union to compute the area when you could just sum() the
areas?
Won't that only yield the same answer if you can guarantee no overlapping
geometries in the fazendas table? My understanding was that
On Fri, Aug 23, 2013 at 5:30 AM, Nathaniel Clay clay.nathan...@gmail.comwrote:
I have a table of polygons that overlap with each other, I need the
polygon of the areas that only have one provider eg do not overlap. Please
find attached the shape file. Any help would be greatly appreciated!!
On Thu, Aug 29, 2013 at 3:02 PM, Burgholzer, Robert (DEQ)
robert.burghol...@deq.virginia.gov wrote:
I just noticed something interesting, perhaps its trivial and well
understood, but this is the first time I figured it out (older postgis and
postgresql to boot). I am doing a spatial
On Wed, Aug 28, 2013 at 11:25 PM, Tom C t...@tecrails.com wrote:
I have set up the Tiger geocoder for all US states and territories, but
when I try to geocode addresses in larger states like CA and TX the
processing takes quite a long time. I have run SELECT
install_missing_indexes(); and
On Wed, Aug 14, 2013 at 6:01 PM, René Fournier m...@renefournier.com wrote:
The reason is that each of the rectangles are actually subdivided into 12
smaller, equal rectangles, numbered/lettered A-L. How would you go about
doing this? It doesn't seem like something I can compute in the initial
On Tue, Aug 6, 2013 at 12:53 PM, James David Smith
james.david.sm...@gmail.com wrote:
However it says that Topology and Raster support are not present. So I
thought that I could now run the following commands to install those
too:
snip
On Tue, Aug 6, 2013 at 6:32 PM, BladeOfLight16 bladeofligh...@gmail.comwrote:
Could rtpostgis-2.0.so be a pg-routing binary? I noticed two of your
copies of GEOS are in subdirectories of /depot/shared/pgrouting/. Maybe the
routing binary is still linked to the old GEOS.
Forgive my ignorance
On Fri, Aug 2, 2013 at 5:39 PM, Paragon Corporation l...@pcorp.us wrote:
**
Try using a trigger.
http://www.postgresql.org/docs/9.1/static/sql-createtrigger.html
A foreign key won't work since it requires a btree primary key unless you
use a btree primarky key on geometry, which at best
TL;DR Version:
ST_Intersection is blowing up with errors about non-noded intersections
and no outgoing dirEdge on my polygons. A bunch of sordid details about
my data later, what can I try to make it stop throwing TopologyExceptions?
Some gory details:
The data I have comes from GPS, and it
, BladeOfLight16 wrote:
Re: JOIN selectivity
Not sure that's an option. In my real data, I'm joining to several
polygons. Many of my queries go off to different tables that have
polygons
subdividing the main polygon table. So are you basically saying that JOIN
and spatial data don't
I posted this question on StackOverflow, and the only person to answer
recommended I ask these lists for more details and link to the question:
http://stackoverflow.com/questions/16927331/postgresql-point-ops-with-gist-postgis-spatial-index
My question is:
The 9.0 release
.
** **
*From:* postgis-users-boun...@lists.osgeo.org [mailto:
postgis-users-boun...@lists.osgeo.org] *On Behalf Of *BladeOfLight16
*Sent:* Wednesday, June 05, 2013 2:29 PM
*To:* PostGIS Users Discussion; pgsql-gene...@postgresql.org
*Subject:* [postgis-users] point_ops with GiST PostGIS Spatial
27 matches
Mail list logo
