Am 21.12.2022 um 16:43 schrieb Regina Obe:
Hi Regina,
> 1) Make sure you do have a gist index on latlng
This was my error...
I created an Index just doing:
CREATE INDEX idx_elevation_latlng ON elevation (latlng);
Now I recreated the index with:
CREATE INDEX idx_elevation_latlng ON elevation
> Hi all!
>
> I have a table "elevation", defined as:
>
> gis=# \d+ elevation
>Table "public.elevation"
> Column | Type | Collation | Nullable | Default | Storage
> | Stats target | Description
>
> On Tue, Dec 20, 2022 at 12:02:03PM -0500, Regina Obe wrote:
>
> > Sandro and Paul, is there any way we can expose the compiled version of
> GEOS and Proj?
>
> I don't think there's a speicific function but some functions do include
the
> compiled-in version in the error message, like
Hello Regina,
thanks to your information I could find a workaround. I ended up
removing the postgresql and ubuntugis-unstable repositories along with
the installed software and installed docker to use the alpine-based
docker files (https://registry.hub.docker.com/r/postgis/postgis/). The
On Tue, Dec 20, 2022 at 12:02:03PM -0500, Regina Obe wrote:
> Sandro and Paul, is there any way we can expose the compiled version of GEOS
> and Proj?
I don't think there's a speicific function but some functions
do include the compiled-in version in the error message, like
ST_FrechetDistance
Sorry for not replying sooner but only now I could test it.
Can confirm that the topology that was having errors (with around 10k
linestrings) now finishes without any errors.
Thanks for your help.
De: postgis-users em nome de Sandro
Santilli
Enviado: 3
Hi all!
I have a table "elevation", defined as:
gis=# \d+ elevation
Table "public.elevation"
Column | Type | Collation | Nullable | Default | Storage
| Stats target | Description
