February 2024 Archives by author

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...

Starting: Thu Feb 1 11:40:20 PST 2024
Ending: Thu Feb 29 15:41:34 PST 2024
Messages: 204

• [PostGIS] #5661: Garden crash on ST_DFullyWithin   PostGIS
• [PostGIS] #5661: Garden crash on ST_DFullyWithin   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5664: Yum Update nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common   PostGIS
• [PostGIS] #5664: Yum Update nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common   PostGIS
• [PostGIS] #5664: Yum Update nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common   PostGIS
• [PostGIS] #5662: XML parser breaks for RHEL systems   PostGIS
• [PostGIS] #5662: XML parser breaks for RHEL systems   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] Batch modify: #5622, #5642, #5651, #5654, #5655, #5663, #5664   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5622: cloud.drone.io not testing github pull requests   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5666: Build reproducibility: timestamps in extension upgrade SQL scripts   PostGIS
• [PostGIS] #5666: Build reproducibility: timestamps in extension upgrade SQL scripts   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #4469: ST_ConcaveHull Runtime   PostGIS
• [PostGIS] #4469: ST_ConcaveHull Runtime   PostGIS
• [PostGIS] #5649: Since introduction of resampling on ST_Value (v3.2) behaviour on inexisting band has changed   PostGIS
• [PostGIS] #5666: Build reproducibility: timestamps in extension upgrade SQL scripts   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5664: Yum Update nothing provides libarmadillo.so.12()(64bit) needed by gdal36-libs-3.6.4-6PGDG.rhel9.x86_64 from pgdg-common   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5668: Add topology population functions taking Topology record instead of name   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5669: Batch addition of geometries in non-empty topology   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5405: Reexpose SFCGAL ST_3DIntersects and ST_3DDistance perhaps as CG_3DIntersects, CG_3DDistance, CG_3DIntersection   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #220: Implement ST_Numcurves and ST_CurveN   PostGIS
• [PostGIS] #5663: ST_GeometryN cannot access sections of CompoundCurve   PostGIS
• [PostGIS] #5361: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, and ST_Dump (was: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, and ST_Dump, add support for SQL MM ST_NumCurves and ST_CurveN)   PostGIS
• [PostGIS] #220: Implement ST_Numcurves and ST_CurveN   PostGIS
• [PostGIS] #5361: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, and ST_Dump   PostGIS
• [PostGIS] #5361: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, ST_Dump, and ST_DumpSegments (was: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, and ST_Dump)   PostGIS
• [PostGIS] #220: Implement ST_Numcurves and ST_CurveN   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5667: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #2862: PostGis Topology performance improvements : batch loading mode   PostGIS
• [PostGIS] #5669: Batch addition of geometries in non-empty topology   PostGIS
• [PostGIS] #5669: Batch addition of geometries in non-empty topology   PostGIS
• [PostGIS] #5670: Speed up ST_CreateTopoGeo by postponing face detection   PostGIS
• [PostGIS] #5361: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, ST_Dump, and ST_DumpSegments   PostGIS
• [PostGIS] #5667: Performance Postgis Topology when adding million lines by using TopoGeo_AddLineString (was: Performance Postgis Topolgy when adding millions by using TopoGeo_AddLineString)   PostGIS
• [PostGIS] #5667: Performance Postgis Topology when adding million lines by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #5670: Speed up ST_CreateTopoGeo by postponing face detection   PostGIS
• [PostGIS] #2862: PostGis Topology performance improvements : batch loading mode   PostGIS
• [PostGIS] #2862: Batch topology loading mode (was: PostGis Topology performance improvements : batch loading mode)   PostGIS
• [PostGIS] #2862: Batch topology loading mode   PostGIS
• [PostGIS] #5671: Bug in ST_Area function with use_spheroid=false   PostGIS
• [PostGIS] #5671: Bug in ST_Area function with use_spheroid=false   PostGIS
• [PostGIS] #5672: Function ST_3DIntersects does not work for MULTILINESTRING and LINESTRING.   PostGIS
• [PostGIS] #5361: Compound Curve inconsistent behavior with ST_GeometryN, ST_NumGeometries, ST_Dump, and ST_DumpSegments   PostGIS
• [PostGIS] #5673: Case studies link broken on postgis.net   PostGIS
• [PostGIS] #5674: ST_CoveredBy(geography, geography) not working for covered polygon with hole   PostGIS
• [PostGIS] #5675: WARN Module "hugo-geekdoc" is not compatible with this Hugo version   PostGIS
• [PostGIS] #5676: Missing events from the events page   PostGIS
• [PostGIS] #5673: Case studies link broken on postgis.net   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5677: ST_Union(geom[]) doesn't union single member arrays   PostGIS
• [PostGIS] #5478: ST_GeometryN should thrown an error when requesting the 0th geometry   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5681: Document transaction management for topology   PostGIS
• [PostGIS] #5681: Document transaction management for topology   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5679: sfcgal.sql:xxx: WARNING: there is no transaction in progress   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5680: populate_topology_layer does not work as documented   PostGIS
• [PostGIS] #5678: WARNING: nonstandard use of escape in a string literal   PostGIS
• [PostGIS] #2695: Topology performance improvment perspective (was: PostGis Topology performance improvment perspective)   PostGIS
• [PostGIS] #2695: Topology performance improvement perspective (was: Topology performance improvment perspective)   PostGIS
• [PostGIS] #5667: Performance Postgis Topology when adding million lines by using TopoGeo_AddLineString   PostGIS
• [PostGIS] #2862: Batch topology loading mode   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5682: Bug in geometry_columns view   PostGIS
• [PostGIS] #5682: Bug in geometry_columns view   PostGIS
• [PostGIS] #5682: Bug in geometry_columns view   PostGIS
• [PostGIS] #5682: Bug in geometry_columns view   PostGIS
• [PostGIS] #5682: Bug in geometry_columns view   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5589: ST_3DDistance seems not to work for LINESTRINGs in specified situation.   PostGIS
• [PostGIS] #5448: Test failures on i386   PostGIS
• [SCM] PostGIS branch master updated. 3.4.0rc1-911-gac4e90e9e   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-912-gfcdf1f229   git at osgeo.org
• [SCM] PostGIS branch stable-2.5 updated. 2.5.9-1-gca800d25e   git at osgeo.org
• [SCM] PostGIS branch stable-2.5 updated. 2.5.9-2-g83ac76a8b   git at osgeo.org
• [SCM] PostGIS branch stable-3.0 updated. 3.0.10-16-gdd7f67e7a   git at osgeo.org
• [SCM] PostGIS branch stable-3.0 updated. 3.0.11-1-g4be8770c7   git at osgeo.org
• [SCM] PostGIS branch stable-3.0 updated. 3.0.11-2-g66c509726   git at osgeo.org
• [SCM] PostGIS branch stable-3.1 updated. 3.1.10-19-gca03d62ca   git at osgeo.org
• [SCM] PostGIS branch stable-3.1 updated. 3.1.11-1-g8ec72f9a6   git at osgeo.org
• [SCM] PostGIS branch stable-3.2 updated. 3.2.6-22-g32dc0cc4c   git at osgeo.org
• [SCM] PostGIS branch stable-3.2 updated. 3.2.7-1-g2052b5710   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-913-g6d8aa3f75   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.1-37-ge63018427   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.5-30-gcfe89b399   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-1-g655081e7f   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.1-38-gc19ce56ca   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-1-gd739ca28b   git at osgeo.org
• [SCM] postgis.net branch website updated. clarity-final-85-g788923e   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-914-g703825535   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-923-g5560fb5cd   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-924-g595a67e52   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-2-g28d30004b   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-2-g373326f16   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-926-g799a63a81   git at osgeo.org
• [SCM] PostGIS branch stable-2.5 updated. 2.5.10-2-g0418cc0dd   git at osgeo.org
• [SCM] postgis.net branch website updated. clarity-final-86-gb3a0f07   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-927-g88b28ad0c   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-928-g22d74f7e7   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-929-g963416f2f   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-930-g8779495f9   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-933-gd47bde26b   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-934-g53b48e51d   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-935-g8ed84517a   git at osgeo.org
• [SCM] postgis.net branch recover-readme created. clarity-final-87-g44bc530   git at osgeo.org
• [SCM] postgis.net branch website updated. clarity-final-87-g44bc530   git at osgeo.org
• [SCM] postgis.net branch casestudy created. clarity-final-88-g85273f5   git at osgeo.org
• [SCM] postgis.net branch casestudy updated. clarity-final-88-g3b1fe3d   git at osgeo.org
• [SCM] postgis.net branch casestudy updated. clarity-final-88-g94ec7da   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-938-gc38c834cd   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-939-g3c79bd65b   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-943-gb3429f879   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-3-gc19da1107   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-3-g662ad692a   git at osgeo.org
• [SCM] PostGIS branch stable-3.2 updated. 3.2.7-3-gc90e28232   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-944-g15c8d95ef   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-4-gf37390b9c   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-4-gb885f39be   git at osgeo.org
• [SCM] PostGIS branch stable-3.2 updated. 3.2.7-4-gbd10d04c5   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-945-g6896fe0fe   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-946-gabf836f0a   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-947-g553258b55   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-948-g02580d807   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-5-ga22f29c3c   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-5-g29037e7e3   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-949-gf64b082ef   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-6-gc3093e575   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-6-g71afa3e0e   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-950-g5d7f02582   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-951-gea78085af   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-952-g8b3f16a62   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-953-g0fed221e6   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-954-gbccab952f   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-955-g8a41ae8f4   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-7-g1d1d8d83a   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-7-g2e3c331a3   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-956-g8f341b2a9   git at osgeo.org
• [SCM] PostGIS branch stable-3.4 updated. 3.4.2-8-g94e5b95d5   git at osgeo.org
• [SCM] PostGIS branch stable-3.3 updated. 3.3.6-8-g5c276bc0c   git at osgeo.org
• [SCM] PostGIS branch stable-3.2 updated. 3.2.7-5-g98d112ff7   git at osgeo.org
• [SCM] PostGIS branch stable-3.1 updated. 3.1.11-2-g4425662aa   git at osgeo.org
• [SCM] PostGIS branch master updated. 3.4.0rc1-957-g07a73c0f2   git at osgeo.org

Last message date: Thu Feb 29 15:41:34 PST 2024
Archived on: Thu Feb 29 15:41:35 PST 2024

• Messages sorted by: [ thread ] [ subject ] [ date ]
• More info on this list...