From lr at pcorp.us Fri Jun 2 09:05:23 2023 From: lr at pcorp.us (Regina Obe) Date: Fri, 2 Jun 2023 12:05:23 -0400 Subject: [postgis-users] PostGIS 3.3.3 Bundle for Windows released (PG 11-15) Message-ID: <003c01d9956c$0a5b4320$1f11c960$@pcorp.us> PostGIS 3.3.3 Bundle for Windows is now available on application stackbuilder and OSGeo website. Details of what's included are listed on: https://postgis.net/documentation/getting_started/install_windows/released_v ersions/ New in this release is addition of a new extension MobilityDB (1.1.0, develop version) for tracking objects in motion. It also includes various useful spatial types and functions to do so. This new extension is only available for PostgreSQL 12-15 (not 11) bundles. https://mobilitydb.com For mobilitydb usage issues, report on the https://github.com/MobilityDB/MobilityDB/issues tracker. If you run into other issues, report on the PostGIS tracker - https://trac.osgeo.org/postgis with under milestone "PostGIS Packaging" and keywords "windows" Thanks, Regina From garg at zeemaps.com Fri Jun 2 09:48:07 2023 From: garg at zeemaps.com (Pankaj K Garg) Date: Fri, 02 Jun 2023 09:48:07 -0700 Subject: [postgis-users] Problem compiling postgis Message-ID: <1887d025f88.b3577e01679318.8836781606438881254@zeemaps.com> I cannot compile Postgis 3.3.3 (or 3.2.3) on Mac OS Ventura 13.4. I installed abseil?using brew. Abseil mandates the use of at least C++14. PostGIS is trying the build flatgeobuf with C++11. Will appreciate any help or pointers. Thanks. Pankaj ---- Making all in postgis /Applications/Xcode.app/Contents/Developer/usr/bin/make -C ../deps/flatgeobuf all gcc -std=c++11 -x c++ -I../../liblwgeom -I../../liblwgeom -I./include? -I/usr/local/Cellar/geos/3.11.2/include -I/usr/local/Cellar/proj/9.2.0_1/include -I/usr/local/Cellar/libtiff/4.5.0/include -I/usr/local/Cellar/zstd/1.5.5/include -I/usr/local/Cellar/jpeg-turbo/2.1.5.1/include? -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include? -I/usr/local/Cellar/json-c/0.16/include -I/usr/local/Cellar/json-c/0.16/include/json-c -I/usr/local/Cellar/pcre2/10.42/include -DNDEBUG? ? -fno-common -DPIC -c -o flatgeobuf_c.o flatgeobuf_c.cpp In file included from flatgeobuf_c.cpp:26: In file included from ./feature_generated.h:7: In file included from ./include/flatbuffers/flatbuffers.h:22: In file included from ./include/flatbuffers/array.h:20: In file included from ./include/flatbuffers/base.h:237: In file included from /usr/local/include/absl/strings/string_view.h:39: In file included from /usr/local/include/absl/base/attributes.h:37: In file included from /usr/local/include/absl/base/config.h:86: /usr/local/include/absl/base/policy_checks.h:79:2: error: "C++ versions less than C++14 are not supported." #error "C++ versions less than C++14 are not supported." ?^ 1 error generated. make[2]: *** [flatgeobuf_c.o] Error 1 make[1]: *** [../deps/flatgeobuf/libflatgeobuf.la] Error 2 make: *** [all] Error 1 9:42 postgis-3.3.3 %? ZeeMaps ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?http://www.zeemaps.com 21060 Homestead Road, Suite 150 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? support at zeemaps.com Cupertino, CA 95014 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?408 914-2955 Like us on Facebook:?http://www.facebook.com/zeemaps? ? ? ? ? ? ? ?Follow us on Twitter:?http://twitter.com/zeemaps -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Fri Jun 2 12:47:23 2023 From: lr at pcorp.us (Regina Obe) Date: Fri, 2 Jun 2023 15:47:23 -0400 Subject: [postgis-users] [postgis-devel] Problem compiling postgis In-Reply-To: <606BE51C-3D2C-4790-AC8B-EBBA421D0DA1@cleverelephant.ca> References: <1887d025f88.b3577e01679318.8836781606438881254@zeemaps.com> <4C8B238F-660A-4710-A299-340F985033D8@cleverelephant.ca> <21822437-466a-b516-612d-f5d114a23e4d@spatialys.com> <000f01d99584$ec5a68b0$c50f3a10$@pcorp.us> <606BE51C-3D2C-4790-AC8B-EBBA421D0DA1@cleverelephant.ca> Message-ID: <001e01d9958b$0da83320$28f89960$@pcorp.us> I think Bjorn was concerned it was too big of an update to push into a stable release, Though I guess if it's preventing people from building, maybe we need to or at least a partial update. I'm not sure we should bother with 3.2 though as it seems to be an issue that is affecting newer OS and such people probably won't be bothering with PostGIS 3.2. Added back the users list and Pankaj. Thanks, Regina > -----Original Message----- > From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf > Of Paul Ramsey > Sent: Friday, June 2, 2023 3:05 PM > To: PostGIS Development Discussion > Cc: Bj?rn Harrtell > Subject: Re: [postgis-devel] [postgis-users] Problem compiling postgis > > Ah, that explains failures in 3.2/3.3? seems like a back port is also required. > > P > > > On Jun 2, 2023, at 12:03 PM, Regina Obe wrote: > > > > I think he pushed the latest flatgeobuf in 3.4.0 > > > > Is it this one - https://github.com/postgis/postgis/pull/726 > > > > > > https://trac.osgeo.org/postgis/ticket/5368 > > > > > > > >> -----Original Message----- > >> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On > >> Behalf Of Paul Ramsey > >> Sent: Friday, June 2, 2023 2:54 PM > >> To: Even Rouault ; Bj?rn Harrtell > >> > >> Cc: PostGIS Development Discussion > >> Subject: Re: [postgis-devel] [postgis-users] Problem compiling > >> postgis > >> > >> Am I reading this right, we have flatgeobuf vendored in? Bjorn could > >> you update our copy to what you think it a good state? > >> > >> On Fri, Jun 2, 2023 at 10:07?AM Even Rouault > >> > >> wrote: > >>> > >>> cf MapServer fix for similar issue: > >>> https://github.com/MapServer/MapServer/pull/6833 (the issue was > >>> fixed in upstream flatbuffers) > >>> > >>> Le 02/06/2023 ? 19:00, Paul Ramsey a ?crit : > >>> > >>> Wait, we now have an implicit abseil dependency from flatgeobuf? > >>> > >>> > >>> On Jun 2, 2023, at 9:48 AM, Pankaj K Garg wrote: > >>> > >>> I cannot compile Postgis 3.3.3 (or 3.2.3) on Mac OS Ventura 13.4. > >>> > >>> I installed abseil using brew. Abseil mandates the use of at least C++14. > >> PostGIS is trying the build flatgeobuf with C++11. > >>> > >>> Will appreciate any help or pointers. > >>> > >>> Thanks. > >>> > >>> Pankaj > >>> > >>> > >>> ---- Making all in postgis > >>> /Applications/Xcode.app/Contents/Developer/usr/bin/make -C > >> ../deps/flatgeobuf all > >>> gcc -std=c++11 -x c++ -I../../liblwgeom -I../../liblwgeom > >>> -I./include - > >> I/usr/local/Cellar/geos/3.11.2/include > >> -I/usr/local/Cellar/proj/9.2.0_1/include > >> -I/usr/local/Cellar/libtiff/4.5.0/include > >> -I/usr/local/Cellar/zstd/1.5.5/include - > >> I/usr/local/Cellar/jpeg-turbo/2.1.5.1/include - > >> > I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform > >> / Developer/SDKs/MacOSX.sdk/usr/include -I/usr/local/Cellar/json- > >> c/0.16/include -I/usr/local/Cellar/json-c/0.16/include/json-c - > >> I/usr/local/Cellar/pcre2/10.42/include -DNDEBUG -fno-common -DPIC -c > -o > >> flatgeobuf_c.o flatgeobuf_c.cpp > >>> In file included from flatgeobuf_c.cpp:26: > >>> In file included from ./feature_generated.h:7: > >>> In file included from ./include/flatbuffers/flatbuffers.h:22: > >>> In file included from ./include/flatbuffers/array.h:20: > >>> In file included from ./include/flatbuffers/base.h:237: > >>> In file included from /usr/local/include/absl/strings/string_view.h:39: > >>> In file included from /usr/local/include/absl/base/attributes.h:37: > >>> In file included from /usr/local/include/absl/base/config.h:86: > >>> /usr/local/include/absl/base/policy_checks.h:79:2: error: "C++ > >>> versions less > >> than C++14 are not supported." > >>> #error "C++ versions less than C++14 are not supported." > >>> ^ > >>> 1 error generated. > >>> make[2]: *** [flatgeobuf_c.o] Error 1 > >>> make[1]: *** [../deps/flatgeobuf/libflatgeobuf.la] Error 2 > >>> make: *** [all] Error 1 > >>> 9:42 postgis-3.3.3 % > >>> > >>> ________________________________ > >>> > >>> ZeeMaps > >> http://www.zeemaps.com > >>> 21060 Homestead Road, Suite 150 > >> support at zeemaps.com > >>> Cupertino, CA 95014 > >> 408 914-2955 > >>> Like us on Facebook: http://www.facebook.com/zeemaps Follow > us > >> on Twitter: http://twitter.com/zeemaps > >>> > >>> > >>> _______________________________________________ > >>> postgis-users mailing list > >>> postgis-users at lists.osgeo.org > >>> https://lists.osgeo.org/mailman/listinfo/postgis-users > >>> > >>> > >>> > >>> _______________________________________________ > >>> postgis-devel mailing list > >>> postgis-devel at lists.osgeo.org > >>> https://lists.osgeo.org/mailman/listinfo/postgis-devel > >>> > >>> -- > >>> http://www.spatialys.com > >>> My software is free, but my time generally not. > >> _______________________________________________ > >> postgis-devel mailing list > >> postgis-devel at lists.osgeo.org > >> https://lists.osgeo.org/mailman/listinfo/postgis-devel > > > > _______________________________________________ > > postgis-devel mailing list > > postgis-devel at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/postgis-devel > > _______________________________________________ > postgis-devel mailing list > postgis-devel at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/postgis-devel From pramsey at cleverelephant.ca Fri Jun 2 12:50:10 2023 From: pramsey at cleverelephant.ca (Paul Ramsey) Date: Fri, 2 Jun 2023 12:50:10 -0700 Subject: [postgis-users] [postgis-devel] Problem compiling postgis In-Reply-To: <001e01d9958b$0da83320$28f89960$@pcorp.us> References: <1887d025f88.b3577e01679318.8836781606438881254@zeemaps.com> <4C8B238F-660A-4710-A299-340F985033D8@cleverelephant.ca> <21822437-466a-b516-612d-f5d114a23e4d@spatialys.com> <000f01d99584$ec5a68b0$c50f3a10$@pcorp.us> <606BE51C-3D2C-4790-AC8B-EBBA421D0DA1@cleverelephant.ca> <001e01d9958b$0da83320$28f89960$@pcorp.us> Message-ID: > On Jun 2, 2023, at 12:47 PM, Regina Obe wrote: > > I think Bjorn was concerned it was too big of an update to push into a stable release, > Though I guess if it's preventing people from building, maybe we need to or at least a partial update. > I'm not sure we should bother with 3.2 though as it seems to be an issue that is affecting newer OS and such people probably won't be bothering with PostGIS 3.2. Well, it is affecting people doing their own builds. Homebrew bumping their copy of abseil up in combination with this means everyone on home-brew is going to bang into this if they are building something more than 2 years old? presumably this will end up affecting all kinds of environments that run with a latest-and-greatest policy, as they pull in newer abseil. P. > > Added back the users list and Pankaj. > > Thanks, > Regina > > >> -----Original Message----- >> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf >> Of Paul Ramsey >> Sent: Friday, June 2, 2023 3:05 PM >> To: PostGIS Development Discussion >> Cc: Bj?rn Harrtell >> Subject: Re: [postgis-devel] [postgis-users] Problem compiling postgis >> >> Ah, that explains failures in 3.2/3.3? seems like a back port is also required. >> >> P >> >>> On Jun 2, 2023, at 12:03 PM, Regina Obe wrote: >>> >>> I think he pushed the latest flatgeobuf in 3.4.0 >>> >>> Is it this one - https://github.com/postgis/postgis/pull/726 >>> >>> >>> https://trac.osgeo.org/postgis/ticket/5368 >>> >>> >>> >>>> -----Original Message----- >>>> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On >>>> Behalf Of Paul Ramsey >>>> Sent: Friday, June 2, 2023 2:54 PM >>>> To: Even Rouault ; Bj?rn Harrtell >>>> >>>> Cc: PostGIS Development Discussion >>>> Subject: Re: [postgis-devel] [postgis-users] Problem compiling >>>> postgis >>>> >>>> Am I reading this right, we have flatgeobuf vendored in? Bjorn could >>>> you update our copy to what you think it a good state? >>>> >>>> On Fri, Jun 2, 2023 at 10:07?AM Even Rouault >>>> >>>> wrote: >>>>> >>>>> cf MapServer fix for similar issue: >>>>> https://github.com/MapServer/MapServer/pull/6833 (the issue was >>>>> fixed in upstream flatbuffers) >>>>> >>>>> Le 02/06/2023 ? 19:00, Paul Ramsey a ?crit : >>>>> >>>>> Wait, we now have an implicit abseil dependency from flatgeobuf? >>>>> >>>>> >>>>> On Jun 2, 2023, at 9:48 AM, Pankaj K Garg wrote: >>>>> >>>>> I cannot compile Postgis 3.3.3 (or 3.2.3) on Mac OS Ventura 13.4. >>>>> >>>>> I installed abseil using brew. Abseil mandates the use of at least C++14. >>>> PostGIS is trying the build flatgeobuf with C++11. >>>>> >>>>> Will appreciate any help or pointers. >>>>> >>>>> Thanks. >>>>> >>>>> Pankaj >>>>> >>>>> >>>>> ---- Making all in postgis >>>>> /Applications/Xcode.app/Contents/Developer/usr/bin/make -C >>>> ../deps/flatgeobuf all >>>>> gcc -std=c++11 -x c++ -I../../liblwgeom -I../../liblwgeom >>>>> -I./include - >>>> I/usr/local/Cellar/geos/3.11.2/include >>>> -I/usr/local/Cellar/proj/9.2.0_1/include >>>> -I/usr/local/Cellar/libtiff/4.5.0/include >>>> -I/usr/local/Cellar/zstd/1.5.5/include - >>>> I/usr/local/Cellar/jpeg-turbo/2.1.5.1/include - >>>> >> I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform >>>> / Developer/SDKs/MacOSX.sdk/usr/include -I/usr/local/Cellar/json- >>>> c/0.16/include -I/usr/local/Cellar/json-c/0.16/include/json-c - >>>> I/usr/local/Cellar/pcre2/10.42/include -DNDEBUG -fno-common -DPIC -c >> -o >>>> flatgeobuf_c.o flatgeobuf_c.cpp >>>>> In file included from flatgeobuf_c.cpp:26: >>>>> In file included from ./feature_generated.h:7: >>>>> In file included from ./include/flatbuffers/flatbuffers.h:22: >>>>> In file included from ./include/flatbuffers/array.h:20: >>>>> In file included from ./include/flatbuffers/base.h:237: >>>>> In file included from /usr/local/include/absl/strings/string_view.h:39: >>>>> In file included from /usr/local/include/absl/base/attributes.h:37: >>>>> In file included from /usr/local/include/absl/base/config.h:86: >>>>> /usr/local/include/absl/base/policy_checks.h:79:2: error: "C++ >>>>> versions less >>>> than C++14 are not supported." >>>>> #error "C++ versions less than C++14 are not supported." >>>>> ^ >>>>> 1 error generated. >>>>> make[2]: *** [flatgeobuf_c.o] Error 1 >>>>> make[1]: *** [../deps/flatgeobuf/libflatgeobuf.la] Error 2 >>>>> make: *** [all] Error 1 >>>>> 9:42 postgis-3.3.3 % >>>>> >>>>> ________________________________ >>>>> >>>>> ZeeMaps >>>> http://www.zeemaps.com >>>>> 21060 Homestead Road, Suite 150 >>>> support at zeemaps.com >>>>> Cupertino, CA 95014 >>>> 408 914-2955 >>>>> Like us on Facebook: http://www.facebook.com/zeemaps Follow >> us >>>> on Twitter: http://twitter.com/zeemaps >>>>> >>>>> >>>>> _______________________________________________ >>>>> postgis-users mailing list >>>>> postgis-users at lists.osgeo.org >>>>> https://lists.osgeo.org/mailman/listinfo/postgis-users >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> postgis-devel mailing list >>>>> postgis-devel at lists.osgeo.org >>>>> https://lists.osgeo.org/mailman/listinfo/postgis-devel >>>>> >>>>> -- >>>>> http://www.spatialys.com >>>>> My software is free, but my time generally not. >>>> _______________________________________________ >>>> postgis-devel mailing list >>>> postgis-devel at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/postgis-devel >>> >>> _______________________________________________ >>> postgis-devel mailing list >>> postgis-devel at lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/postgis-devel >> >> _______________________________________________ >> postgis-devel mailing list >> postgis-devel at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/postgis-devel > > _______________________________________________ > postgis-users mailing list > postgis-users at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/postgis-users From mail at johannes-froelich.de Mon Jun 12 01:07:36 2023 From: mail at johannes-froelich.de (=?utf-8?Q?Johannes_Fr=C3=B6lich?=) Date: Mon, 12 Jun 2023 10:07:36 +0200 Subject: [postgis-users] get points from pgis db with "resolution"? Message-ID: Hi, i am not sure if i am right here, but i have a question: i have points in a pgis db in a regular grid shape with lets say resolution 1m, 1000m x1000m, so 1.000.000 points. is there any way to recieve query these points in a certain area with a "resolution" - so like only return points within 2m to get a 2m resolution, and return only 500.000 points? i need something like that to then generate Terrain models with different LODs. Thanks a lot! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lars.Opsahl at nibio.no Tue Jun 13 20:33:44 2023 From: Lars.Opsahl at nibio.no (Lars Aksel Opsahl) Date: Wed, 14 Jun 2023 03:33:44 +0000 Subject: [postgis-users] Postgis Simple Feature silently giving us wrong results Message-ID: Hi In Postgis we now have problems where we silently get wrong result from ST_Difference. This bug was only found because a tester did inspect the result manually by actually checking the maps generated on the screen. In this case, we have a fixed restricted area (blue), where users can select an area to use that are not already used by another user (red area), so we need to remove the area taken. The result the user saw is here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/pictures/difference_test_01_POSTGIS_3_3_3.png (output from ST_Difference, the green rectangles). The ST_Difference test and data used can be found here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/sql/regress/rog_sf_difference.sql . If we use Postgis Topology we get a result that seems to be correct. https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/pictures/topo_difference_test_01_POSTGIS_3_3_3.png . The Postgis Topology test is here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/sql/regress/rog_topology_difference.sql . We use the same input data and run on the same Postgis version (POSTGIS="3.3.3 2355e8e") and server for this tests. (If a I use latest source compiled by Sandro a couple weeks ago on a server locally, this test case works, but then another test case fails). We have reported errors like before so the path that Simple Feature seems to be heading now is where it silently generate very wrong results and then silently corrupts your spatial database, is very problematic for us. It would be much better for us if we got with a Topology exception that could tell us what and where the problem was and then can decide what to do. Is that possible today? The default behavior of Postgis Simple Feature (not only ST_Difference) today makes it problematic for NIBIO to use it in systems where users can apply for subsidies related to areas of land for instance. It?s also difficult to find new errors, because they are silently hidden and when doing billions of operation, manual inspection is out off range. We can maybe start to make tests to check if any the selected from from ST_Difference intersects with area already used, but I have no idea if that will find all problems. Another problem is producing spatial change logs because with Postgis bugs like this, you get new changes just because of a new Postgis version and not because data have changed. It would have been better throwing an error in cases like this and then user can decide if he wants to report this as error maybe modify the input data, I think, actually one of the reasons why NIBIO started use Postgis was that others system did cover up operations like Postgis are doing now. Another option is to use Postgis Topology and the way that Sandro is doing it here seem much better related to data corruption, because here we get an error if the system are not able to handle a new input line. In Postgis Topology we also have methods (https://postgis.net/docs/ValidateTopology.html ) that can check the database consistency. NIBIO will have both a workshop and talk at Foss4g 2023 in Prizren. Here we will talk about Postgis Topology related used cases https://gitlab.com/nibioopensource/topology_update_app and https://gitlab.com/nibioopensource/resolve-overlap-and-gap. Thanks. Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Tue Jun 13 21:43:20 2023 From: lr at pcorp.us (Regina Obe) Date: Wed, 14 Jun 2023 00:43:20 -0400 Subject: [postgis-users] Postgis Simple Feature silently giving us wrong results In-Reply-To: References: Message-ID: <001901d99e7a$bede78f0$3c9b6ad0$@pcorp.us> I haven't looked thru your examples, but it would be good to know which version of GEOS you are running since ST_Difference ultimately depends on GEOS. What does: SELECT postgis_full_version(), version(); Return on your system? Thanks, Regina From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf Of Lars Aksel Opsahl Sent: Tuesday, June 13, 2023 11:34 PM To: 'PostGIS Users Discussion' Subject: [postgis-users] Postgis Simple Feature silently giving us wrong results Hi In Postgis we now have problems where we silently get wrong result from ST_Difference. This bug was only found because a tester did inspect the result manually by actually checking the maps generated on the screen. In this case, we have a fixed restricted area (blue), where users can select an area to use that are not already used by another user (red area), so we need to remove the area taken. The result the user saw is here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/sr c/test/pictures/difference_test_01_POSTGIS_3_3_3.png (output from ST_Difference, the green rectangles). The ST_Difference test and data used can be found here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/sr c/test/sql/regress/rog_sf_difference.sql . If we use Postgis Topology we get a result that seems to be correct. https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/sr c/test/pictures/topo_difference_test_01_POSTGIS_3_3_3.png . The Postgis Topology test is here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/sr c/test/sql/regress/rog_topology_difference.sql . We use the same input data and run on the same Postgis version (POSTGIS="3.3.3 2355e8e") and server for this tests. (If a I use latest source compiled by Sandro a couple weeks ago on a server locally, this test case works, but then another test case fails). We have reported errors like before so the path that Simple Feature seems to be heading now is where it silently generate very wrong results and then silently corrupts your spatial database, is very problematic for us. It would be much better for us if we got with a Topology exception that could tell us what and where the problem was and then can decide what to do. Is that possible today? The default behavior of Postgis Simple Feature (not only ST_Difference) today makes it problematic for NIBIO to use it in systems where users can apply for subsidies related to areas of land for instance. It's also difficult to find new errors, because they are silently hidden and when doing billions of operation, manual inspection is out off range. We can maybe start to make tests to check if any the selected from from ST_Difference intersects with area already used, but I have no idea if that will find all problems. Another problem is producing spatial change logs because with Postgis bugs like this, you get new changes just because of a new Postgis version and not because data have changed. It would have been better throwing an error in cases like this and then user can decide if he wants to report this as error maybe modify the input data, I think, actually one of the reasons why NIBIO started use Postgis was that others system did cover up operations like Postgis are doing now. Another option is to use Postgis Topology and the way that Sandro is doing it here seem much better related to data corruption, because here we get an error if the system are not able to handle a new input line. In Postgis Topology we also have methods (https://postgis.net/docs/ValidateTopology.html ) that can check the database consistency. NIBIO will have both a workshop and talk at Foss4g 2023 in Prizren. Here we will talk about Postgis Topology related used cases https://gitlab.com/nibioopensource/topology_update_app and https://gitlab.com/nibioopensource/resolve-overlap-and-gap. Thanks. Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lars.Opsahl at nibio.no Tue Jun 13 21:59:30 2023 From: Lars.Opsahl at nibio.no (Lars Aksel Opsahl) Date: Wed, 14 Jun 2023 04:59:30 +0000 Subject: [postgis-users] Postgis Simple Feature silently giving us wrong results In-Reply-To: <001901d99e7a$bede78f0$3c9b6ad0$@pcorp.us> References: <001901d99e7a$bede78f0$3c9b6ad0$@pcorp.us> Message-ID: Hi Sure On my local mac I have this postgis_full_version | POSTGIS="3.2.3 2f97b6c" [EXTENSION] PGSQL="140" GEOS="3.11.0-CAPI-1.17.0" PROJ="9.0.1" LIBXML="2.9.14" LIBJSON="0.16" LIBPROTOBUF="1.4.1" WAGYU="0.5.0 (Internal)" TOPOLOGY version | PostgreSQL 14.5 on x86_64-apple-darwin21.5.0, compiled by Apple clang version 13.1.6 (clang-1316.0.21.2.5), 64-bit In test environment where we first did see the problem postgis_full_version | POSTGIS="3.2.0 c3e3cc0" [EXTENSION] PGSQL="120" GEOS="3.10.1-CAPI-1.16.0" SFCGAL="1.3.7" PROJ="8.2.0" GDAL="GDAL 3.4.0, released 2021/11/04" LIBXML="2.9.10" LIBJSON="0.13.1" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" TOPOLOGY RASTERversion | PostgreSQL 12.12 (Ubuntu 12.12-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit In our CI system POSTGIS="3.3.3 2355e8e" [EXTENSION] PGSQL="120" GEOS="3.10.2-CAPI-1.16.0" PROJ="8.2.1" LIBXML="2.9.13" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" TOPOLOGY --ON Postgresql 12, 13 and 14 There are more details here around the results and what's tested here also in https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/sql/regress/rog_sf_difference.sql Thanks. Lars ________________________________ From: postgis-users on behalf of Regina Obe Sent: Wednesday, June 14, 2023 6:43 AM To: 'PostGIS Users Discussion' Subject: Re: [postgis-users] Postgis Simple Feature silently giving us wrong results I haven?t looked thru your examples, but it would be good to know which version of GEOS you are running since ST_Difference ultimately depends on GEOS. What does: SELECT postgis_full_version(), version(); Return on your system? Thanks, Regina From: postgis-users [mailto:postgis-users-bounces at lists.osgeo.org] On Behalf Of Lars Aksel Opsahl Sent: Tuesday, June 13, 2023 11:34 PM To: 'PostGIS Users Discussion' Subject: [postgis-users] Postgis Simple Feature silently giving us wrong results Hi In Postgis we now have problems where we silently get wrong result from ST_Difference. This bug was only found because a tester did inspect the result manually by actually checking the maps generated on the screen. In this case, we have a fixed restricted area (blue), where users can select an area to use that are not already used by another user (red area), so we need to remove the area taken. The result the user saw is here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/pictures/difference_test_01_POSTGIS_3_3_3.png (output from ST_Difference, the green rectangles). The ST_Difference test and data used can be found here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/sql/regress/rog_sf_difference.sql . If we use Postgis Topology we get a result that seems to be correct. https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/pictures/topo_difference_test_01_POSTGIS_3_3_3.png . The Postgis Topology test is here https://gitlab.com/nibioopensource/resolve-overlap-and-gap/-/blob/develop/src/test/sql/regress/rog_topology_difference.sql . We use the same input data and run on the same Postgis version (POSTGIS="3.3.3 2355e8e") and server for this tests. (If a I use latest source compiled by Sandro a couple weeks ago on a server locally, this test case works, but then another test case fails). We have reported errors like before so the path that Simple Feature seems to be heading now is where it silently generate very wrong results and then silently corrupts your spatial database, is very problematic for us. It would be much better for us if we got with a Topology exception that could tell us what and where the problem was and then can decide what to do. Is that possible today? The default behavior of Postgis Simple Feature (not only ST_Difference) today makes it problematic for NIBIO to use it in systems where users can apply for subsidies related to areas of land for instance. It?s also difficult to find new errors, because they are silently hidden and when doing billions of operation, manual inspection is out off range. We can maybe start to make tests to check if any the selected from from ST_Difference intersects with area already used, but I have no idea if that will find all problems. Another problem is producing spatial change logs because with Postgis bugs like this, you get new changes just because of a new Postgis version and not because data have changed. It would have been better throwing an error in cases like this and then user can decide if he wants to report this as error maybe modify the input data, I think, actually one of the reasons why NIBIO started use Postgis was that others system did cover up operations like Postgis are doing now. Another option is to use Postgis Topology and the way that Sandro is doing it here seem much better related to data corruption, because here we get an error if the system are not able to handle a new input line. In Postgis Topology we also have methods (https://postgis.net/docs/ValidateTopology.html ) that can check the database consistency. NIBIO will have both a workshop and talk at Foss4g 2023 in Prizren. Here we will talk about Postgis Topology related used cases https://gitlab.com/nibioopensource/topology_update_app and https://gitlab.com/nibioopensource/resolve-overlap-and-gap. Thanks. Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at markus-raab.org Thu Jun 29 07:47:55 2023 From: mailinglists at markus-raab.org (Markus Raab) Date: Thu, 29 Jun 2023 16:47:55 +0200 Subject: [postgis-users] Searching for Paid Developers Message-ID: <6b2c99be-360c-f78d-dad2-75600153c856@markus-raab.org> Dear PostGIS users, we started developing a free/libre and open-source permaculture designer tool for maps with focus on plants, see https://www.permaplant.net/ While we have lots of expertise in programming and biology, we are still lacking experience in GIS, which is not essential but would be useful for some use cases. We are applying for funding from netidee.at and (if accepted) search for someone who implements some of our use cases in PostGIS (paid, ~30?/h). Would be great to hear from you before 3rd of July. You can write us via kontakt at permaplant.net or also reply here. We also speak German. Best regards, Markus Raab & Yvonne Markl