Hi Ross,
On Tue, Mar 20, 2018 at 05:59:37PM +, McDonaldR wrote:
Maybe you can point me in the right direction. I'm running PostgreSQL
9.6.8 (64bit) on Windows 2008 R2 with PostGIS 2.3.5 installed. I have
installed the 2.4.3 binaries and when I try to run ALTER EXTENSION
postgis UPDATE TO
Hi strk,
On Tue, Mar 20, 2018 at 11:08:53PM +0100, Sandro Santilli wrote:
On Tue, Mar 20, 2018 at 02:27:47PM -0400, Tom Kazimiers wrote:
This is just a random guess, but one problem I encountered on all my
Postgres setups to upgrade from PostGIS 2.3 to 2.4 is the following: There
was a single
Hi all,
I need to convert a lot of Box3D geometries to TIN geometries. Is there a way
in PostGIS to do this without specifiying each triangle and vertex for the new
TINs explicitly? Idealy, I would just be able to issue a simple update
statement without needing to think about vertex order and
order :-/
>Also tried dumping and delaunay triangulation but yet not solution.
>Anyone else?
>
>Cheers,
>Felix
>
>
>
>Gesendet: Dienstag, 17. Juli 2018 um 20:04 Uhr
>Von: "Tom Kazimiers" mailto:t...@voodoo-arts.net]>
>An: postgis-users@lists.osgeo.org[ma
Hi Darafei,
On Tue, Jul 24, 2018 at 09:31:25PM +0300, Darafei "Komяpa" Praliaskouski
wrote:
You can copy the triangulated from my message Box and ST_Translate /
ST_Scale it using ST_{X,Y,Z}{Min,Max} of your box. Of course, more
preferable way would be to use SFCGAL extension, as it's part of
P
Hi Regina,
It might not really fit the book, because it's not exactly GIS, but our
PostGIS use case is certainly an interesting one as well: As a software
engineer at the Howard Hughes Medical Institute, I work on a
collaborative neuron reconstruction and analysis software called CATMAID
[1]
Hi,
On Fri, Jan 24, 2020 at 01:50:22PM -0700, S.Bob wrote:
Can I use pg_upgrade to upgrade a cluster that has postGIS enabled
databases?
Yes, you can. But you have to make sure the *same* version of PostGIS is
available in the target database.
Cheers,
Tom
___
Hi,
I am in the process of evaluating an upgrade from Postgres 11 to 12 and
PostGIS 2.5 to 3. For one central query in my application the same plan
is executed in slightly different ways in the older PG11/PGIS2.5 setup
compared to the new one. I wonder if anyone has some insight why this
migh
Hi Regina and Paul,
On Sun, Feb 02, 2020 at 07:42:06PM -0800, Paul Ramsey wrote:
On Feb 2, 2020, at 7:37 PM, Regina Obe wrote:
If it does, can you try changing the function to your old 11 definition and see
if that makes the answers the same. Then at least we'll know it's the change
in defi
df/S0092-8674(18)30787-6.pdf
On Mon, Feb 03, 2020 at 02:46:59AM -0500, Regina Obe wrote:
It could be the change in logic of _ST_3DDWithin. That was changed to support
more 3d types, so that might have caused a slow down elsewhere.
If you can provide a dataset that would be great. I'll tr
Thanks for the report. I've ticketed as a bug -
https://trac.osgeo.org/postgis/ticket/4635
Thanks for filing the ticket Regina!
On Tue, Feb 04, 2020 at 11:49:44AM -0800, Paul Ramsey wrote:
OK, cleaning this out a little.
Ticket for reference https://trac.osgeo.org/postgis/ticket/4635#comment:
C0950341208E2041000020B511410000C0950341A0C71C4120B5114180940341'::geometry)
Planning Time: 0.833 ms
Execution Time: 148.855 ms
Also, the 12/2.5 query wants to parallelize (???) while the 12/3 one does not.
Anyways, it's super funky and not so
fits indeed better to the initial observation that PostGIS 2.5
is faster than 3.0 for this query if both &&& and ST_3DDWithin are used.
3.0 is faster if &&& is not used, but only because the 2.5 queries get
much slower.
Best,
Tom
On Thu, Mar 05, 2020 at 12:39:06AM -0500
#x27;t been able
to even replicate the behavious so far, so I am at an impasse at this
moment.
I have never worked with a sampling profiler, but I assume it varies
parameters in a query and logs the plans? Do you have a particular one
in mind? On a brief search I found pgstatprof. I suppose in my case
Hello everyone,
I use Postgres 9.4 and PostGIS 2.1 to represent about 13.000.000
vertices in a 3D space (growing). Many points are connected in tree
structures of varying size, often around 5000 nodes per tree. Therefore,
we use single edges to represent them in our table. My aim is to have
very f
Hi Sandro,
Thanks for your input!
On Wed, Jul 01, 2015 at 11:06:25AM +0200, Sandro Santilli wrote:
> On Tue, Jun 30, 2015 at 11:18:59PM -0400, Tom Kazimiers wrote:
> > Option (1) is already pretty quick, but I get some false positives (due
> > to intersecting bounding boxes of e
Hi William,
Did you run VACUUM ANALYZE on on the PG 9.4 table (after you imported
the data)? This would be required to have up-to-date statistics which
the query planner uses to e.g. decide if using an index would improve
query time.
And what is the query plan for your query (EXPLAIN ANALYZE)?
B
Hi all,
I hope this is the right place to ask, please let me know if it isn't.
PostGIS is involved in this problem, but I am unsure whether it is
actually the source of it. I hope you can help me figuring out what is
going on with a crash I encounter in a Python program running on Ubuntu
12.04.5
Hi all,
I am using Postgres 9.6 with PostGIS 2.3 and want to improve the
performance of a bounding box intersection query on a large set of
lines. I asked the same questions two month ago on
gis.stackexchange.com, but didn't get any reply. Therefore, please
excuse me for cross-posting, but I
Hi Rémi,
Thanks a lot for your thorough reply. Especially scenario A.1 has helped
me to improve performance by over an order of magnitude for our most
common use case. My reply got a bit longer, sorry, I wanted to provide a
clearer picture of my setup. For further tests I changed the system,
20 matches
Mail list logo