[postgis-tickets] [SCM] PostGIS branch stable-3.0 updated. 3.0.1-43-g9aaf78d

git at osgeo.org git at osgeo.org
Sat Aug 15 11:16:11 PDT 2020


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".

The branch, stable-3.0 has been updated
       via  9aaf78d3ff86eaf77762c85b3d71b7ab07b67cdb (commit)
      from  3fc59980780763c68ba9bc5ff71bd67a959794c3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 9aaf78d3ff86eaf77762c85b3d71b7ab07b67cdb
Author: Regina Obe <lr at pcorp.us>
Date:   Sat Aug 15 14:16:03 2020 -0400

    Prep for PostGIS 3.0.2 release, raster doc update references #4640 for PostGIS 3.0.2

diff --git a/NEWS b/NEWS
index 420ec97..f33c043 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,5 @@
 PostGIS 3.0.2
-2020/08/XX
+2020/08/15
 
 * Bug Fixes and Enhancements *
   - Remove useless duplicated call in ST_ChangeEdgeGeom (Sandro Santilli)
@@ -15,6 +15,8 @@ PostGIS 3.0.2
   - #4691, Fix segfault during gist index creation with empty geometries (Raúl Marín)
   - #4541, ST_ConcaveHull returns a "geometrycollection"
            type instead of the expected "polygon" (Regina Obe)
+  - #4640, Update raster docs to explain why ST_Transform using alignment is important.
+           Update raster FAQ (Regina Obe, Maksim Gomov)
 
 PostGIS 3.0.1
 2020/02/20
diff --git a/README.postgis b/README.postgis
index 384f374..137ffac 100644
--- a/README.postgis
+++ b/README.postgis
@@ -1,8 +1,8 @@
 PostGIS - Geographic Information Systems Extensions to PostgreSQL
 =================================================================
 
-:Version: 3.0.1
-:Date: 2020-02-20
+:Version: 3.0.2
+:Date: 2020-08-15
 :Website: https://postgis.net
 
 This distribution contains a module which implements GIS simple features, ties
diff --git a/Version.config b/Version.config
index f7dd615..dd0c26d 100644
--- a/Version.config
+++ b/Version.config
@@ -5,7 +5,7 @@
 
 POSTGIS_MAJOR_VERSION=3
 POSTGIS_MINOR_VERSION=0
-POSTGIS_MICRO_VERSION=2dev
+POSTGIS_MICRO_VERSION=2
 
 # Liblwgeom interface versioning, reset to 0:0:0 (cur:age:rev)
 # when changing POSTGIS_MINOR_VERSION
diff --git a/ci/debbie/postgis_make_dist.sh b/ci/debbie/postgis_make_dist.sh
index 7cbd323..0344b11 100644
--- a/ci/debbie/postgis_make_dist.sh
+++ b/ci/debbie/postgis_make_dist.sh
@@ -9,8 +9,8 @@ export OS_BUILD=64
 # export POSTGIS_MINOR_VERSION=2
 # export POSTGIS_MICRO_VERSION=0dev
 export PROJECTS=/var/lib/jenkins/workspace
-export GEOS_VER=3.6
-export GDAL_VER=2.2
+export GEOS_VER=3.8
+export GDAL_VER=3.0
 export WEB_DIR=/var/www/postgis_stuff
 export PATH="${PGPATH}/bin:$PATH"
 export LD_LIBRARY_PATH="${PROJECTS}/gdal/rel-${GDAL_VER}w${OS_BUILD}/lib:${PROJECTS}/geos/rel-${GEOS_VER}w${OS_BUILD}/lib:${PGPATH}/lib"
diff --git a/doc/faq_raster.xml b/doc/faq_raster.xml
index c5f24c0..bcf9221 100644
--- a/doc/faq_raster.xml
+++ b/doc/faq_raster.xml
@@ -20,9 +20,9 @@
 
       <answer>
         <para>There is a full length beginner tutorial <ulink url="http://trac.osgeo.org/postgis/wiki/WKTRasterTutorial01"> Intersecting vector buffers with large raster coverage using PostGIS Raster</ulink>.
-        Jorge has a series of blog articles on PostGIS Raster that demonstrate how to load raster data as well as cross compare to same tasks in Oracle GeoRaster. Check out
+        Jorge has a series of blog articles on PostGIS Raster that demonstrate how to load raster data as well as cross compare to same tasks in Oracle GeoRaster. Check out:
             <ulink url="http://gis4free.wordpress.com/category/postgis-raster/">Jorge's PostGIS Raster / Oracle GeoRaster Series</ulink>.
-            There is a whole chapter (more than 35 pages of content) dedicated to PostGIS Raster with free code and data downloads at <ulink url="https://www.manning.com/books/postgis-in-action-second-edition">PostGIS in Action - Raster chapter</ulink>.
+            There is a whole chapter (more than 35 pages of content) dedicated to PostGIS Raster with free code and data downloads at <ulink url="https://www.manning.com/books/postgis-in-action-third-edition">PostGIS in Action - Raster chapter. Also covered in second edition.</ulink>.
         You can <ulink url="http://www.postgis.us/page_buy_book">buy PostGIS in Action</ulink> now from Manning in hard-copy (significant discounts for bulk purchases) or just the E-book format.
         You can also buy from Amazon and various other book distributors. All hard-copy books come with a free coupon to download the E-book version.
         </para>
@@ -37,29 +37,8 @@
       </question>
 
       <answer>
-        <para>Starting with PostGIS 2.0 PostGIS Raster is fully integrated, so it will be compiled when you compile PostGIS.</para>
-	<para>Instructions for installing and running under windows are available at <ulink url="http://gis4free.wordpress.com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/">How to Install and Configure PostGIS raster on windows</ulink></para>
-        <para>
-			If you are on windows, you can compile yourself, or use the <ulink
-            url="http://postgis.net/windows_downloads">pre-compiled
-            PostGIS Raster windows binaries</ulink>.
-			If you are on Mac OSX Leopard or Snow Leopard, there are binaries available at <ulink url="http://www.kyngchaos.com/software/postgres">Kyng Chaos Mac OSX PostgreSQL/GIS binaries</ulink>.
-		</para>
-		<para>For other platforms, install PostGIS from your software repository. For more details about compiling from source, please refer to <ulink url="http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources">Installing PostGIS Raster from source</ulink></para>
-      </answer>
-    </qandaentry>
-
-	 <qandaentry>
-      <question>
-        <para>I get error could not load library "C:/Program Files/PostgreSQL/8.4/lib/rtpostgis.dll": The specified module could not be found.
-	or could not load library on Linux when trying to run rtpostgis.sql</para>
-      </question>
-
-      <answer>
-        <para>rtpostgis.so/dll is built with dependency on libgdal.dll/so. Make sure for Windows you have libgdal-1.dll in the bin folder of your PostgreSQL install.
-        For Linux libgdal has to be in your path or bin folder.  </para>
-		<para>You may also run into different errors if you don't have PostGIS installed in your database.  Make sure to install PostGIS first in your
-		database before trying to install the raster support.</para>
+        <para>PostGIS Raster is part of the PostGIS codebase and generally available with most PostGIS binary distributions.  Starting with PostGIS 3.0, PostGIS raster is now a separate extension and requires:  `CREATE EXTENSION postgis_raster;` to enable it in your database. If you are compiling your own PostGIS, you will need to compile with GDAL otherwise postgis_raster extension will not be builit.</para>
+        <para>Refer to <ulink url="http://postgis.net/install/">Download PostGIS binaries</ulink> for popular distributions of PostGIS that include raster support.</para>
       </answer>
     </qandaentry>
 
@@ -92,7 +71,8 @@
 
       <answer>
         <para>Yes</para>
-		<para>GDAL has a PostGIS raster driver, but is only compiled in if you choose to compile with PostgreSQL support. </para>
+        <para>PostGIS raster has a function <xref linkend="RT_ST_AsGDALRaster" /> that will allow you to use SQL to export to any raster format supported by your GDAL.  You can get a list of these using the <xref linkend="RT_ST_GDALDrivers" /> SQL function.</para>
+		<para>You can also use GDAL commandline tools to export PostGIS raster to other formats. GDAL has a PostGIS raster driver, but is only compiled in if you choose to compile with PostgreSQL support. </para>
 		<para>The driver currently doesn't support irregularly blocked rasters,
 		although you can store irregularly blocked rasters in PostGIS raster data type.</para>
 		<para>If you are compiling from source, you need to include in your configure
@@ -119,20 +99,19 @@
 			Below are some using a where clause</para>
 		 <programlisting>gdal_translate -of PNG -outsize 10% 10% "PG:host=localhost port=5432 dbname='mygisdb' user='postgres' password='whatever' schema='someschema' table=sometable where='filename=\'abcd.sid\''" " C:\somefile.png</programlisting>
 		 <programlisting>gdal_translate -of PNG -outsize 10% 10% "PG:host=localhost port=5432 dbname='mygisdb' user='postgres' password='whatever' schema='someschema' table=sometable where='ST_Intersects(rast, ST_SetSRID(ST_Point(-71.032,42.3793),4326) )' " C:\intersectregion.png</programlisting>
-		 <para>To see more examples and syntax refer to <ulink url="http://trac.osgeo.org/gdal/wiki/frmts_wtkraster.html#a3.2-Readingrasterdatafromthedatabase">Reading Raster Data of PostGIS Raster section</ulink></para>
+		 <para>To see more examples and syntax refer to <ulink url="https://gdal.org/drivers/raster/postgisraster.html">Reading Raster Data of PostGIS Raster section</ulink></para>
       </answer>
     </qandaentry>
 
     <qandaentry>
 	<question><para>Are their binaries of GDAL available already compiled with PostGIS Raster suppport?</para></question>
 	<answer>
-		<para>Yes. Check out the page <ulink url="http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries">GDAL Binaries</ulink> page.  Any compiled with PostgreSQL
-		support should have PostGIS Raster in them.  </para>
-		<para>PostGIS Raster is undergoing many changes.  If you want to get the latest nightly build for Windows -- then check out
+		<para>Yes. Check out the page <ulink url="https://gdal.org/download.html#binaries">GDAL Binaries</ulink> page.  Any compiled with PostgreSQL
+		support should have PostGIS Raster in them. GDAL tools is also generally included as part of <ulink url="https://qgis.org">QGIS</ulink>.</para>
+		<para>If you want to get the latest nightly build for Windows -- then check out
 		 the Tamas Szekeres  nightly builds built with Visual Studio which contain GDAL trunk, Python Bindings and MapServer executables and PostGIS Raster driver built-in.  Just
          click the SDK bat and run your commands from there.  <ulink url="www.gisinternals.com">http://www.gisinternals.com</ulink>.
 			Also available are VS project files.</para>
-			<para><ulink url="http://fwtools.maptools.org/">FWTools latest stable version for Windows is compiled with Raster support</ulink>.</para>
 	</answer>
     </qandaentry>
 
@@ -142,10 +121,10 @@
       </question>
 
       <answer>
-        <para>You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver support to view Raster data. QGIS supports viewing of PostGIS Raster if you
+        <para>You can use <ulink url="https://mapserver.org/">MapServer</ulink> compiled with GDAL to view Raster data. QGIS supports viewing of PostGIS Raster if you
         have PostGIS raster driver installed.</para>
         <para>In theory any tool that renders data using GDAL can support PostGIS raster data or
-            support it with fairly minimal effort. Again for Windows, Tamas' binaries <ulink url="www.gisinternals.com">http://www.gisinternals.com</ulink> are a good choice if you don't want the hassle of having to setup to compile your own.</para>
+            support it with fairly minimal effort. Again for Windows, Tamas' binaries (includes Mapserver) <ulink url="www.gisinternals.com">http://www.gisinternals.com</ulink> are a good choice for windows users if you don't want the hassle of having to setup to compile your own.</para>
       </answer>
     </qandaentry>
 
@@ -156,9 +135,9 @@
 
       <answer>
         <para>First you need GDAL 1.7 or higher compiled with PostGIS raster support.
-            GDAL 1.8 or above is preferred since many issues have been fixed in 1.8 and more PostGIS raster issues fixed in trunk version.</para>
+            GDAL 3 or above is preferred since many issues have been fixed in 1.8 and more PostGIS raster issues fixed in trunk version.</para>
         <para>You can much like you can with any other raster.
-        Refer to <ulink url="http://mapserver.org/input/raster.html">MapServer Raster processing options</ulink>
+        Refer to <ulink url="https://mapserver.org/input/raster.html">MapServer Raster processing options</ulink>
         for list of various processing functions you can use with MapServer raster layers.</para>
         <para>What makes PostGIS raster data particularly interesting, is that since
 	each tile can have various standard database columns, you can segment it in your data source</para>
diff --git a/doc/html/image_src/Makefile.in b/doc/html/image_src/Makefile.in
index 7c53bd7..34840d9 100644
--- a/doc/html/image_src/Makefile.in
+++ b/doc/html/image_src/Makefile.in
@@ -149,7 +149,9 @@ IMAGES= \
 	../images/st_voronoi01.png \
 	../images/st_voronoi02.png \
 	../images/st_voronoi03.png \
-	../images/st_within01.png
+	../images/st_within01.png \
+	../images/rt_st_transform01.png \
+	../images/rt_st_transform02.png
 
 # Images that are created with dimensions 100x100
 IMAGES_RESIZED= \
diff --git a/doc/html/image_src/rt_st_transform01.wkt b/doc/html/image_src/rt_st_transform01.wkt
new file mode 100644
index 0000000..20c5e79
--- /dev/null
+++ b/doc/html/image_src/rt_st_transform01.wkt
@@ -0,0 +1,9 @@
+Style2;POLYGON((0.971135534320737 100.198164698777,0.973586221467386 100.198164698777,0.973586221467386 100.195714011631,0.971135534320737 100.195714011631,0.971135534320737 100.198164698777))
+Style2;POLYGON((0.973933293135374 100.198324208518,0.976383950436883 100.198324208518,0.976383950436883 100.195873551217,0.973933293135374 100.195873551217,0.973933293135374 100.198324208518))
+Style2;POLYGON((0.976731068363691 100.198483654947,0.979181695816038 100.198483654947,0.979181695816038 100.196033027495,0.976731068363691 100.196033027495,0.976731068363691 100.198483654947))
+Style2;POLYGON((0.971395384296088 100.196373137183,0.973845994625563 100.196373137183,0.973845994625563 100.193922526854,0.971395384296088 100.193922526854,0.971395384296088 100.196373137183))
+Style2;POLYGON((0.974193041210469 100.196532639711,0.976643621699466 100.196532639711,0.976643621699466 100.194082059222,0.974193041210469 100.194082059222,0.974193041210469 100.196532639711))
+Style2;POLYGON((0.976990714536086 100.196692078929,0.979441265180583 100.196692078929,0.979441265180583 100.194241528284,0.976990714536086 100.194241528284,0.976990714536086 100.196692078929))
+Style2;POLYGON((0.971655209404048 100.194581576034,0.97410574292519 100.194581576034,0.97410574292519 100.192131042513,0.971655209404048 100.192131042513,0.971655209404048 100.194581576034))
+Style2;POLYGON((0.97445276442771 100.194741071348,0.976903268113048 100.194741071348,0.976903268113048 100.192290567663,0.97445276442771 100.192290567663,0.97445276442771 100.194741071348))
+Style2;POLYGON((0.977250335860205 100.194900503356,0.979700809705705 100.194900503356,0.979700809705705 100.192450029511,0.977250335860205 100.192450029511,0.977250335860205 100.194900503356))
diff --git a/doc/html/image_src/rt_st_transform02.wkt b/doc/html/image_src/rt_st_transform02.wkt
new file mode 100644
index 0000000..45c8463
--- /dev/null
+++ b/doc/html/image_src/rt_st_transform02.wkt
@@ -0,0 +1,9 @@
+Style2;POLYGON((0.971135534320737 100.198164698777,0.973586221467386 100.198164698777,0.973586221467386 100.195714011631,0.971135534320737 100.195714011631,0.971135534320737 100.198164698777))
+Style2;POLYGON((0.973586221467386 100.199390042351,0.977262252187373 100.199390042351,0.977262252187373 100.195714011631,0.973586221467386 100.195714011631,0.973586221467386 100.199390042351))
+Style2;POLYGON((0.976036908614049 100.199390042351,0.979712939334036 100.199390042351,0.979712939334036 100.195714011631,0.976036908614049 100.195714011631,0.976036908614049 100.199390042351))
+Style2;POLYGON((0.971135534320737 100.196939355204,0.974811565040724 100.196939355204,0.974811565040724 100.193263324484,0.971135534320737 100.193263324484,0.971135534320737 100.196939355204))
+Style2;POLYGON((0.973586221467386 100.196939355204,0.977262252187373 100.196939355204,0.977262252187373 100.193263324484,0.973586221467386 100.193263324484,0.973586221467386 100.196939355204))
+Style2;POLYGON((0.976036908614049 100.196939355204,0.979712939334036 100.196939355204,0.979712939334036 100.193263324484,0.976036908614049 100.193263324484,0.976036908614049 100.196939355204))
+Style2;POLYGON((0.971135534320737 100.195714011631,0.974811565040724 100.195714011631,0.974811565040724 100.192037980911,0.971135534320737 100.192037980911,0.971135534320737 100.195714011631))
+Style2;POLYGON((0.973586221467386 100.195714011631,0.977262252187373 100.195714011631,0.977262252187373 100.192037980911,0.973586221467386 100.192037980911,0.973586221467386 100.195714011631))
+Style2;POLYGON((0.976036908614049 100.195714011631,0.979712939334036 100.195714011631,0.979712939334036 100.192037980911,0.976036908614049 100.192037980911,0.976036908614049 100.195714011631))
diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml
index 58b461f..0a3c962 100644
--- a/doc/reference_raster.xml
+++ b/doc/reference_raster.xml
@@ -6990,6 +6990,12 @@ SELECT rid, (meta).* FROM bar
 					</para>
 				</note>
 
+				<warning>
+					<para>
+						When transforming a coverage of tiles, you almost always want to use a reference raster to insure same alignment as demonstrated in example: Variant 3.
+					</para>
+				</warning>
+
 				<para>Availability: 2.0.0  Requires GDAL 1.6.1+</para>
 				<para>Enhanced: 2.1.0 Addition of ST_Transform(rast, alignto) variant</para>
 			</refsection>
@@ -7089,6 +7095,33 @@ FROM baz
 ------+-------------+---------
  t    | f           | t
 				</programlisting>
+				<informaltable>
+				  <tgroup cols="2">
+					<tbody>
+					  <row>
+						<entry><para><informalfigure>
+							<mediaobject>
+							  <imageobject>
+								<imagedata fileref="images/rt_st_transform01.png" />
+							  </imageobject>
+							  <caption><para>not_aligned</para></caption>
+							</mediaobject>
+						  </informalfigure>
+						  </para></entry>
+
+						<entry><para><informalfigure>
+							<mediaobject>
+							  <imageobject>
+								<imagedata fileref="images/rt_st_transform02.png" />
+							  </imageobject>
+							  <caption><para>aligned</para></caption>
+							</mediaobject>
+						  </informalfigure>
+						</para></entry>
+					  </row>
+						</tbody>
+						</tgroup>
+					</informaltable>
 			</refsection>
 
 			<refsection>
diff --git a/doc/release_notes.xml b/doc/release_notes.xml
index 3575840..5416ec2 100644
--- a/doc/release_notes.xml
+++ b/doc/release_notes.xml
@@ -4,6 +4,31 @@
     <subtitle>Release Notes</subtitle>
 
     <sect1>
+        <title>Release 3.0.2</title>
+        <para>Release date: 2020/08/15</para>
+        <para>This is a bug fix / performance enhancements release. This version requires PostgreSQL 9.5+-12 and GEOS >= 3.6+
+              Additional features and enhancements enabled if you are running Proj6+, PostgreSQL 12, and GEOS 3.8</para>
+      <simplesect>
+        <title>Bug Fixes and Enhancements</title>
+          <para>Remove useless duplicated call in ST_ChangeEdgeGeom (Sandro Santilli)</para>
+          <para>4709, Fix crash in adding edge to corrupted topology, (Sandro Santilli)</para>
+          <para>- Handle non-closed edge rings by human readable error (Sandro Santilli)</para>
+          <para>4706, Fix crash in ST_ChangeEdgeGeom on corrupted topology (Sandro Santilli)</para>
+          <para>4652, Fix several memory related bugs in ST_GeomFromGML (Raúl Marín)</para>
+          <para>4661,4129, Fix access to spatial_ref_sys with a non default schema (Raúl Marín)</para>
+          <para>4670, ST_AddPoint: Fix bug when a positive position is requested (Raúl Marín)</para>
+          <para>4702, Legacy ST_Locate_Between_Measures is wrong (Kaplas80)</para>
+          <para>4699, crash on null input to ST_Union(raster, otherarg) (Jaime Casanova, 2ndQuadrant)</para>
+          <para>4716, Fix several issues with pkg-config in the configure script (Raúl Marín)</para>
+          <para>4691, Fix segfault during gist index creation with empty geometries (Raúl Marín)</para>
+          <para>4541, ST_ConcaveHull returns a "geometrycollection"
+                    type instead of the expected "polygon" (Regina Obe)</para>
+          <para>4640, Update raster docs to explain why ST_Transform using alignment is important.
+                    Update raster FAQ (Regina Obe, Maksim Gomov)</para>
+        </simplesect>
+    </sect1>
+
+    <sect1>
       <title>PostGIS 3.0.1</title>
       <para>Release date: 2020/02/20</para>
 

-----------------------------------------------------------------------

Summary of changes:
 NEWS                                     |  4 ++-
 README.postgis                           |  4 +--
 Version.config                           |  2 +-
 ci/debbie/postgis_make_dist.sh           |  4 +--
 doc/faq_raster.xml                       | 49 +++++++++-----------------------
 doc/html/image_src/Makefile.in           |  4 ++-
 doc/html/image_src/rt_st_transform01.wkt |  9 ++++++
 doc/html/image_src/rt_st_transform02.wkt |  9 ++++++
 doc/reference_raster.xml                 | 33 +++++++++++++++++++++
 doc/release_notes.xml                    | 25 ++++++++++++++++
 10 files changed, 101 insertions(+), 42 deletions(-)
 create mode 100644 doc/html/image_src/rt_st_transform01.wkt
 create mode 100644 doc/html/image_src/rt_st_transform02.wkt


hooks/post-receive
-- 
PostGIS


More information about the postgis-tickets mailing list