On Wed, Feb 09, 2022 at 09:55:14AM -0600, Jim Klassen wrote:
> I always thought it
> was cumbersome that I had to maintain the custom coordinate system in
> so many places (PROJ, PostGIS, older versions of GDAL, older versions
> of QGIS) when most of them are reaching back to PROJ to do the
On 2/9/22 03:31, Sandro Santilli wrote:
Would you be disappointed/surprised by a PostGIS upgrade
replacing your custom entries above 20 with some new
"official" entry ? What strategy did you set in place to
prevent this ?
I missed the second part in my first reply.
As it stands it would
> On Feb 10, 2022, at 7:10 AM, Jim Klassen wrote:
>
> On 2/9/22 03:31, Sandro Santilli wrote:
>> Would you be disappointed/surprised by a PostGIS upgrade
>> replacing your custom entries above 20 with some new
>> "official" entry ? What strategy did you set in place to
>> prevent this ?
>
Hi Regina,
Thanks very much for this useful information. Yes, I appreciate there
may be breaking changes causing trouble.
Maybe it would be good though, to provide some basic guidance on the
PostGIS webpages regarding all of the different dependencies that
"SELECT PostGIS_Full_Version()" by
Yes. That version is telling you that PostGIS was compiled with PROJ 6.3.1.
The check is done at compile time cause we have a lot of IF DEFS to handle
various proj changes.
It’s less of an issue with GEOS since with GEOS just means you will not be
getting the newer features.
For PROJ it
I have a linear dataset on which I was building a query to find edges
that are “very close” but don’t touch. While working on this query I
found some unexpected results with the st_intersects and st_disjoint
functions. As outlined below, the query returned true for both
st_instersects and
> On Feb 10, 2022, at 4:55 PM, Emily Gouge wrote:
>
> I have a linear dataset on which I was building a query to find edges that
> are “very close” but don’t touch. While working on this query I found some
> unexpected results with the st_intersects and st_disjoint functions. As
> outlined
Here you go. Thanks!
SELECT ST_AsHEXEWKB (geometry) FROM test.eflowpath WHERE id =
'889105be-5782-43f1-b50c-5a5825c83875'
Hello,
I noticed inconsistent behavior with ST_Within across different
PostgreSQL-PostGIS versions. Most notably, the outcome (not performance) of my
query is determined by the presence of an index, which strikes me as odd. I
filed my first bug report about 3 months ago and I expect no
Hi,
I have a table with Lat Long and 3 additional values (X, Y, Z). What I want
to do is plot the points and if additional Values are set as True, then
generate a point Parallel to it or a point at an offset distance of 2.5
Meters for X, 5 meters for Y, and 7.5 Meters for Z. Here's a
10 matches
Mail list logo
