[postgis-users] How to just get the last in a recursive query

In this example, Network Walking in PostGIS · Paul Ramsey (cleverelephant.ca) 3 rows got returns as follows: id --- 6 3 1 How to just get the last (namely, 1) in the most efficient way? Regards, David

Re: [postgis-users] ST_Transform weirdness in 3.1.5

I also cannot reproduce the Infinities in the first query on my installs with proj 7.2.1 (on amd64 and aarch64). To answer why transformations with SRID and proj4txt give different results: I believe the SRID based transformation goes through all the proj.db magic to select the best

Re: [postgis-users] ST_Transform weirdness in 3.1.5

Yeah, at a first approximation, the obvious reason for the problem is "with an EPSG code, proj can try and do a smart datum conversion via grids, whereas with only a proj string, proj is stuck doing a naive bursa-wolf transformation, hence your problem". However, that would still leave open

Re: [postgis-users] ST_Transform weirdness in 3.1.5

Thanks at least for looking into this. One other thing I just noticed: If I transform from EPSG:4269 -> EPSG:4326 first, it seems to work as expected. select st_asewkt(st_transform('SRID=4326;POLYGON((-81.11425169432798 25.139365690162226,-79.88375846050846 25.97,-79.8759485474324

Re: [postgis-users] ST_Transform weirdness in 3.1.5

Not super obvious as I'm not seeing a reproduction here on a more recent proj. Anyone with proj6 able to reproduce? P > On Apr 4, 2022, at 9:18 AM, Jeff Hoffmann wrote: > > I am running PostgreSQL via Amazon RDS. Here is the version > information for the instance that exhibits the problem: >

[postgis-users] ST_Transform weirdness in 3.1.5

I am running PostgreSQL via Amazon RDS. Here is the version information for the instance that exhibits the problem: version - PostgreSQL

[postgis-users] Fwd: Trigger Function Only for Updated Row.

Hello, Currently my trigger executes on ALL the rows in the table. I would like it to execute ONLY on the UPDATED row. My thinking is that it is inefficient to check all rows in a large table every time a single field is updated. My main reason for wanting to do this is for efficient processing.