Bonjour,
on aurait gagné du temps avec cette info dès le début.
Ne cherchez pas plus loin l'erreur est là.
D'abord la force d'une base de donnée réside dans les indexes, sinon pas
d'accélération
Si vous avez un seul polygone, l'index ne sert à rien. Pour qu'il soit
utile il vous faudrait par
Hello,
When I write :
CREATE TABLE cadastre.p__edigeo_2012_2b_thread1_com_148_EAD0A01 (idobj
serial,ptrobj integer, refedigeo varchar(255))
it works with an implicit conversion from EAD0A01 to lower case.
When I write
CREATE TABLE cadastre.p__edigeo_2012_2b_thread1_com_149_EAD0A01 (idobj
Hi all,
Apologies for cross-posting this to the RPostrgeSQL and PostGIS mailing
lists, but I'm not sure where the problem lies.
I am using the RPostgreSQL package of R to connect to my installation of
PostgreSQL/PostGIS. I want to retrieve some coordinates from my database
and run the below
Both work fine here (9.3).
Cheers,
Rémi-C
2013/12/3 Christophe Vergon christophevergon-gir...@orange.fr
Hello,
When I write :
CREATE TABLE cadastre.p__edigeo_2012_2b_thread1_com_148_EAD0A01 (idobj
serial,ptrobj integer, refedigeo varchar(255))
it works with an implicit conversion from
Thanks,
I solve it with a temp table the p__edigeo_... was here to make the
unicity of the table for different threads.
Christophe
Rémi Cura a écrit :
Both work fine here (9.3).
Cheers,
Rémi-C
___
postgis-users mailing list
Hey all,
somebody has a trick to clean all the topology infrastructure in DB?
I mean ensuring that there is no orphan in relation, that layer
references existing tables, and so on?
Thanks,
Rémi-C
___
postgis-users mailing list
On Tue, Dec 3, 2013 at 5:23 AM, James David Smith
james.david.sm...@gmail.com wrote:
Hi all,
Apologies for cross-posting this to the RPostrgeSQL and PostGIS mailing
lists, but I'm not sure where the problem lies.
I am using the RPostgreSQL package of R to connect to my installation of
On Tue, Dec 03, 2013 at 04:50:40PM +0100, Rémi Cura wrote:
Hey all,
somebody has a trick to clean all the topology infrastructure in DB?
I mean ensuring that there is no orphan in relation, that layer
references existing tables, and so on?
Garbage collection for relation is available as a
On 3 December 2013 15:55, Lee Hachadoorian lee.hachadooria...@gmail.comwrote:
On Tue, Dec 3, 2013 at 5:23 AM, James David Smith
james.david.sm...@gmail.com wrote:
Hi all,
Apologies for cross-posting this to the RPostrgeSQL and PostGIS mailing
lists, but I'm not sure where the problem
On Tue, Dec 03, 2013 at 05:43:18PM +0100, Rémi Cura wrote:
Thanks !
Any chance you would have the garbage collection in sql ?
Sure, why not. Actually I tought I had a ticket for that but
cannot find it right now.
The trouble is that when you have a row in layer referencing nothing, you
On Tue, Dec 03, 2013 at 05:55:54PM +0100, Rémi Cura wrote:
For records :
I add to desactivate trigger on layer to delete manually rows concerning
deleted schema, then reactivate trigger, then delete from topology the
Have you tried DropTopoGeometryColumn ?
--strk;
line concerning schema,
Yep, but the table with the topogeometry column was deleted,
so no way to use classical function.
It is somehow worrisome that the system can finish in such a lock (I agree
it is not a good practice to delete all table in a schema where there is
topology).
But, you can't prevent people from
On Tue, Dec 03, 2013 at 06:19:13PM +0100, Rémi Cura wrote:
Yep, but the table with the topogeometry column was deleted,
so no way to use classical function.
We could make the DropGeometryColumn function tolerant
to the fact that the column isn't there anymore while
still having it cleanup
On Tue, Dec 3, 2013 at 11:50 AM, James David Smith
james.david.sm...@gmail.com wrote:
On 3 December 2013 15:55, Lee Hachadoorian
lee.hachadooria...@gmail.comwrote:
On Tue, Dec 3, 2013 at 5:23 AM, James David Smith
james.david.sm...@gmail.com wrote:
Hi all,
Apologies for cross-posting
That would mean
_create a function bollean table_exists(qualified_tablename)
and use it to safeguard (if exist, no change, else, skip) in all the
postgis topology functions.
Not hard, but a lot's of impacted functions.
Cheers,
Rémi-C
2013/12/3 Sandro Santilli s...@keybit.net
On Tue, Dec 03,
Hi, I believe I was unclear - the centerlines have to straight. But I'll
keep in mind your reference to delauney triangles and skeletonization for
future purposes.
To create the centerline a manual sketch is probably OK. Could I then just
move on with linear referencing? Which function should I
Hm what you seem to do is
compute a minimal bouding box (not aligned with NS or EW),
then use the greatest side as a reference, translate it so it passes by the
center of this bbox,
then several times offset the shortest side by a small step in the normal
direction, until you are out of the
If I create an nd aware index, say:
CREATE INDEX lidar_the_geom_3dx ON lidar USING gist(the_geom
gist_geometry_ops_nd);
Can - and # be made to use that? If so, how?
Thanks,
Best,
Steve
___
postgis-users mailing list
postgis-users@lists.osgeo.org
Can't, it's not implemented against nd.
P.
On Tue, Dec 3, 2013 at 12:05 PM, Stephen Mather
step...@smathermather.com wrote:
If I create an nd aware index, say:
CREATE INDEX lidar_the_geom_3dx ON lidar USING gist(the_geom
gist_geometry_ops_nd);
Can - and # be made to use that? If so, how?
Ah. Explains the output I was getting.
BTW, seems to work against an nd index, just seems to treat is as 2D (which
is an OK fallback).
Thanks!
Best,
Steve
On Tue, Dec 3, 2013 at 3:12 PM, Paul Ramsey pram...@cleverelephant.cawrote:
Can't, it's not implemented against nd.
P.
On Tue, Dec
Hi All,
Will ST_DWithin work against an nd index? I'm getting back the same number
of records, whether I use a standard 2D gist or nd, only running it with
the nd index takes 5 times as long.
Thanks,
Best,
Steve
___
postgis-users mailing list
Ahem, dumb question:tired brain.
ST_3DDWithin http://postgis.net/docs/ST_3DDWithin.html
On Tue, Dec 3, 2013 at 5:06 PM, Stephen Mather step...@smathermather.comwrote:
Hi All,
Will ST_DWithin work against an nd index? I'm getting back the same
number of records, whether I use a standard 2D
22 matches
Mail list logo
