postgis-users  

Messages by Thread

• Patch Releases 3.6.3, 3.5.6, 3.4.6, 3.3.10, 3.2.10 Paul Ramsey via postgis-users
  • Re: Patch Releases 3.6.3, 3.5.6, 3.4.6, 3.3.10, 3.2.10 Devrim Gündüz
  • Re: Patch Releases 3.6.3, 3.5.6, 3.4.6, 3.3.10, 3.2.10 Paul Ramsey via postgis-users
  • Re: Patch Releases 3.6.3, 3.5.6, 3.4.6, 3.3.10, 3.2.10 Devrim Gündüz
• ST_SNAP behaviour with 3D Geometries Alexandre Neto
• Possible Bug in postgis_restore Aussem, Robert (LGL extern) via postgis-users
  • Re: Possible Bug in postgis_restore Sandro Santilli via postgis-users
• Coordinate transformations with pipelines Antonio Valanzano
  • Re: Coordinate transformations with pipelines Florian Nadler
  • Re: Coordinate transformations with pipelines Antonio Valanzano
• PG_Restore error David Haynes
  • RE: PG_Restore error Regina Obe
  • Re: PG_Restore error David Haynes
  • Re: PG_Restore error Richard Greenwood
• PostGIS Patch releases for 3.0 - 3.6 Regina Obe
• Slowness in testing any crossing straight lines in a layer Bo Guo
  • RE: [ScanMail-Spam] Slowness in testing any crossing straight lines in a layer MONTICOLO Julien
  • Re: [ScanMail-Spam] Slowness in testing any crossing straight lines in a layer Bo Guo
  • Re: [ScanMail-Spam] Slowness in testing any crossing straight lines in a layer Paul Ramsey via postgis-users
  • RE: Slowness in testing any crossing straight lines in a layer Regina Obe
  • Re: Slowness in testing any crossing straight lines in a layer Bo Guo
  • RE: Slowness in testing any crossing straight lines in a layer Regina Obe
  • Re: Slowness in testing any crossing straight lines in a layer Bo Guo
• When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1." Michael Downey via postgis-users
  • Re: When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1." Paul Ramsey via postgis-users
  • RE: When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1." Michael Downey via postgis-users
  • Re: When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1." Paul Ramsey via postgis-users
  • RE: When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1." Michael Downey via postgis-users
• St_GeoHash: boundary handling in non-point case Sztegi
  • Re: St_GeoHash: boundary handling in non-point case Paul Ramsey via postgis-users
• Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Bharath Tadikonda
  • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Greg Troxel
  • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Paul Ramsey via postgis-users
  • RE: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Regina Obe
  • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Bharath Tadikonda
  • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Bharath Tadikonda
  • RE: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Regina Obe
  • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28) Bharath Tadikonda
• Best ways around memory Error on large st_union for overlay processing Mike Treglia
  • Re: Best ways around memory Error on large st_union for overlay processing Paul Ramsey via postgis-users
  • Re: Best ways around memory Error on large st_union for overlay processing Mike Treglia
  • Re: Best ways around memory Error on large st_union for overlay processing Paul Ramsey via postgis-users
• postgis_extensions_upgrade() issue with pg_init_privs Ari Jolma
• PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Cedric Duprez
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Paul Ramsey via postgis-users
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Cedric Duprez
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Arthur Bazin
  • RE: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Regina Obe
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Arthur Bazin
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Paul Ramsey via postgis-users
  • RE: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Regina Obe
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Cedric Duprez
  • RE: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Regina Obe
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Cedric Duprez
  • Re: PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry Paul Ramsey via postgis-users
• Re: ogr2ogr with missing geometries crashes postgresql with segmentation fault Daryl Herzmann
  • Re: ogr2ogr with missing geometries crashes postgresql with segmentation fault Paul Ramsey via postgis-users
  • Re: ogr2ogr with missing geometries crashes postgresql with segmentation fault Paul Ramsey via postgis-users
  • Re: ogr2ogr with missing geometries crashes postgresql with segmentation fault Paul Ramsey via postgis-users
  • Re: ogr2ogr with missing geometries crashes postgresql with segmentation fault Jorge Gustavo Rocha
• Problem with ST_NRings Marco Boeringa
  • Re: Problem with ST_NRings Marco Boeringa
  • Re: Problem with ST_NRings Erik Wienhold
  • Re: Problem with ST_NRings Marco Boeringa
  • RE: Problem with ST_NRings Regina Obe
  • Re: Problem with ST_NRings Marco Boeringa
  • RE: Problem with ST_NRings Regina Obe
  • Re: Problem with ST_NRings Marco Boeringa
• PostGIS Windows Bundle for PostGIS 3.6.1 for PostgreSQL 13-18 Regina Obe
• Happy PostGIS Day to all Jeff McKenna
• Re: Issue with st_estimatedextent function ?? Paul Ramsey via postgis-users
  • RE: Issue with st_estimatedextent function ?? Regina Obe
  • Re: Issue with st_estimatedextent function ?? Bo Victor Thomsen
• PostGIS Day on Thursday (Nov 20) Paul Ramsey via postgis-users
• PostGIS 3.6.1 Released Paul Ramsey via postgis-users
• PostGIS Day 2025 Paul Ramsey via postgis-users
• Question about pgSphere Antonio Siles Aguilar
  • RE: Question about pgSphere Regina Obe
• raster2pgsql ignoring nodata (seemingly) Lorenzo Curcio
• Spatial join issues Shaozhong SHI
  • Re: Spatial join issues Greg Troxel
  • Re: Spatial join issues Shaozhong SHI
  • Re: Spatial join issues Paul Ramsey via postgis-users
  • Re: Spatial join issues Paul Ramsey via postgis-users
  • Re: Spatial join issues Shaozhong SHI
  • Re: Spatial join issues Shaozhong SHI
  • Re: Spatial join issues Paul Ramsey via postgis-users
• Why PostGIS sets a max value for SRID IDs? G. Allegri
  • Re: Why PostGIS sets a max value for SRID IDs? Komяpa
  • Re: Why PostGIS sets a max value for SRID IDs? G. Allegri
  • Re: Why PostGIS sets a max value for SRID IDs? Jim Klassen
  • Re: Why PostGIS sets a max value for SRID IDs? Paul Ramsey via postgis-users
  • RE: Why PostGIS sets a max value for SRID IDs? Regina Obe
  • Re: Why PostGIS sets a max value for SRID IDs? Vincent Picavet via postgis-users
• PostGIS 3.5.4 in PGDG packages? Raine Ekman via postgis-users
  • Re: PostGIS 3.5.4 in PGDG packages? Paul Ramsey via postgis-users
  • RE: PostGIS 3.5.4 in PGDG packages? Regina Obe
• Dissolve keeping all attributes values (concatenation/aggregation)? celati Laurent
  • Re: Dissolve keeping all attributes values (concatenation/aggregation)? Erik Wienhold
  • Re: Dissolve keeping all attributes values (concatenation/aggregation)? celati Laurent
  • Re: Dissolve keeping all attributes values (concatenation/aggregation)? Erik Wienhold
  • Re: Dissolve keeping all attributes values (concatenation/aggregation)? celati Laurent
  • Re: Dissolve keeping all attributes values (concatenation/aggregation)? Erik Wienhold
• Documentation for 3.5 and 3.6 links not working Alexandre Neto
  • RE: Documentation for 3.5 and 3.6 links not working Regina Obe
• RE: PostgreSQL 18 PostGIS 3.6 installer Windows Regina Obe
• PostGIS Day 2025, Nov 20! Paul Ramsey via postgis-users
• Installing latest PostGIS on Windows Anthony DeBarros
  • RE: Installing latest PostGIS on Windows Regina Obe
• PostGIS 3.5.4 Released Paul Ramsey via postgis-users
  • Re: PostGIS 3.5.4 Released Devrim Gündüz
  • Re: PostGIS 3.5.4 Released Paragon Corporation
• different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Antonio Valanzano
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Scott
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Antonio Valanzano
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Antonio Valanzano
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Antonio Valanzano
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Antonio Valanzano
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • RE: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Regina Obe
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Paul Ramsey via postgis-users
  • Re: different results for ST_Relate with 3 parameters compared to those for ST_Relate with 2 parameters Antonio Valanzano
• Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Douglas Fan
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Greg Troxel
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Paul Ramsey via postgis-users
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Douglas Fan
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Martin Davis
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Paul Ramsey via postgis-users
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Martin Davis
  • Re: Clarification on ST_CoverageClean Parameters: snappingDistance and gapMaximumWidth Douglas Fan
• ST_Distance() query error Juho Rekilä via postgis-users
  • Re: ST_Distance() query error Paul Ramsey via postgis-users
• backend error after upgrading to 3.6.0 Ярослав Минин via postgis-users
  • Re: backend error after upgrading to 3.6.0 Erik Wienhold
  • RE: backend error after upgrading to 3.6.0 Regina Obe
  • backend error after upgrading to 3.6.0 Ярослав Минин via postgis-users
  • RE: backend error after upgrading to 3.6.0 Regina Obe
  • Re: RE: backend error after upgrading to 3.6.0 Ярослав Минин via postgis-users
  • RE: RE: backend error after upgrading to 3.6.0 Regina Obe
  • backend error after upgrading to 3.6.0 Ярослав Минин via postgis-users
  • RE: backend error after upgrading to 3.6.0 Regina Obe
  • Re: RE: backend error after upgrading to 3.6.0 Ярослав Минин via postgis-users
  • Re: backend error after upgrading to 3.6.0 Yaroslav Minin via postgis-users
• Geometry / geography woes nikolai.berkoff via postgis-users
  • Re: Geometry / geography woes Paul Ramsey via postgis-users
  • RE: Geometry / geography woes Regina Obe
  • Re: Geometry / geography woes Paul Ramsey via postgis-users
  • Re: Geometry / geography woes nikolai.berkoff via postgis-users
• PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Paul Ramsey via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Paul Ramsey via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • RE: PostGIS 3.5.2 ST_Contains() query on gist is slow Regina Obe
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Paul Ramsey via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • RE: PostGIS 3.5.2 ST_Contains() query on gist is slow Regina Obe
  • RE: PostGIS 3.5.2 ST_Contains() query on gist is slow Regina Obe
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Paul Ramsey via postgis-users
  • RE: PostGIS 3.5.2 ST_Contains() query on gist is slow Regina Obe
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • RE: PostGIS 3.5.2 ST_Contains() query on gist is slow Regina Obe
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • RE: PostGIS 3.5.2 ST_Contains() query on gist is slow Regina Obe
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Daryl Herzmann
  • Re: PostGIS 3.5.2 ST_Contains() query on gist is slow Sebastiaan Couwenberg via postgis-users
• Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Marco Boeringa
  • Re: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Greg Troxel
  • Re: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Marco Boeringa
  • Re: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Scott
  • Re: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Greg Troxel
  • RE: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Regina Obe
  • Re: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Scott
  • RE: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Regina Obe
  • Re: Wrong SFCGAL version used for compiling PostGIS 3.6.0 on Ubuntu? Scott
• Calculate the vertical distance between two lines that just intersects on 2D Jorge Gustavo Rocha
• PostGIS 3.6.0 released Regina Obe
  • PostGIS in non-standard path Scott
  • Re: PostGIS in non-standard path Greg Troxel
• [PostGIS] ST_3DIntersection query hangs (PostGIS 3.4, PostgreSQL 15.12, SFCGAL 1.5.0) rmaron via postgis-users
  • RE: [PostGIS] ST_3DIntersection query hangs (PostGIS 3.4, PostgreSQL 15.12, SFCGAL 1.5.0) Regina Obe
  • AW: [PostGIS] ST_3DIntersection query hangs (PostGIS 3.4, PostgreSQL 15.12, SFCGAL 1.5.0) rmaron via postgis-users
• Difference in behavior of AddGeometryColumn change in behavior between 3.5.2 and 3.5.3? SRID is listed as unknown when querying Geometry_Columns instead of the specified SRID Michael Downey via postgis-users
  • RE: Difference in behavior of AddGeometryColumn change in behavior between 3.5.2 and 3.5.3? SRID is listed as unknown when querying Geometry_Columns instead of the specified SRID Regina Obe
  • RE: Difference in behavior of AddGeometryColumn change in behavior between 3.5.2 and 3.5.3? SRID is listed as unknown when querying Geometry_Columns instead of the specified SRID Regina Obe
  • Re: Difference in behavior of AddGeometryColumn change in behavior between 3.5.2 and 3.5.3? SRID is listed as unknown when querying Geometry_Columns instead of the specified SRID Paul Ramsey via postgis-users
  • Re: Difference in behavior of AddGeometryColumn change in behavior between 3.5.2 and 3.5.3? SRID is listed as unknown when querying Geometry_Columns instead of the specified SRID Paul Ramsey via postgis-users
  • Re: Difference in behavior of AddGeometryColumn change in behavior between 3.5.2 and 3.5.3? SRID is listed as unknown when querying Geometry_Columns instead of the specified SRID Paul Ramsey via postgis-users
• GEOS 3.14.0 Released Paul Ramsey via postgis-users

• Earlier messages