From victoria.rautenbach at gmail.com Fri Jan 1 22:11:25 2021 From: victoria.rautenbach at gmail.com (Victoria Rautenbach) Date: Sat, 2 Jan 2021 08:11:25 +0200 Subject: [OSGeo-Announce] PROJ 7.2.1 & PROJ-data 1.4 In-Reply-To: <3E32A8F5-C720-40BA-A776-6B497FD964FC@sdfe.dk> References: <3E32A8F5-C720-40BA-A776-6B497FD964FC@sdfe.dk> Message-ID: *News item by Kristian Evers* Published at https://www.osgeo.org/foundation-news/proj-7-2-1-proj-data-1-4/ On behalf of the PROJ development team I am happy to announce the release of PROJ 7.2.1 and PROJ-data 1.4. The PROJ release includes updates to the database and a number of bug fixes. See the detailed release notes below. The PROJ-data package adds two new grid files (au_ga_AGQG_20191107.tif and eu_nkg_nkgrf2017vel.tif) that are referenced in the database updates. Get the packages here: http://download.osgeo.org/proj/proj-7.2.1.tar.gz http://download.osgeo.org/proj/proj-7.2.1.zip http://download.osgeo.org/proj/proj-data-1.4.tar.gz http://download.osgeo.org/proj/proj-data-1.4.zip /Kristian ??????????????? 7.2.1 Release Notes ------------------- Updates ------- o Add metadata with the version number of the database layout (#2474) o Split coordinateoperation.cpp and test_operation.cpp in several parts (#2484) o Update to EPSG v10.008 (#2490) o Added the NKG 2008 and 2020 transformations in proj.db (#2495) Bug fixes --------- o Set CURL_ENABLED definition on projinfo build (#2405) o createBoundCRSToWGS84IfPossible(): make it return same result with a CRS built from EPSG code or WKT1 (#2412) o WKT2 parsing: several fixes related to map projection parameter units (#2428) o createOperation(): make it work properly when one of the CRS is a BoundCRS of a DerivedGeographicCRS (+proj=ob_tran +o_proj=lonlat +towgs84=....) (#2441) o WKT parsing: fix ingestion of WKT with a Geocentric CRS as the base of the projected CRS (#2443) o GeographicCRS::_isEquivalentTo(EQUIVALENT_EXCEPT_AXIS_ORDER_GEOGCRS): make it work when comparing easting,northing,up and northing,easting,up (#2446) o createOperation(): add a ballpark vertical transformation when dealing with GEOIDMODEL[] (#2449) o Use same arguments to printf format string for both radians and degrees in output by cct (#2453) o PRIMEM WKT handling: fixes on import for 'sexagesimal DMS' or from WKT1:GDAL/ESRI when GEOGCS UNIT != Degree; morph to ESRI the PRIMEM name on export (#2455) o createObjectsFromName(): in exact match, make looking for 'ETRS89 / UTM zone 32N' return only the exact match (#2462) o Inverse tmerc spherical: fix wrong sign of latitude when lat_0 is used (#2469) o Add option to allow export of Geographic/Projected 3D CRS in WKT1_GDAL (#2470) o Fix building proj.db with SQLite built with -DSQLITE_DQS=0 (#2480) o Include JSON Schema files in CMake builds (#2485) o createOperations(): fix inconsistent chaining exception when transforming from BoundCRS of projected CRS based on NTF Paris to BoundCRS of geog CRS NTF Paris (#2486) -------------- next part -------------- An HTML attachment was scrubbed... URL: From victoria.rautenbach at gmail.com Tue Jan 26 02:14:37 2021 From: victoria.rautenbach at gmail.com (Victoria Rautenbach) Date: Tue, 26 Jan 2021 12:14:37 +0200 Subject: [OSGeo-Announce] pgRouting version 3.1.3 and version 3.0.5 release Message-ID: *News item by Ashish Kumar and the pgRouting Team* Published at https://www.osgeo.org/foundation-news/pgrouting-version-3-1-3-and-version-3-0-5-release/ Hello pgRouting community, The pgRouting Team is pleased to announce the release of pgRouting version 3.1.3 and 3.0.5. The latest release is available at [1] The fixes were backported to version 3.0.5 [2] *Note to packagers* The license changed >From GPL-2.0 to GPL-2.0-or-later *The build changed* *Cleaned the build* We made some changes to the CMakeLists to actually use cmake 3.2 and stop using the copies of some Find files we had stored *About Boost* Because of our main dependency Boost The minimum version of Boost published on the README is: 1.53 but it was not honored, We are honoring it now with a few caveats Compiling with 1.53 will not have a usable pgr_alphaShape but it will have it See #1850 [3] for details. In order to have a working pgr_alphaShape, at least Boost version 1.54 is needed with a work around where we have copied the least amount of boost files needed to make it work. In the future, starting from the 3.2.0 release of pgRouting (not scheduled yet) the minimum boost version will be 1.56 which removes the workaround, We remove the boost files Also the boost geometry requires a minimal standard of c++14 starting from Boost version 1.75 We prefer to compile our code with C++11, but the minimal requirement from boost is c++03 if the boost version >= "1.75.0" Use c++14 standard else Set to use c++11 if the compiler supports it else Set to use c++0x if the compiler supports it else Use the compiler as is. For example on MSVC pgRouting's code will be using c++0x standard which is the minimum standard for Boost <= 1.74 *Issues fixes* #1825: Boost versions are not honored #1849: Boost 1.75.0 geometry "point_xy.hpp" build error on macOS environment #1861: vrp functions crash server *To update your database:* Download the packaged version from your operating system, and use this command in the database: ALTER EXTENSION pgrouting UPDATE TO "3.1.3"; [1] https://github.com/pgRouting/pgrouting/releases/latest [2] https://github.com/pgRouting/pgrouting/releases/tag/v3.0.5 [3] https://github.com/pgRouting/pgrouting/issues/1850 -- Regards, pgRouting Team. -------------- next part -------------- An HTML attachment was scrubbed... URL: