Damn, send too early.
Your query feels awkward, if you want the link between layer and parcel,
you should have at least 2 terms in the select.
When you precise a little bit why your query is slow, it will be possible
to propose solutions adapted.
Cheers,
Rémi-C
2015-05-27 10:19 GMT+02:00 Rémi
Hey,
the type of info you should consider to give for a meaningfull answer :
https://wiki.postgresql.org/wiki/Slow_Query_Questions
The slowness could come from many things.
For instance
layer.id = 339 AND
ST_Intersects(layer.geom_4326, parcel.geom_4326);
You use 2 conditions, postgres might
Alexander,
Using explain, make sure the where clause is used before the intersects
function.
Maybe this query will help.
SELECT DISTINCT parcel.apn
FROM
gis.parcels as parcel
JOIN (select geom_4326 from gis.layers where layer.id = 339) as layer ON
ST_Intersects(layer.geom_4326,
Hey,
Map Algebra?
(custom function with a thresholding?)
Cheers,
Rémi-C
2015-05-27 14:57 GMT+02:00 Gabriel Vatin gabriel.va...@kinaxia.fr:
Hello all,
I'd like to have some feedbacks on an operation that should be possible
with Postgis raster, but I can't find out how to do this.
I have a
Hello all,
I'd like to have some feedbacks on an operation that should be possible
with Postgis raster, but I can't find out how to do this.
I have a whole raster of French DEM (elevation data) stored on PostGis,
with tiled objects. That makes a table with some 14.000 rows of data:
france_mnt
Hello all,
I'm working on a many million lines topology project with OSM data in 4326
srid. I'd like to know if i should transform their geom in a meter srid ( like
3857). Should it be faster for the 'toTopoGeom()' function to work with
geometry in 4326 or in 3857 srid?
Thanks
Marc
Hey,
maybe you should choose whatever srid reduce the number of digits,
for the sake of precision
Cheers,
Rémi-C
2015-05-27 17:32 GMT+02:00 Marc-André Goderre magode...@cgq.qc.ca:
Hello all,
I'm working on a many million lines topology project with OSM data in 4326
srid. I'd like to know if i
Or ST_Reclass() reclassifying everything 10 to nodata...
-Original Message-
From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users-
boun...@lists.osgeo.org] On Behalf Of Rémi Cura
Sent: Wednesday, May 27, 2015 9:31 AM
To: PostGIS Users Discussion
Subject: Re:
That's the problem. I use the whole planet road data. I' can't use UTM or MTM
meter srid.
Thanks
Marc
De : postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] De la part de
steve.tout...@inspq.qc.ca
Envoyé : 27 mai 2015 12:56
À : PostGIS Users Discussion
Cc :
UTM covers the earth, could you generate the 120 zones and translate
data...
I don't know after it is usable for topology..
Marc-André Goderre magode...@cgq.qc.ca@lists.osgeo.org
Envoyé par : postgis-users-boun...@lists.osgeo.org
2015-05-27 13:00
Veuillez répondre à
PostGIS Users
If you need to translate to meter I think you should avoid 3857 if you
need precision on linear or surface measure.
It depend where on earth you are
Marc-André Goderre magode...@cgq.qc.ca@lists.osgeo.org
Envoyé par : postgis-users-boun...@lists.osgeo.org
2015-05-27 11:32
Veuillez
Since everything is wrong except for GML, which has to reverse things
that are correct in order to do the right thing vis-a-vis GML, my
guess is that the data were loaded in the wrong order to start with.
That is, if you run ST_AsText() you'll find the coordinates in Lat-Lon
order, when the
thank you ( Rémi ),
Good support. I had never known MATERIAL VIEW.
regards
On Tue, May 26, 2015 at 1:43 PM, Rémi Cura remi.c...@gmail.com wrote:
Hey,
first, about slow query question
https://wiki.postgresql.org/wiki/Slow_Query_Questions
Now you need to identify the problem.
For this,
13 matches
Mail list logo
