[postgis-tickets] [SCM] postgis.net branch website updated. 5a13fc9897d5b242492d2f48392c4cd1e75a5646
git at osgeo.org
git at osgeo.org
Sun Apr 24 09:38:46 PDT 2022
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.net".
The branch, website has been updated
via 5a13fc9897d5b242492d2f48392c4cd1e75a5646 (commit)
from ad017466108cd3df5452da1364367394ed8a0a0f (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 5a13fc9897d5b242492d2f48392c4cd1e75a5646
Author: Regina Obe <lr at pcorp.us>
Date: Sun Apr 24 12:38:38 2022 -0400
Change all page-break to more tags, so huguo correctly creates the summary
diff --git a/content/events/11-21_postgis-day-panel.md b/content/events/11-21_postgis-day-panel.md
index 842868f..0411d60 100644
--- a/content/events/11-21_postgis-day-panel.md
+++ b/content/events/11-21_postgis-day-panel.md
@@ -17,7 +17,7 @@ November 21st, 2013 was PostGIS day and to celebrate we had a four panel discuss
<a href="https://www.youtube.com/watch?feature=player_embedded&v=xzl6gaOsasE" target="_blank">Video here</a>
-<!-- pagebreak -->
+<!--more-->
**A very PostGIS Day Video**
diff --git a/content/post/2012/06-22_postgis-2-0-1.md b/content/post/2012/06-22_postgis-2-0-1.md
index 2f87b18..830e32b 100644
--- a/content/post/2012/06-22_postgis-2-0-1.md
+++ b/content/post/2012/06-22_postgis-2-0-1.md
@@ -12,7 +12,7 @@ The 2.0.1 release of PostGIS is [now available][1].
This is a bug fix release, addressing issues that have been filed since the 2.0.0 release.
-<!-- pagebreak -->
+<!--more-->
**Bug Fixes**
diff --git a/content/post/2012/07-20_postgis-1-5-5.md b/content/post/2012/07-20_postgis-1-5-5.md
index 52e8c38..c68f95d 100644
--- a/content/post/2012/07-20_postgis-1-5-5.md
+++ b/content/post/2012/07-20_postgis-1-5-5.md
@@ -12,7 +12,7 @@ The 1.5.5 release of PostGIS is [now available][1].
This is a bug fix release, addressing issues that have been filed since the 1.5.4, most importantly a crash bug for geography indexes on tables with many NULL values in them.
-<!-- pagebreak -->
+<!--more-->
**Bug Fixes**
diff --git a/content/post/2012/10-17_infoterra/index.md b/content/post/2012/10-17_infoterra/index.md
index c76122a..d941e08 100644
--- a/content/post/2012/10-17_infoterra/index.md
+++ b/content/post/2012/10-17_infoterra/index.md
@@ -10,7 +10,7 @@ thumbnail: infoterra.jpg
Infoterra has been in the geospatial business for over 25 years, since its founding in 1980 as the UK National Remote Sensing Centre. In that time, NRSC grew, formed international partnerships with space agencies, expanded into aerial data collection, and was eventually privatized and re-named "Infoterra" in the late 1990s.
-<!-- pagebreak -->
+<!--more-->
<img class="left" src="infoterra_logo_sm.jpg" />
As a major re-seller of remote sensing and aerial photography in the UK and Europe, Infoterra has had to manage larger and larger collections of data for customers. With the rise of the internet, Infoterra has moved more of its data catalogues online, and customers have gotten used to having direct access to information about data holdings.
diff --git a/content/post/2012/10-18_ign/index.md b/content/post/2012/10-18_ign/index.md
index 0f45b32..bca3af0 100644
--- a/content/post/2012/10-18_ign/index.md
+++ b/content/post/2012/10-18_ign/index.md
@@ -12,7 +12,7 @@ The [Institut Géographique National](http://ign.fr/) (IGN) is the national mapp
France, with 1800 employees and a mandate to collect, integrate, manage and
distribute reference geographical information for the whole country.
-<!-- pagebreak -->
+<!--more-->
<img class='right' src='ign.png' />
For many years, IGN has managed the national spatial data using the [GeoConcept](http://www.geoconcept.com/)
diff --git a/content/post/2012/10-30_postgis-1-5-6.md b/content/post/2012/10-30_postgis-1-5-6.md
index 725913f..72d42d1 100644
--- a/content/post/2012/10-30_postgis-1-5-6.md
+++ b/content/post/2012/10-30_postgis-1-5-6.md
@@ -21,7 +21,7 @@ This is a bug fix release, addressing issues that have been filed since the 1.5.
* #1976, Geography point-in-ring code overhauled for more reliability
* #2071, Add PgSQL 9.2 support
-<!-- pagebreak -->
+<!--more-->
View all [closed tickets][2].
diff --git a/content/post/2012/10-31_postgis-1-5-7.md b/content/post/2012/10-31_postgis-1-5-7.md
index eaeac44..cfe0179 100644
--- a/content/post/2012/10-31_postgis-1-5-7.md
+++ b/content/post/2012/10-31_postgis-1-5-7.md
@@ -16,7 +16,7 @@ This is a bug fix release, addressing issues that have been filed since the 1.5.
* #2071, Add PgSQL 9.2 support updates to 1.5.6
-<!-- pagebreak -->
+<!--more-->
View all [closed tickets][2].
diff --git a/content/post/2012/11-15_postgis-1-5-8.md b/content/post/2012/11-15_postgis-1-5-8.md
index d20336c..84dc91e 100644
--- a/content/post/2012/11-15_postgis-1-5-8.md
+++ b/content/post/2012/11-15_postgis-1-5-8.md
@@ -18,7 +18,7 @@ This is a bug fix release, addressing issues that have been filed since the 1.5.
* #2048, `ST_Within` and `ST_CoveredBy` producing bad results
* #2095, proj4 cache corrupted by projection error
-<!-- pagebreak -->
+<!--more-->
[source download]({{< loc "postgis.release_source">}}/postgis-1.5.8.tar.gz)
diff --git a/content/post/2012/12-03_postgis-2-0-2.md b/content/post/2012/12-03_postgis-2-0-2.md
index 72be6b3..d3fb5bd 100644
--- a/content/post/2012/12-03_postgis-2-0-2.md
+++ b/content/post/2012/12-03_postgis-2-0-2.md
@@ -12,7 +12,7 @@ The 2.0.2 release of PostGIS is [now available]({{< loc "postgis.release_source"
The PostGIS development team is happy to release the second patch version of PostGIS 2, the 2.0.2 release. As befits a patch release, the focus is on bugs and breakages, and there are a large number of obscure things that are now better in this release.
-<!-- pagebreak -->
+<!--more-->
<{{< loc "postgis.release_source">}}/postgis-2.0.2.tar.gz>
diff --git a/content/post/2013/03-01_postgis-2-0-3.md b/content/post/2013/03-01_postgis-2-0-3.md
index 9747dba..f507de3 100644
--- a/content/post/2013/03-01_postgis-2-0-3.md
+++ b/content/post/2013/03-01_postgis-2-0-3.md
@@ -16,7 +16,7 @@ Best served with a bottle of GEOS 3.3.8.
<{{< loc "postgis.release_source">}}/postgis-2.0.3.tar.gz>
-<!-- pagebreak -->
+<!--more-->
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.0.3.tar.gz)
diff --git a/content/post/2013/05-11_postgis-2-1-0beta2.md b/content/post/2013/05-11_postgis-2-1-0beta2.md
index a96ddf4..f2e740e 100644
--- a/content/post/2013/05-11_postgis-2-1-0beta2.md
+++ b/content/post/2013/05-11_postgis-2-1-0beta2.md
@@ -24,7 +24,7 @@ Users of 1.5 and below will need to go the hard-upgrade path.
Best served with a bottle of GEOS 3.4.0dev and PostgreSQL 9.3beta1. (which will also be released soon)
-<!-- pagebreak -->
+<!--more-->
<{{< loc "postgis.release_source">}}/postgis-2.1.0beta2.tar.gz>
diff --git a/content/post/2013/06-22_postgis-2-1-0beta3.md b/content/post/2013/06-22_postgis-2-1-0beta3.md
index 42e4531..f7536aa 100644
--- a/content/post/2013/06-22_postgis-2-1-0beta3.md
+++ b/content/post/2013/06-22_postgis-2-1-0beta3.md
@@ -24,7 +24,7 @@ Users of 1.5 and below will need to go the hard-upgrade path.
Best served with a bottle of GEOS 3.4.0dev and PostgreSQL 9.3beta2. (which will also be released soon)
-<!-- pagebreak -->
+<!--more-->
<{{< loc "postgis.release_source">}}/postgis-2.1.0beta3.tar.gz>
diff --git a/content/post/2013/07-10_postgis-2-1-0rc1.md b/content/post/2013/07-10_postgis-2-1-0rc1.md
index 8cd3944..c11a610 100644
--- a/content/post/2013/07-10_postgis-2-1-0rc1.md
+++ b/content/post/2013/07-10_postgis-2-1-0rc1.md
@@ -31,7 +31,7 @@ Users of 1.5 and below will need to go the hard-upgrade path.
Best served with a bottle of GEOS 3.4.0dev and PostgreSQL 9.3beta2.
-<!-- pagebreak -->
+<!--more-->
<{{< loc "postgis.release_source">}}/postgis-2.1.0rc1.tar.gz>
diff --git a/content/post/2013/08-03_postgis-2-1-0rc2.md b/content/post/2013/08-03_postgis-2-1-0rc2.md
index 57a9669..62b209e 100644
--- a/content/post/2013/08-03_postgis-2-1-0rc2.md
+++ b/content/post/2013/08-03_postgis-2-1-0rc2.md
@@ -34,7 +34,7 @@ Users of 1.5 and below will need to go the hard-upgrade path.
Best served with a bottle of GEOS 3.4.0 (planned release Aug 11th) and PostgreSQL 9.3beta2.
-<!-- pagebreak -->
+<!--more-->
<{{< loc "postgis.release_source">}}/postgis-2.1.0rc2.tar.gz>
diff --git a/content/post/2013/08-17_postgis-2-1-0.md b/content/post/2013/08-17_postgis-2-1-0.md
index 599a948..b65cdf6 100644
--- a/content/post/2013/08-17_postgis-2-1-0.md
+++ b/content/post/2013/08-17_postgis-2-1-0.md
@@ -35,7 +35,7 @@ Best served with a bottle of GEOS 3.4.1 and
PostgreSQL 9.3beta2 (planned release September).
-<!-- pagebreak -->
+<!--more-->
<{{< loc "postgis.release_source">}}/postgis-2.1.0.tar.gz>
diff --git a/content/post/2013/08-18_tip_lon_lat.md b/content/post/2013/08-18_tip_lon_lat.md
index 0ac01e4..357f628 100644
--- a/content/post/2013/08-18_tip_lon_lat.md
+++ b/content/post/2013/08-18_tip_lon_lat.md
@@ -13,7 +13,7 @@ spatial coordinates are in x = longitude, and y = latitude.
If you accidentally loaded data as lat,lon, you can always fix the mistake
by using the <a href="/docs/manual-dev/ST_FlipCoordinates.html" target="_blank">```ST_FlipCoordinates```</a> function introduced in PostGIS 2.0.
-<!-- pagebreak -->
+<!--more-->
An example use for geometry:
```postgres
ALTER TABLE sometable
diff --git a/content/post/2013/08-26_tip_ST_DWithin.md b/content/post/2013/08-26_tip_ST_DWithin.md
index 2ae2339..55c59f5 100644
--- a/content/post/2013/08-26_tip_ST_DWithin.md
+++ b/content/post/2013/08-26_tip_ST_DWithin.md
@@ -19,7 +19,7 @@ Use <a href="/docs/manual-dev/ST_DWithin.html" target="_blank">```ST_DWithin```<
Also note that ```ST_DWithin``` is supported for both geometry and geography.
-<!-- pagebreak -->
+<!--more-->
**Examples**
diff --git a/content/post/2013/08-30_tip_ST_Set_or_Transform.md b/content/post/2013/08-30_tip_ST_Set_or_Transform.md
index a5f4c7c..bf06292 100644
--- a/content/post/2013/08-30_tip_ST_Set_or_Transform.md
+++ b/content/post/2013/08-30_tip_ST_Set_or_Transform.md
@@ -20,7 +20,7 @@ from a known spatial reference system to another known spatial reference system.
In PostGIS 2+ it's pretty easy to correct mistakes you've made with standard ALTER TABLE commands. We'll demonstrate a couple of scenarios
-<!-- pagebreak -->
+<!--more-->
**Examples**
diff --git a/content/post/2013/09-06_postgis-2-0-4.md b/content/post/2013/09-06_postgis-2-0-4.md
index 1a43a0d..c2c73d5 100644
--- a/content/post/2013/09-06_postgis-2-0-4.md
+++ b/content/post/2013/09-06_postgis-2-0-4.md
@@ -19,7 +19,7 @@ Best served with a bottle of GEOS 3.3.9.
Doc downloads:
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.0.4.tar.gz) [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.0.4.pdf)
-<!-- pagebreak -->
+<!--more-->
**Bug Fixes**
diff --git a/content/post/2013/10-05_tip_pgAdmin_shows_no_data.md b/content/post/2013/10-05_tip_pgAdmin_shows_no_data.md
index a43c85d..d4c3968 100644
--- a/content/post/2013/10-05_tip_pgAdmin_shows_no_data.md
+++ b/content/post/2013/10-05_tip_pgAdmin_shows_no_data.md
@@ -18,7 +18,7 @@ Since this question gets asked so much, I thought it best to highlight it again.
Spatial objects can be big things and if your geometry, geography, or raster row field is big enough, pgAdmin is not going to load it
and will just show an empty field. This is by design. There are a couple of ways to verify you really have data and even how big your geometry, geography or raster column is
-<!-- pagebreak -->
+<!--more-->
**Examples**
diff --git a/content/post/2013/11-08_postgis-2.1.1.md b/content/post/2013/11-08_postgis-2.1.1.md
index ab05742..e6f4d37 100644
--- a/content/post/2013/11-08_postgis-2.1.1.md
+++ b/content/post/2013/11-08_postgis-2.1.1.md
@@ -16,7 +16,7 @@ Best served with a bottle of GEOS 3.4.2.
<{{< loc "postgis.release_source">}}/postgis-2.1.1.tar.gz>
-<!-- pagebreak -->
+<!--more-->
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.1.1.tar.gz)
diff --git a/content/post/2014/03-14_tip_intersection_faster.md b/content/post/2014/03-14_tip_intersection_faster.md
index 131c90b..b8bf3a0 100644
--- a/content/post/2014/03-14_tip_intersection_faster.md
+++ b/content/post/2014/03-14_tip_intersection_faster.md
@@ -21,7 +21,7 @@ without actually computing an intersection. In these cases, you can skip the co
This kind of question comes up a lot: As discussed in stackexchange <a href="http://gis.stackexchange.com/questions/31310/acquiring-arcgis-like-speed-in-postgis/31562" target="_blank">Acquiring ArcGIS speed in PostGIS</a>
-<!-- pagebreak -->
+<!--more-->
**Examples**
diff --git a/content/post/2014/03-31_postgis-2-0-5.md b/content/post/2014/03-31_postgis-2-0-5.md
index 3d3a247..715ea9c 100644
--- a/content/post/2014/03-31_postgis-2-0-5.md
+++ b/content/post/2014/03-31_postgis-2-0-5.md
@@ -19,7 +19,7 @@ Best served with a bottle of GEOS 3.3.9.
Doc downloads:
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.0.5.tar.gz) [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.0.5.pdf)
-<!-- pagebreak -->
+<!--more-->
**Important Change**
diff --git a/content/post/2014/03-31_postgis-2.1.2.md b/content/post/2014/03-31_postgis-2.1.2.md
index 592dff8..119aeea 100644
--- a/content/post/2014/03-31_postgis-2.1.2.md
+++ b/content/post/2014/03-31_postgis-2.1.2.md
@@ -16,7 +16,7 @@ Best served with a bottle of GEOS 3.4.2.
<{{< loc "postgis.release_source">}}/postgis-2.1.2.tar.gz>
-<!-- pagebreak -->
+<!--more-->
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.1.2.tar.gz)
[pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.1.2.pdf)
diff --git a/content/post/2014/05-19_postgis-2.0.6_and_2.1.3.md b/content/post/2014/05-19_postgis-2.0.6_and_2.1.3.md
index e65bc96..5059320 100644
--- a/content/post/2014/05-19_postgis-2.0.6_and_2.1.3.md
+++ b/content/post/2014/05-19_postgis-2.0.6_and_2.1.3.md
@@ -13,7 +13,7 @@ may give more privileges to users than an administrator is
willing to grant. These include reading files from the filesystem
and opening connections to network hosts.
-<!-- pagebreak -->
+<!--more-->
Both issues can be limited in existing installations by setting
the GDAL_SKIP variable (in the PostgreSQL server environment)
diff --git a/content/post/2014/09-10_postgis-2.1.4.md b/content/post/2014/09-10_postgis-2.1.4.md
index e9e67b6..9bfd008 100644
--- a/content/post/2014/09-10_postgis-2.1.4.md
+++ b/content/post/2014/09-10_postgis-2.1.4.md
@@ -13,7 +13,7 @@ The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.
<{{< loc "postgis.release_source">}}/postgis-2.1.4.tar.gz>
-<!-- pagebreak -->
+<!--more-->
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.1.4.tar.gz)
[pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.1.4.pdf)
diff --git a/content/post/2014/09-26_tip_count_of_pixel_values.md b/content/post/2014/09-26_tip_count_of_pixel_values.md
index cb923fb..4bf6bd6 100644
--- a/content/post/2014/09-26_tip_count_of_pixel_values.md
+++ b/content/post/2014/09-26_tip_count_of_pixel_values.md
@@ -17,7 +17,7 @@ The temptation is to reach for <a href="/docs/manual-dev/RT_ST_Value.html" targe
This tip was prompted by the question on stackexchange <a href="http://gis.stackexchange.com/questions/115161/how-can-i-extract-all-distinct-values-from-a-postgis-raster/115245" target="_blank">How can I extract all distinct values from a PostGIS Raster?</a>
-<!-- pagebreak -->
+<!--more-->
**Examples**
diff --git a/content/post/2014/12-18_postgis-2.1.5.md b/content/post/2014/12-18_postgis-2.1.5.md
index 8f6b7fd..d2648a2 100644
--- a/content/post/2014/12-18_postgis-2.1.5.md
+++ b/content/post/2014/12-18_postgis-2.1.5.md
@@ -13,7 +13,7 @@ The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.
<{{< loc "postgis.release_source">}}/postgis-2.1.5.tar.gz>
-<!-- pagebreak -->
+<!--more-->
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.1.5.tar.gz)
[pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.1.5.pdf)
diff --git a/content/post/2015/03-20_postgis-2.1.6.md b/content/post/2015/03-20_postgis-2.1.6.md
index 9c4fe8f..7b1391d 100644
--- a/content/post/2015/03-20_postgis-2.1.6.md
+++ b/content/post/2015/03-20_postgis-2.1.6.md
@@ -14,7 +14,7 @@ The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.
* [Download 2.1.6]({{< loc "postgis.release_source">}}/postgis-2.1.6.tar.gz)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.1.6/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
[html doc download]({{< loc "postgis.release_docs">}}/doc-html-2.1.6.tar.gz)
[pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.1.6.pdf)
diff --git a/content/post/2015/05-02_tip_enable_raster_drivers.md b/content/post/2015/05-02_tip_enable_raster_drivers.md
index e16b345..fd62659 100644
--- a/content/post/2015/05-02_tip_enable_raster_drivers.md
+++ b/content/post/2015/05-02_tip_enable_raster_drivers.md
@@ -21,7 +21,7 @@ SELECT ST_AsPNG(rast)
Gives error: Warning: pg_query(): Query failed: ERROR: rt\_raster\_to\_gdal: Could not load the output GDAL driver.
-<!-- pagebreak -->
+<!--more-->
So why does this happen? This has been an issue since our release of 2.0.6/2.13 PostGIS security patches that by default disabled all raster drivers and out-of-db raster storage. Raster is much less useful if you don't have any raster drivers enabled, so you need to renable them or the selective ones you need.
diff --git a/content/post/2015/10-25_postgis_sfcgal_extension.md b/content/post/2015/10-25_postgis_sfcgal_extension.md
index 229226e..96778e8 100644
--- a/content/post/2015/10-25_postgis_sfcgal_extension.md
+++ b/content/post/2015/10-25_postgis_sfcgal_extension.md
@@ -20,7 +20,7 @@ as in this question: <a href="http://gis.stackexchange.com/questions/167687/sfcg
There are two main causes for this:
-<!-- pagebreak -->
+<!--more-->
1. The ``CREATE EXTENSION postgis_sfcgal;`` syntax is new in PostGIS 2.2. Although SFCGAL was available in PostGIS 2.1,
you needed to use the sfcgal.sql script in contrib to install it. So if you have PostGIS 2.1, you definitely can't use the CREATE EXTENSION syntax.
diff --git a/content/post/2016/03-13_tip_pixels_of_range_value.md b/content/post/2016/03-13_tip_pixels_of_range_value.md
index 51264a4..9e80481 100644
--- a/content/post/2016/03-13_tip_pixels_of_range_value.md
+++ b/content/post/2016/03-13_tip_pixels_of_range_value.md
@@ -16,7 +16,7 @@ their rasters as Pixel valued polygons they then filter
with WHERE val > 90,
where ```ST_Reclass``` does the same thing but orders of magnitude faster.
-<!-- pagebreak -->
+<!--more-->
The question goes something like this
diff --git a/content/post/2016/03-17_clever_maps.md b/content/post/2016/03-17_clever_maps.md
index f2dee2f..b54d136 100644
--- a/content/post/2016/03-17_clever_maps.md
+++ b/content/post/2016/03-17_clever_maps.md
@@ -14,7 +14,7 @@ Clever°Maps' is a three years old startup based in the Czech Republic. We creat
3. road infrastructure administration - settlement of land property rights, treaty evidence, speeding up the whole administrative process
4. assets administration - treaty management, land purchases
-<!-- pagebreak -->
+<!--more-->
All our activities take advantage of PostgreSQL as a great DBMS and PostGIS as a tool to query data our apps need. These days we keep a complete monthly updated copy of the whole Czech cadastre together with LPIS (Land Parcel Identification System), that is more than 650 GB of data. We use PostGIS for much more than simple queries (although talking millions of parcel lots it is hard to tell them simple anymore):
diff --git a/content/post/2016/03-17_vanguard_appraisals.md b/content/post/2016/03-17_vanguard_appraisals.md
index 7c6bd21..a6d246a 100644
--- a/content/post/2016/03-17_vanguard_appraisals.md
+++ b/content/post/2016/03-17_vanguard_appraisals.md
@@ -12,7 +12,7 @@ date: "2016-03-17"
Vanguard Appraisals is new to the GIS world. In fact, we aren't really in the GIS world; we just kind of brush up against it. We do mass property appraisal for entire county and city jurisdictions, and we develop software to collect, price and maintain values. We also host assessment data online so that homeowners can search and find property information much simpler from the comfort of their own home. Our software and websites are used in 7 states (IA, IL, MN, MO, NE, ND, SD).
-<!-- pagebreak -->
+<!--more-->
We were happy in our little world, doing parcel stuff, not really knowing about or using GIS, but then the landscape started changing, and GIS started popping up all over the place. Our clients starting asking us if we could host their GIS data, as well as their parcel data. Some of our clients are very small; there is one person in the Assessor's office with one computer, no server, and a very small internet pipe. Some of our clients are big with many users, multiple servers, and an internet pipe that makes me blush. :-)
diff --git a/content/post/2016/03-29_plenario_uccd.md b/content/post/2016/03-29_plenario_uccd.md
index 937651e..cb05dab 100644
--- a/content/post/2016/03-29_plenario_uccd.md
+++ b/content/post/2016/03-29_plenario_uccd.md
@@ -11,7 +11,7 @@ thumbnail: uccd-logo.png
The [Urban Center for Computation and Data (UrbanCCD)](http://www.urbanccd.org/#urbanccd) is a research initiative of Argonne National Laboratory and the Computation Institute of the University of Chicago. We create computational tools to better understand cities. One of these is [Plenario](http://plenar.io/), our hub for open geospatial data.
PostGIS makes the spatial operations at the heart of Plenario possible.
-<!-- pagebreak -->
+<!--more-->
# What is Plenario?
diff --git a/content/post/2016/04-04_remi_cura.md b/content/post/2016/04-04_remi_cura.md
index 7d6755c..3808b7b 100644
--- a/content/post/2016/04-04_remi_cura.md
+++ b/content/post/2016/04-04_remi_cura.md
@@ -12,7 +12,7 @@ The first is that PostGIS is a good steady horse (elephant?):
a database is the perfect place to store a lot of very different information in the same place and put them in relation.
For geospatial data, postgis means you always have a way to put data in relation (are they at the same place?).
-<!-- pagebreak -->
+<!--more-->
1. So we have a vehicle with lots of sensors (camera, lidar, gps, etc.)
Postgis is the perfect candidate to store metadata of all of this.
diff --git a/content/post/2016/04-05_nautilytics.md b/content/post/2016/04-05_nautilytics.md
index 8f8cbbf..fdcf921 100644
--- a/content/post/2016/04-05_nautilytics.md
+++ b/content/post/2016/04-05_nautilytics.md
@@ -12,7 +12,7 @@ thumbnail: nautilytics.jpg
We use PostGIS and PostgreSQL, among other open-source tools to build powerful web applications
for US government organizations, public, and private sector companies.
-<!-- pagebreak -->
+<!--more-->
# USAID
diff --git a/content/post/2016/09-26_postgis-2.3.0.md b/content/post/2016/09-26_postgis-2.3.0.md
index 1953f25..a821421 100644
--- a/content/post/2016/09-26_postgis-2.3.0.md
+++ b/content/post/2016/09-26_postgis-2.3.0.md
@@ -26,7 +26,7 @@ Packages from maintainers will be out in the coming days and weeks.
* [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.3.0.pdf)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.3.0/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
If you are a Mac user using newer XCode 8, you might run into some compilation issues
as a result of recent changes in XCode. Refer to [https://trac.osgeo.org/postgis/ticket/3643](https://trac.osgeo.org/postgis/ticket/3643)
diff --git a/content/post/2016/10-06_postgis-2.2.3.md b/content/post/2016/10-06_postgis-2.2.3.md
index 224c088..f49f9f4 100644
--- a/content/post/2016/10-06_postgis-2.2.3.md
+++ b/content/post/2016/10-06_postgis-2.2.3.md
@@ -16,7 +16,7 @@ As befits a patch release, the focus is on bugs and breakages.
* [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.2.3.pdf)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.2.3/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
If you are a Mac user using newer XCode 8, you might run into some compilation issues
as a result of recent changes in XCode. Refer to [https://trac.osgeo.org/postgis/ticket/3643](https://trac.osgeo.org/postgis/ticket/3643)
diff --git a/content/post/2016/11-26_postgis-2.2.4.md b/content/post/2016/11-26_postgis-2.2.4.md
index bd7faf7..e114adf 100644
--- a/content/post/2016/11-26_postgis-2.2.4.md
+++ b/content/post/2016/11-26_postgis-2.2.4.md
@@ -16,7 +16,7 @@ As befits a patch release, the focus is on bugs and breakages.
* [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.2.4.pdf)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.2.4/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
If you are a Mac user using newer XCode 8, you might run into some compilation issues
as a result of recent changes in XCode. Refer to [https://trac.osgeo.org/postgis/ticket/3643](https://trac.osgeo.org/postgis/ticket/3643)
diff --git a/content/post/2016/11-28_postgis-2.3.1.md b/content/post/2016/11-28_postgis-2.3.1.md
index 4056fba..d3ac44f 100644
--- a/content/post/2016/11-28_postgis-2.3.1.md
+++ b/content/post/2016/11-28_postgis-2.3.1.md
@@ -19,7 +19,7 @@ As befits a patch release, the focus is on bugs and breakages.
* [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.3.1.pdf)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.3.1/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/01-30_postgis-2.2.5.md b/content/post/2017/01-30_postgis-2.2.5.md
index a3545fc..86ad2d7 100644
--- a/content/post/2017/01-30_postgis-2.2.5.md
+++ b/content/post/2017/01-30_postgis-2.2.5.md
@@ -16,7 +16,7 @@ As befits a patch release, the focus is on bugs and breakages.
* [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.2.5.pdf)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.2.5/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/01-31_postgis-2.3.2.md b/content/post/2017/01-31_postgis-2.3.2.md
index 3c74b74..61eb6cf 100644
--- a/content/post/2017/01-31_postgis-2.3.2.md
+++ b/content/post/2017/01-31_postgis-2.3.2.md
@@ -19,7 +19,7 @@ and [pgRouting 2.3.2](https://lists.osgeo.org/pipermail/pgrouting-users/2017-Jan
* [epub doc download]({{< loc "postgis.release_docs">}}/postgis-2.3.2.epub)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.3.2/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/06-05_postgis-backend-is-already-set.md b/content/post/2017/06-05_postgis-backend-is-already-set.md
index 2a1a54f..a05c694 100644
--- a/content/post/2017/06-05_postgis-backend-is-already-set.md
+++ b/content/post/2017/06-05_postgis-backend-is-already-set.md
@@ -21,7 +21,7 @@ filled with these messages :
"WARNING 'postgis.backend' is already set and cannot be changed until
you reconnect"</em>
-<!-- pagebreak -->
+<!--more-->
**REASON 1:** You installed legacy.sql a while back say in 2.1, and the old legacy functions
are pointing at your old PostGIS library.
diff --git a/content/post/2017/07-01_postgis-2.3.3.md b/content/post/2017/07-01_postgis-2.3.3.md
index 5baab8b..93014b9 100644
--- a/content/post/2017/07-01_postgis-2.3.3.md
+++ b/content/post/2017/07-01_postgis-2.3.3.md
@@ -19,7 +19,7 @@ and [pgRouting 2.4.1](http://docs.pgrouting.org/2.4/en/release_notes.html#change
* [epub doc download]({{< loc "postgis.release_docs">}}/postgis-2.3.3.epub)
* [ChangeLog](https://git.osgeo.org/gogs/postgis/postgis/raw/2.3.3/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/08-05_postgis-2.4.0alpha.md b/content/post/2017/08-05_postgis-2.4.0alpha.md
index 4b3f277..3db7526 100644
--- a/content/post/2017/08-05_postgis-2.4.0alpha.md
+++ b/content/post/2017/08-05_postgis-2.4.0alpha.md
@@ -20,7 +20,7 @@ See the full list of changes in the [news file](https://git.osgeo.org/gogs/postg
* [epub doc download]({{< loc "postgis.release_docs">}}/postgis-2.4.0alpha.epub)
* [ChangeLog](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0alpha/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/09-02_postgis-2.4.0beta1.md b/content/post/2017/09-02_postgis-2.4.0beta1.md
index d9a612f..661a35f 100644
--- a/content/post/2017/09-02_postgis-2.4.0beta1.md
+++ b/content/post/2017/09-02_postgis-2.4.0beta1.md
@@ -34,7 +34,7 @@ GEOS 3.7.0 will be released around the same time as PostGIS 2.4.0 and will have
* [epub doc download]({{< loc "postgis.release_docs">}}/postgis-2.4.0beta1.epub)
* [ChangeLog](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0beta1/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/09-13_postgis-2.4.0rc1.md b/content/post/2017/09-13_postgis-2.4.0rc1.md
index c8d0203..115960b 100644
--- a/content/post/2017/09-13_postgis-2.4.0rc1.md
+++ b/content/post/2017/09-13_postgis-2.4.0rc1.md
@@ -47,7 +47,7 @@ GEOS 3.7.0 will probably not be released before PostGIS 2.4.0 is out.
* [epub doc download]({{< loc "postgis.release_docs">}}/postgis-2.4.0rc1.epub)
* [ChangeLog](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0rc1/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
[Full News](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0rc1/NEWS)
diff --git a/content/post/2017/09-19_postgis-2.1.9.md b/content/post/2017/09-19_postgis-2.1.9.md
index 7d1f1d8..a33c98a 100644
--- a/content/post/2017/09-19_postgis-2.1.9.md
+++ b/content/post/2017/09-19_postgis-2.1.9.md
@@ -18,7 +18,7 @@ As befits a patch release, the focus is on bugs and breakages.
* [pdf doc download]({{< loc "postgis.release_docs">}}/postgis-2.1.9.pdf)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.1.9/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
Please [report bugs](http://postgis.net/support/) that you find in this release.
diff --git a/content/post/2017/09-24_postgis-2.4.0rc2.md b/content/post/2017/09-24_postgis-2.4.0rc2.md
index 8cf6174..4b38bb0 100644
--- a/content/post/2017/09-24_postgis-2.4.0rc2.md
+++ b/content/post/2017/09-24_postgis-2.4.0rc2.md
@@ -42,7 +42,7 @@ ALTER EXTENSION pgrouting UPDATE;
* pgsql help files for non-english languages: [ja]({{ postgis.dev_download }}/pgsql-help-2.4-ja.tar.gz), [de]({{ postgis.dev_download }}/pgsql-help-2.4-de.tar.gz), [br]({{ postgis.dev_download }}/pgsql-help-2.4-br.tar.gz), [ko_KR]({{ postgis.dev_download }}/pgsql-help-2.4-ko_KR.tar.gz)
* [ChangeLog](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0rc2/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
[Full News](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0rc2/NEWS)
diff --git a/content/post/2017/09-27_postgis-2.4.0rc3.md b/content/post/2017/09-27_postgis-2.4.0rc3.md
index 7b0c121..77176c2 100644
--- a/content/post/2017/09-27_postgis-2.4.0rc3.md
+++ b/content/post/2017/09-27_postgis-2.4.0rc3.md
@@ -44,7 +44,7 @@ ALTER EXTENSION pgrouting UPDATE;
* pgsql help files for non-english languages: [ja]({{ postgis.dev_download }}/pgsql-help-2.4-ja.tar.gz), [de]({{ postgis.dev_download }}/pgsql-help-2.4-de.tar.gz), [br]({{ postgis.dev_download }}/pgsql-help-2.4-br.tar.gz), [ko_KR]({{ postgis.dev_download }}/pgsql-help-2.4-ko_KR.tar.gz)
* [ChangeLog](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0rc3/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
[Full News](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0rc3/NEWS)
diff --git a/content/post/2017/09-30_postgis-2.4.0.md b/content/post/2017/09-30_postgis-2.4.0.md
index d990fc4..84945c4 100644
--- a/content/post/2017/09-30_postgis-2.4.0.md
+++ b/content/post/2017/09-30_postgis-2.4.0.md
@@ -47,7 +47,7 @@ GEOS 3.7.0 is not released yet but is expected sometime next month.
* pgsql help files for non-english languages: [ja]({{ postgis.dev_download }}/pgsql-help-2.4-ja.tar.gz), [de]({{ postgis.dev_download }}/pgsql-help-2.4-de.tar.gz), [br]({{ postgis.dev_download }}/pgsql-help-2.4-br.tar.gz), [ko_KR]({{ postgis.dev_download }}/pgsql-help-2.4-ko_KR.tar.gz)
-<!-- pagebreak -->
+<!--more-->
[Full News](https://git.osgeo.org/gogs/postgis/postgis/raw/2.4.0/NEWS)
diff --git a/content/post/2017/11-07_tip-move-postgis-schema.md b/content/post/2017/11-07_tip-move-postgis-schema.md
index 406893a..a0284d2 100644
--- a/content/post/2017/11-07_tip-move-postgis-schema.md
+++ b/content/post/2017/11-07_tip-move-postgis-schema.md
@@ -22,7 +22,7 @@ it into another schema location.
You can run these steps using psql or pgAdmin or any other PostgreSQL tool you want.
-<!-- pagebreak -->
+<!--more-->
Most people have their default schema set to `public`
so not explicitly specifying an install schema will generally install `postgis` in the `public` schema.
diff --git a/content/post/2018/09-23_postgis-2.5.0.md b/content/post/2018/09-23_postgis-2.5.0.md
index b993cd6..7a91b55 100644
--- a/content/post/2018/09-23_postgis-2.5.0.md
+++ b/content/post/2018/09-23_postgis-2.5.0.md
@@ -33,7 +33,7 @@ GEOS >= 3.5
* pgsql help files for non-english languages: [de]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-de.tar.gz), [ja]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-ja.tar.gz),[kr]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-kr.tar.gz), [br]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-br.tar.gz), [es]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-es.tar.gz)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.5.0/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
**New Features**
diff --git a/content/post/2018/11-02_vanguard_appraisals.md b/content/post/2018/11-02_vanguard_appraisals.md
index 52cf4f9..c7a7aca 100644
--- a/content/post/2018/11-02_vanguard_appraisals.md
+++ b/content/post/2018/11-02_vanguard_appraisals.md
@@ -9,7 +9,7 @@ date: "2018-11-02"
Vanguard Appraisals is new to the GIS world. In fact, we aren't really in the GIS world; we just kind of brush up against it. We do mass property appraisal for entire county and city jurisdictions, and we develop software to collect, price and maintain values. We also host assessment data online so that homeowners can search and find property information much simpler from the comfort of their own home. Our software and websites are used in 7 states (IA, IL, MN, MO, NE, ND, SD).
-<!-- pagebreak -->
+<!--more-->
We were happy in our little world, doing parcel stuff, not really knowing about or using GIS, but then the landscape started changing, and GIS started popping up all over the place. Our clients starting asking us if we could host their GIS data, as well as their parcel data. Some of our clients are very small; there is one person in the Assessor's office with one computer, no server, and a very small internet pipe. Some of our clients are big with many users, multiple servers, and an internet pipe that makes me blush. :-)
diff --git a/content/post/2018/11-03_howard_hughes.md b/content/post/2018/11-03_howard_hughes.md
index 6265823..3847d87 100644
--- a/content/post/2018/11-03_howard_hughes.md
+++ b/content/post/2018/11-03_howard_hughes.md
@@ -8,7 +8,7 @@ date: "2018-11-03"
---
As a software engineer at the Howard Hughes Medical Institute, I work on a collaborative neuron reconstruction and analysis software called CATMAID [1] [2] (screenshot: [3]), which is used for neuroscience research. We use PostGIS to represent neurons in a 3D space.
-<!-- pagebreak -->
+<!--more-->
They consist of 3D points that reference their parent nodes or are the root [=soma of neuron] if they have no parent). Together with synapses, point clouds and TIN meshes for modeling compartments in a dataset, they model the spatial aspects of our neuroscience world. Users create those neuron reconstructions manually in a collaborative fashion plus segmentation programs can be used as additional data source. Using its spatial indices, PostGIS helps us to quickly query neurons in a particular field of view. The space of a single project contains sometimes 100s of millions of interconnected individual points. We also do bounding box intersection queries between neurons and compartment meshes, which then refine in the front-end by doing more precise intersection tests.
diff --git a/content/post/2018/11-18_postgis-2.5.1md b/content/post/2018/11-18_postgis-2.5.1md
index fe26a01..74bc1b0 100644
--- a/content/post/2018/11-18_postgis-2.5.1md
+++ b/content/post/2018/11-18_postgis-2.5.1md
@@ -33,7 +33,7 @@ GEOS >= 3.5
* pgsql help files for non-english languages: [de]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-de.tar.gz), [ja]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-ja.tar.gz),[kr]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-kr.tar.gz), [br]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-br.tar.gz), [es]({{< loc "postgis.release_docs">}}/pgsql-help-2.5-es.tar.gz)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.5.1/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
**Bug fixes**
diff --git a/content/post/2018/11-22_postgis-2.2.8.md b/content/post/2018/11-22_postgis-2.2.8.md
index 66efedc..dcc6505 100644
--- a/content/post/2018/11-22_postgis-2.2.8.md
+++ b/content/post/2018/11-22_postgis-2.2.8.md
@@ -29,7 +29,7 @@ This release supports PostgreSQL 9.1-9.6.
* [epub doc download]({{< loc "postgis.release_docs">}}/postgis-2.2.8.epub)
* [Changelog](https://svn.osgeo.org/postgis/tags/2.2.8/ChangeLog)
-<!-- pagebreak -->
+<!--more-->
**Bug fixes**
diff --git a/content/post/2018/11-24_postgis-patches.md b/content/post/2018/11-24_postgis-patches.md
index 4ef7c6a..64eb912 100644
--- a/content/post/2018/11-24_postgis-patches.md
+++ b/content/post/2018/11-24_postgis-patches.md
@@ -11,7 +11,7 @@ thumbnail:
The PostGIS development team is pleased to provide
bug fix 2.3.8 and 2.4.6 for the 2.3 and 2.4 stable branches.
-<!-- pagebreak -->
+<!--more-->
**2.4.6**
This release supports PostgreSQL 9.3-10.
diff --git a/content/post/2019/03-11_postgis-patches.md b/content/post/2019/03-11_postgis-patches.md
index 593b2ed..06567a3 100644
--- a/content/post/2019/03-11_postgis-patches.md
+++ b/content/post/2019/03-11_postgis-patches.md
@@ -14,7 +14,7 @@ bug fix 2.5.2, 2.4.7, and 2.3.9 for the 2.5, 2.4, and 2.3 stable branches.
These are the first versions to be able to compile against [Proj 6.0.0](https://proj4.org/download.html),
You must upgrade to these if you are using Proj 6.
-<!-- pagebreak -->
+<!--more-->
**2.5.2**
This release supports PostgreSQL 9.3-11
(will compile against PostgreSQL 12, but not pass tests. Use only for pg_upgrade.
diff --git a/content/post/2019/05-26_postgis-3.0.0alpha1.md b/content/post/2019/05-26_postgis-3.0.0alpha1.md
index 09b0a3a..2285b22 100644
--- a/content/post/2019/05-26_postgis-3.0.0alpha1.md
+++ b/content/post/2019/05-26_postgis-3.0.0alpha1.md
@@ -14,7 +14,7 @@ This release works with PostgreSQL 9.5-12beta1 and GEOS >= 3.6
Best served with PostgreSQL 12beta1.
-<!-- pagebreak -->
+<!--more-->
**3.0.0alpha1**
diff --git a/content/post/2019/06-02_postgis-3.0.0alpha2.md b/content/post/2019/06-02_postgis-3.0.0alpha2.md
index d7e7ba6..e2ba489 100644
--- a/content/post/2019/06-02_postgis-3.0.0alpha2.md
+++ b/content/post/2019/06-02_postgis-3.0.0alpha2.md
@@ -14,7 +14,7 @@ This release works with PostgreSQL 9.5-12beta1 and GEOS >= 3.6
Best served with PostgreSQL 12beta1.
-<!-- pagebreak -->
+<!--more-->
**3.0.0alpha2**
diff --git a/content/post/2019/07-01_postgis-3.0.0alpha3.md b/content/post/2019/07-01_postgis-3.0.0alpha3.md
index c4f7c04..a2a45a7 100644
--- a/content/post/2019/07-01_postgis-3.0.0alpha3.md
+++ b/content/post/2019/07-01_postgis-3.0.0alpha3.md
@@ -14,7 +14,7 @@ This release works with PostgreSQL 9.5-12beta2 and GEOS >= 3.6
Best served with [PostgreSQL 12beta2](https://www.postgresql.org/developer/beta/).
-<!-- pagebreak -->
+<!--more-->
**3.0.0alpha3**
diff --git a/content/post/2019/08-11_postgis-patches.md b/content/post/2019/08-11_postgis-patches.md
index 1f43cc1..497bde0 100644
--- a/content/post/2019/08-11_postgis-patches.md
+++ b/content/post/2019/08-11_postgis-patches.md
@@ -12,7 +12,7 @@ The PostGIS development team is pleased to provide
enhancements/features 3.0.0alpha4 for 3.0 feature major branch
bug fix 2.5.3, 2.4.8, and 2.3.10 for the 2.5, 2.4, and 2.3 stable branches.
-<!-- pagebreak -->
+<!--more-->
**3.0.0alpha4**
This release works with PostgreSQL 9.5-12beta3 and GEOS >= 3.6
diff --git a/content/post/2019/09-28_postgis-3.0.0beta1.md b/content/post/2019/09-28_postgis-3.0.0beta1.md
index 48dbcd5..96581a5 100644
--- a/content/post/2019/09-28_postgis-3.0.0beta1.md
+++ b/content/post/2019/09-28_postgis-3.0.0beta1.md
@@ -16,7 +16,7 @@ Best served with [PostgreSQL 12RC1](https://www.postgresql.org/developer/beta/)
and [GEOS 3.8.0beta1](https://lists.osgeo.org/pipermail/geos-devel/2019-September/009267.html)
both of which came out in the past couple of days.
-<!-- pagebreak -->
+<!--more-->
**3.0.0beta1**
diff --git a/content/post/2019/10-08_postgis-3.0.0rc1.md b/content/post/2019/10-08_postgis-3.0.0rc1.md
index e4bd633..ab21965 100644
--- a/content/post/2019/10-08_postgis-3.0.0rc1.md
+++ b/content/post/2019/10-08_postgis-3.0.0rc1.md
@@ -16,7 +16,7 @@ Best served with [PostgreSQL 12](https://www.postgresql.org/about/news/1976/)
, [GEOS 3.8.0rc2](https://lists.osgeo.org/pipermail/geos-devel/2019-October/009288.html)
and [pgRouting 3.0.0-alpha](https://github.com/pgRouting/pgrouting/releases/tag/v3.0.0-alpha).
-<!-- pagebreak -->
+<!--more-->
**3.0.0rc1**
diff --git a/content/post/2019/10-13_postgis-3.0.0rc2.md b/content/post/2019/10-13_postgis-3.0.0rc2.md
index 59b4898..ac9dfe6 100644
--- a/content/post/2019/10-13_postgis-3.0.0rc2.md
+++ b/content/post/2019/10-13_postgis-3.0.0rc2.md
@@ -18,7 +18,7 @@ Best served with [PostgreSQL 12](https://www.postgresql.org/about/news/1976/)
and [pgRouting 3.0.0-alpha](https://github.com/pgRouting/pgrouting/releases/tag/v3.0.0-alpha).
-<!-- pagebreak -->
+<!--more-->
**3.0.0rc2**
diff --git a/content/post/2019/10-20_postgis-3.0.0.md b/content/post/2019/10-20_postgis-3.0.0.md
index fd06c20..f962263 100644
--- a/content/post/2019/10-20_postgis-3.0.0.md
+++ b/content/post/2019/10-20_postgis-3.0.0.md
@@ -18,7 +18,7 @@ Best served with [PostgreSQL 12](https://www.postgresql.org/about/news/1976/)
, [GEOS 3.8.0](https://lists.osgeo.org/pipermail/geos-devel/2019-October/009342.html)
and [pgRouting 3.0.0-beta](https://github.com/pgRouting/pgrouting/releases/tag/v3.0.0-beta).
-<!-- pagebreak -->
+<!--more-->
**3.0.0**
diff --git a/content/post/2020/02-02_postgis-3.1.0alpha1.md b/content/post/2020/02-02_postgis-3.1.0alpha1.md
index 25aa209..78a8c01 100644
--- a/content/post/2020/02-02_postgis-3.1.0alpha1.md
+++ b/content/post/2020/02-02_postgis-3.1.0alpha1.md
@@ -14,7 +14,7 @@ The PostGIS Team is pleased to release the first alpha of upcoming PostGIS
Best served with [PostgreSQL 12.1](https://www.postgresql.org/docs/12/release-12-1.html),
[GEOS 3.8.0](https://lists.osgeo.org/pipermail/geos-devel/2019-October/009342.html).
-<!-- pagebreak -->
+<!--more-->
**3.1.0alpha1**
diff --git a/content/post/2020/02-20_postgis-3.0.1.md b/content/post/2020/02-20_postgis-3.0.1.md
index 323d99b..6c78c19 100644
--- a/content/post/2020/02-20_postgis-3.0.1.md
+++ b/content/post/2020/02-20_postgis-3.0.1.md
@@ -14,7 +14,7 @@ The PostGIS Team is pleased to release PostGIS 3.0.1.
Best served with [PostgreSQL 12.2](https://www.postgresql.org/docs/12/release-12-2.html),
GEOS 3.8.0, SFCGAL 1.3.7, GDAL 3.0.4, PROJ 6.3.1, protobuf-c 1.3.3, json-c 0.13.1.
-<!-- pagebreak -->
+<!--more-->
**PostGIS 3.0.1**
diff --git a/content/post/2020/02-28_postgis-2.5.4.md b/content/post/2020/02-28_postgis-2.5.4.md
index 23d8d79..e0f1b93 100644
--- a/content/post/2020/02-28_postgis-2.5.4.md
+++ b/content/post/2020/02-28_postgis-2.5.4.md
@@ -13,7 +13,7 @@ The PostGIS Team is pleased to release PostGIS 2.5.4.
* [NEWS]({{< loc "postgis.release_notes">}}/2.5.4/NEWS)
* [PDF docs en]({{< loc "postgis.release_docs">}}/postgis-2.5.4.pdf)
-<!-- pagebreak -->
+<!--more-->
If you come across any issues, feel free to report via our ticket tracker
https://trac.osgeo.org/postgis or mailing list with details as described
diff --git a/content/post/2020/05-31_postgis-2.3.11.md b/content/post/2020/05-31_postgis-2.3.11.md
index 1618a71..ec85c0c 100644
--- a/content/post/2020/05-31_postgis-2.3.11.md
+++ b/content/post/2020/05-31_postgis-2.3.11.md
@@ -23,7 +23,7 @@ https://trac.osgeo.org/postgis or mailing list with details as described
[here](https://postgis.net/support/). For security issues, send reports to
security at postgis.net.
-<!-- pagebreak -->
+<!--more-->
**Bug Fixes and Enchantments**
diff --git a/content/post/2020/07-18_postgis-3.1.0alpha2.md b/content/post/2020/07-18_postgis-3.1.0alpha2.md
index da26afd..0c87bf5 100644
--- a/content/post/2020/07-18_postgis-3.1.0alpha2.md
+++ b/content/post/2020/07-18_postgis-3.1.0alpha2.md
@@ -20,7 +20,7 @@ GEOS 3.7 or higher is recommended.
[pgRouting 3.1.0](https://lists.osgeo.org/pipermail/pgrouting-dev/2020-July/002105.html) which will also be released soon.
-<!-- pagebreak -->
+<!--more-->
**3.1.0alpha2**
diff --git a/content/post/2020/08-15_postgis-patches.md b/content/post/2020/08-15_postgis-patches.md
index e53db89..5fb5a4c 100644
--- a/content/post/2020/08-15_postgis-patches.md
+++ b/content/post/2020/08-15_postgis-patches.md
@@ -12,7 +12,7 @@ The PostGIS development team is pleased to provide
bug fix and performance enhancements
3.0.2, 2.5.5, 2.4.9 for the 3.0, 2.5, and 2.4 stable branches.
-<!-- pagebreak -->
+<!--more-->
**3.0.2**
This release works with PostgreSQL 9.5-13beta2 and GEOS >= 3.6
diff --git a/content/post/2020/11-19_postgis-3.1.0alpha3.md b/content/post/2020/11-19_postgis-3.1.0alpha3.md
index 6975cb8..38c6b55 100644
--- a/content/post/2020/11-19_postgis-3.1.0alpha3.md
+++ b/content/post/2020/11-19_postgis-3.1.0alpha3.md
@@ -20,7 +20,7 @@ GEOS 3.7 or higher is recommended.
[pgRouting 3.1.1](https://lists.osgeo.org/pipermail/pgrouting-dev/2020-November/002149.html)
-<!-- pagebreak -->
+<!--more-->
**3.1.0alpha3**
diff --git a/content/post/2020/11-20_postgis-3.0.3.md b/content/post/2020/11-20_postgis-3.0.3.md
index ab4d95b..686b651 100644
--- a/content/post/2020/11-20_postgis-3.0.3.md
+++ b/content/post/2020/11-20_postgis-3.0.3.md
@@ -16,7 +16,7 @@ and [GEOS 3.8.1](https://geos.osgeo.org)
[pgRouting 3.1.1](https://lists.osgeo.org/pipermail/pgrouting-dev/2020-November/002149.html)
-<!-- pagebreak -->
+<!--more-->
**PostGIS 3.0.3**
diff --git a/content/post/2020/12-09_postgis-3.1.0beta1.md b/content/post/2020/12-09_postgis-3.1.0beta1.md
index 74ae544..ce7049d 100644
--- a/content/post/2020/12-09_postgis-3.1.0beta1.md
+++ b/content/post/2020/12-09_postgis-3.1.0beta1.md
@@ -19,7 +19,7 @@ Best served with:
GEOS 3.7 or higher is recommended.
* [pgRouting 3.1.1](https://lists.osgeo.org/pipermail/pgrouting-dev/2020-November/002149.html)
-<!-- pagebreak -->
+<!--more-->
**3.1.beta1**
diff --git a/content/post/2020/12-14_postgis-3.1.0rc1.md b/content/post/2020/12-14_postgis-3.1.0rc1.md
index 1b67fae..9e4df4e 100644
--- a/content/post/2020/12-14_postgis-3.1.0rc1.md
+++ b/content/post/2020/12-14_postgis-3.1.0rc1.md
@@ -16,7 +16,7 @@ Best served with:
* [GEOS 3.9](https://lists.osgeo.org/pipermail/geos-devel/2020-December/010003.html)
* [pgRouting 3.1.1](https://lists.osgeo.org/pipermail/pgrouting-dev/2020-November/002149.html)
-<!-- pagebreak -->
+<!--more-->
* Requires GEOS 3.6+ and PostgreSQL 9.6+.
* MVT support requires protobuf-c 1.1 or higher.
diff --git a/content/post/2020/12-18_postgis-3.1.0.md b/content/post/2020/12-18_postgis-3.1.0.md
index ade16a5..f5c29b4 100644
--- a/content/post/2020/12-18_postgis-3.1.0.md
+++ b/content/post/2020/12-18_postgis-3.1.0.md
@@ -20,7 +20,7 @@ Geometry generators to create [hexagonal and square tilings](http://blog.clevere
Finally, PostGIS exposes the [latest enhancements](http://blog.cleverelephant.ca/2020/12/waiting-postgis-31-3.html) in the GEOS geometry library 3.9 version. The new overlay engine (aka "[OverlayNG](https://lin-ear-th-inking.blogspot.com/2020/10/overlayng-lands-in-jts-master.html)") provides [more robust](https://lin-ear-th-inking.blogspot.com/2020/06/jts-overlayng-tolerant-topology.html) handling of difficult input geometries, using a set of [new noding strategies](https://lin-ear-th-inking.blogspot.com/2020/06/jts-overlayng-noding-strategies.html) to process geometry. For the end user, this should mean no more "topology exceptions" when using the union, difference, intersection or symmetric difference functions. PostGIS also exposes the new fixed precision overlay capability via an additional grid-size parameter on [ST_Intersection](http://postgis.net/docs/manual-dev/ST_Intersection.html) and the other overlay functions.
-<!-- pagebreak -->
+<!--more-->
Best served with:
diff --git a/content/post/2021/01-28_postgis-3.1.1.md b/content/post/2021/01-28_postgis-3.1.1.md
index d0ce05d..bdd6bb5 100644
--- a/content/post/2021/01-28_postgis-3.1.1.md
+++ b/content/post/2021/01-28_postgis-3.1.1.md
@@ -17,7 +17,7 @@ This release is a bug fix release, addressing issues found in the previous 3.1 r
- [#4825](https://trac.osgeo.org/postgis/ticket/4825), Unstable results from ST_MakeValid
- [#4823](https://trac.osgeo.org/postgis/ticket/4823), Avoid listing the same geometry in different collections
-<!-- pagebreak -->
+<!--more-->
**3.1.1**
diff --git a/content/post/2021/05-21_postgis-3.1.2.md b/content/post/2021/05-21_postgis-3.1.2.md
index fa2be3b..f1edc0c 100644
--- a/content/post/2021/05-21_postgis-3.1.2.md
+++ b/content/post/2021/05-21_postgis-3.1.2.md
@@ -28,7 +28,7 @@ This release is a bug fix release, addressing issues found in the previous 3.1 r
- [#4845](https://trac.osgeo.org/postgis/ticket/4845), Add Pg14 build support (Paul Ramsey)
-<!-- pagebreak -->
+<!--more-->
**3.1.2**
diff --git a/content/post/2021/07-02_postgis-3.1.3.md b/content/post/2021/07-02_postgis-3.1.3.md
index 73f536c..d42446e 100644
--- a/content/post/2021/07-02_postgis-3.1.3.md
+++ b/content/post/2021/07-02_postgis-3.1.3.md
@@ -17,7 +17,7 @@ This release is a bug fix release, addressing issues found in the previous 3.1 r
- [#4927](https://trac.osgeo.org/postgis/ticket/4927), Fix PostgreSQL 14 compile FuncnameGetCandidates changes needed to compile against PostgreSQL 14 beta2 or higher (Regina Obe, Julien Rouhaud)
-<!-- pagebreak -->
+<!--more-->
**3.1.3**
diff --git a/content/post/2021/09-04_postgis-patches.md b/content/post/2021/09-04_postgis-patches.md
index 10b005a..6e98e94 100644
--- a/content/post/2021/09-04_postgis-patches.md
+++ b/content/post/2021/09-04_postgis-patches.md
@@ -12,7 +12,7 @@ The PostGIS development team is pleased to provide
bug fix and performance enhancements
3.1.4 and 3.0.4 for the 3.1, 3.0 stable branches.
-<!-- pagebreak -->
+<!--more-->
**3.1.4**
This release supports PostgreSQL 9.6-14.
diff --git a/content/post/2021/09-11_postgis-3.2.0alpha1.md b/content/post/2021/09-11_postgis-3.2.0alpha1.md
index 03fe36d..1428a77 100644
--- a/content/post/2021/09-11_postgis-3.2.0alpha1.md
+++ b/content/post/2021/09-11_postgis-3.2.0alpha1.md
@@ -13,7 +13,7 @@ The PostGIS Team is pleased to release the first alpha of the upcoming PostGIS
Best served with [PostgreSQL 14 beta3](https://www.postgresql.org/docs/14/release.html). This version of PostGIS utilizes the faster GiST building support API introduced in PostgreSQL 14. If compiled with the in-development [GEOS 3.10dev](https://lists.osgeo.org/pipermail/geos-devel/2021-September/010315.html) you can take advantage of improvements in ST_MakeValid. This release also includes many additional functions and improvements for `postgis_raster` and `postgis_topology` extensions.
-<!-- pagebreak -->
+<!--more-->
**3.2.0alpha1**
This release supports PostgreSQL 9.6-14.
diff --git a/content/post/2021/10-23_postgis-3.2.0beta1.md b/content/post/2021/10-23_postgis-3.2.0beta1.md
index 2ec8c94..e991a93 100644
--- a/content/post/2021/10-23_postgis-3.2.0beta1.md
+++ b/content/post/2021/10-23_postgis-3.2.0beta1.md
@@ -12,7 +12,7 @@ The PostGIS Team is pleased to release the first beta of the upcoming PostGIS
Best served with [PostgreSQL 14](https://www.postgresql.org/docs/14/release.html). This version of PostGIS utilizes the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released [GEOS 3.10.0](https://lists.osgeo.org/pipermail/geos-devel/2021-October/010484.html) you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for `postgis_raster` and `postgis_topology` extensions.
-<!-- pagebreak -->
+<!--more-->
**3.2.0beta1**
diff --git a/content/post/2021/11-26_postgis-3.2.0beta2.md b/content/post/2021/11-26_postgis-3.2.0beta2.md
index a032e5d..8ec6c8c 100644
--- a/content/post/2021/11-26_postgis-3.2.0beta2.md
+++ b/content/post/2021/11-26_postgis-3.2.0beta2.md
@@ -13,7 +13,7 @@ The PostGIS Team is pleased to release the second beta of the upcoming PostGIS
Best served with [PostgreSQL 14](https://www.postgresql.org/docs/14/release.html). This version of PostGIS utilizes the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released [GEOS 3.10.1](https://lists.osgeo.org/pipermail/geos-devel/2021-November/010556.html) you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for `postgis_raster` and `postgis_topology` extensions.
-<!-- pagebreak -->
+<!--more-->
**3.2.0beta2**
diff --git a/content/post/2021/12-04_postgis-3.2.0beta3.md b/content/post/2021/12-04_postgis-3.2.0beta3.md
index 91c5997..b032377 100644
--- a/content/post/2021/12-04_postgis-3.2.0beta3.md
+++ b/content/post/2021/12-04_postgis-3.2.0beta3.md
@@ -13,7 +13,7 @@ The PostGIS Team is pleased to release the third beta of the upcoming PostGIS
Best served with [PostgreSQL 14](https://www.postgresql.org/docs/14/release.html). This version of PostGIS can utilize the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released [GEOS 3.10.1](https://lists.osgeo.org/pipermail/geos-devel/2021-November/010556.html) you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for `postgis`, `postgis_raster` and `postgis_topology` extensions and a new input/export format [FlatGeobuf](https://flatgeobuf.org/).
-<!-- pagebreak -->
+<!--more-->
**3.2.0beta3**
diff --git a/content/post/2021/12-10_postgis-3.2.0rc1.md b/content/post/2021/12-10_postgis-3.2.0rc1.md
index 6a1bdf7..cb3a869 100644
--- a/content/post/2021/12-10_postgis-3.2.0rc1.md
+++ b/content/post/2021/12-10_postgis-3.2.0rc1.md
@@ -13,7 +13,7 @@ The PostGIS Team is pleased to release the first rc of the upcoming PostGIS
Best served with [PostgreSQL 14](https://www.postgresql.org/docs/14/release.html). This version of PostGIS can utilize the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released [GEOS 3.10.1](https://lists.osgeo.org/pipermail/geos-devel/2021-November/010556.html) you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for `postgis`, `postgis_raster` and `postgis_topology` extensions and a new input/export format [FlatGeobuf](https://flatgeobuf.org/).
-<!-- pagebreak -->
+<!--more-->
**3.2.0rc1**
diff --git a/content/post/2021/12-17_olivier-courtin.md b/content/post/2021/12-17_olivier-courtin.md
index 40e8f58..4b007ee 100644
--- a/content/post/2021/12-17_olivier-courtin.md
+++ b/content/post/2021/12-17_olivier-courtin.md
@@ -10,7 +10,7 @@ date: "2021-12-17"
In March 2020 we lost a long time PostGIS developer and friend, Olivier Courtin. The PostGIS 3.2.0 release is named in his honor.
<br />
<img src="/images/olivier_courtin.png" width="300px" alt="Olivier at Code Sprint"/>
-<!-- pagebreak -->
+<!--more-->
Olivier was a long time contributor to the PostGIS project and co-founder of [Oslandia](https://oslandia.com), a French Geospatial company focused on Open Source GIS and spatial data solutions. In more than a 10 year span, he contributed to PostGIS on many sides. He helped introduce and enhance many of the PostGIS output functions: ST_AsGML, ST_AsKML, ST_AsGeoJSON, and ST_AsSVG. He also helped implement 3D surface geometry support in PostGIS 2.0 and addition of advanced 2D and 3D functions via [SFCGAL](https://oslandia.gitlab.io/SFCGAL/).
Olivier was a charter member of the Open Source Geospatial Foundation [OSGeo](https://osgeo.org) and a vocal advocate of Open Source software. In addition to the PostGIS OSGeo project, he contributed to other OSGeo projects: QGIS, and MapServer. He also was a speaker in many geospatial and PostgreSQL conferences and was an organizer of OSGeo Code Sprint in Paris (2012) as well as several PostgreSQL Day France conferences.
diff --git a/content/post/2021/12-18_postgis-3.2.0.md b/content/post/2021/12-18_postgis-3.2.0.md
index 8e78d01..39cc8c8 100644
--- a/content/post/2021/12-18_postgis-3.2.0.md
+++ b/content/post/2021/12-18_postgis-3.2.0.md
@@ -19,7 +19,7 @@ Companies that contributed significantly to this release are:
* [NIBIO](https://nibio.no) Developer funding for topology improvements
* [Paragon Corporation](https://www.paragoncorporation.com) -- General CI bot management, release management, alignment of PostGIS with PostgreSQL versions.
-<!-- pagebreak -->
+<!--more-->
Best served with [PostgreSQL 14](https://www.postgresql.org/docs/14/release.html). This version of PostGIS can utilize the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released [GEOS 3.10.1](https://lists.osgeo.org/pipermail/geos-devel/2021-November/010556.html) you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for `postgis`, `postgis_raster` and `postgis_topology` extensions and a new input/export format [FlatGeobuf](https://flatgeobuf.org/).
diff --git a/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md b/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md
index 31af0d2..565f03d 100644
--- a/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md
+++ b/content/post/2022/01-14_tip-upgrading-raster-from-2-3.md
@@ -26,7 +26,7 @@ You can run these steps using psql or pgAdmin or any other PostgreSQL tool you w
Regardless which version of PostGIS you are coming from, you should install the PostGIS 3.* binaries first.
-<!-- pagebreak -->
+<!--more-->
```postgres
-- this step only needed for PostGIS < 2.5.4
diff --git a/content/post/2022/02-01_postgis-3.1.5.md b/content/post/2022/02-01_postgis-3.1.5.md
index f395058..80a5381 100644
--- a/content/post/2022/02-01_postgis-3.1.5.md
+++ b/content/post/2022/02-01_postgis-3.1.5.md
@@ -19,7 +19,7 @@ The PostGIS Team is pleased to release PostGIS 3.1.5!
This release is a bug fix release, addressing issues found in the previous 3.1 releases.
-<!-- pagebreak -->
+<!--more-->
- [#4994](https://trac.osgeo.org/postgis/ticket/4994), Random missing INSERT in shp2pgsql (Sandro Santilli)
- [#5016](https://trac.osgeo.org/postgis/ticket/5016), loader (shp2pgsq): Respect LDFLAGS (Greg Troxel)
diff --git a/content/post/2022/02-02_postgis-3.0.5.md b/content/post/2022/02-02_postgis-3.0.5.md
index f7ee55a..82a8d65 100644
--- a/content/post/2022/02-02_postgis-3.0.5.md
+++ b/content/post/2022/02-02_postgis-3.0.5.md
@@ -16,7 +16,7 @@ The PostGIS Team is pleased to release PostGIS 3.0.5.
* [NEWS](https://git.osgeo.org/gitea/postgis/postgis/raw/tag/3.0.5/NEWS)
* [PDF docs en]({{< loc "postgis.release_docs">}}/postgis-3.0.5.pdf)
-<!-- pagebreak -->
+<!--more-->
This release is a bug fix release, addressing issues found in the previous 3.0 releases.
@@ -24,7 +24,7 @@ This release is a bug fix release, addressing issues found in the previous 3.0 r
- [#5046](https://trac.osgeo.org/postgis/ticket/5046), Fix upgrades in absence of old library (Sandro Santilli)
- [#5069](https://trac.osgeo.org/postgis/ticket/5069), search_path vulnerabilty during install/upgrade (Regina Obe)
-<!-- pagebreak -->
+<!--more-->
**Upgrading**
diff --git a/content/post/2022/02-12_postgis-3.2.1.md b/content/post/2022/02-12_postgis-3.2.1.md
index 1a1c60e..df7bd4a 100644
--- a/content/post/2022/02-12_postgis-3.2.1.md
+++ b/content/post/2022/02-12_postgis-3.2.1.md
@@ -19,7 +19,7 @@ The PostGIS Team is pleased to release PostGIS 3.2.1!
This release is a bug fix release, addressing issues found in the previous 3.1 releases.
-<!-- pagebreak -->
+<!--more-->
**Bug Fixes**
diff --git a/content/post/2022/04-21_postgis-2.5.6.md b/content/post/2022/04-21_postgis-2.5.6.md
index 31292ac..3bd9c2d 100644
--- a/content/post/2022/04-21_postgis-2.5.6.md
+++ b/content/post/2022/04-21_postgis-2.5.6.md
@@ -19,7 +19,7 @@ The PostGIS Team is pleased to release PostGIS 2.5.6!
This release is a bug fix release, addressing issues found in the previous 2.5 releases.
-<!-- pagebreak -->
+<!--more-->
**Bug Fixes**
-----------------------------------------------------------------------
Summary of changes:
content/events/11-21_postgis-day-panel.md | 2 +-
content/post/2012/06-22_postgis-2-0-1.md | 2 +-
content/post/2012/07-20_postgis-1-5-5.md | 2 +-
content/post/2012/10-17_infoterra/index.md | 2 +-
content/post/2012/10-18_ign/index.md | 2 +-
content/post/2012/10-30_postgis-1-5-6.md | 2 +-
content/post/2012/10-31_postgis-1-5-7.md | 2 +-
content/post/2012/11-15_postgis-1-5-8.md | 2 +-
content/post/2012/12-03_postgis-2-0-2.md | 2 +-
content/post/2013/03-01_postgis-2-0-3.md | 2 +-
content/post/2013/05-11_postgis-2-1-0beta2.md | 2 +-
content/post/2013/06-22_postgis-2-1-0beta3.md | 2 +-
content/post/2013/07-10_postgis-2-1-0rc1.md | 2 +-
content/post/2013/08-03_postgis-2-1-0rc2.md | 2 +-
content/post/2013/08-17_postgis-2-1-0.md | 2 +-
content/post/2013/08-18_tip_lon_lat.md | 2 +-
content/post/2013/08-26_tip_ST_DWithin.md | 2 +-
content/post/2013/08-30_tip_ST_Set_or_Transform.md | 2 +-
content/post/2013/09-06_postgis-2-0-4.md | 2 +-
content/post/2013/10-05_tip_pgAdmin_shows_no_data.md | 2 +-
content/post/2013/11-08_postgis-2.1.1.md | 2 +-
content/post/2014/03-14_tip_intersection_faster.md | 2 +-
content/post/2014/03-31_postgis-2-0-5.md | 2 +-
content/post/2014/03-31_postgis-2.1.2.md | 2 +-
content/post/2014/05-19_postgis-2.0.6_and_2.1.3.md | 2 +-
content/post/2014/09-10_postgis-2.1.4.md | 2 +-
content/post/2014/09-26_tip_count_of_pixel_values.md | 2 +-
content/post/2014/12-18_postgis-2.1.5.md | 2 +-
content/post/2015/03-20_postgis-2.1.6.md | 2 +-
content/post/2015/05-02_tip_enable_raster_drivers.md | 2 +-
content/post/2015/10-25_postgis_sfcgal_extension.md | 2 +-
content/post/2016/03-13_tip_pixels_of_range_value.md | 2 +-
content/post/2016/03-17_clever_maps.md | 2 +-
content/post/2016/03-17_vanguard_appraisals.md | 2 +-
content/post/2016/03-29_plenario_uccd.md | 2 +-
content/post/2016/04-04_remi_cura.md | 2 +-
content/post/2016/04-05_nautilytics.md | 2 +-
content/post/2016/09-26_postgis-2.3.0.md | 2 +-
content/post/2016/10-06_postgis-2.2.3.md | 2 +-
content/post/2016/11-26_postgis-2.2.4.md | 2 +-
content/post/2016/11-28_postgis-2.3.1.md | 2 +-
content/post/2017/01-30_postgis-2.2.5.md | 2 +-
content/post/2017/01-31_postgis-2.3.2.md | 2 +-
content/post/2017/06-05_postgis-backend-is-already-set.md | 2 +-
content/post/2017/07-01_postgis-2.3.3.md | 2 +-
content/post/2017/08-05_postgis-2.4.0alpha.md | 2 +-
content/post/2017/09-02_postgis-2.4.0beta1.md | 2 +-
content/post/2017/09-13_postgis-2.4.0rc1.md | 2 +-
content/post/2017/09-19_postgis-2.1.9.md | 2 +-
content/post/2017/09-24_postgis-2.4.0rc2.md | 2 +-
content/post/2017/09-27_postgis-2.4.0rc3.md | 2 +-
content/post/2017/09-30_postgis-2.4.0.md | 2 +-
content/post/2017/11-07_tip-move-postgis-schema.md | 2 +-
content/post/2018/09-23_postgis-2.5.0.md | 2 +-
content/post/2018/11-02_vanguard_appraisals.md | 2 +-
content/post/2018/11-03_howard_hughes.md | 2 +-
content/post/2018/11-18_postgis-2.5.1md | 2 +-
content/post/2018/11-22_postgis-2.2.8.md | 2 +-
content/post/2018/11-24_postgis-patches.md | 2 +-
content/post/2019/03-11_postgis-patches.md | 2 +-
content/post/2019/05-26_postgis-3.0.0alpha1.md | 2 +-
content/post/2019/06-02_postgis-3.0.0alpha2.md | 2 +-
content/post/2019/07-01_postgis-3.0.0alpha3.md | 2 +-
content/post/2019/08-11_postgis-patches.md | 2 +-
content/post/2019/09-28_postgis-3.0.0beta1.md | 2 +-
content/post/2019/10-08_postgis-3.0.0rc1.md | 2 +-
content/post/2019/10-13_postgis-3.0.0rc2.md | 2 +-
content/post/2019/10-20_postgis-3.0.0.md | 2 +-
content/post/2020/02-02_postgis-3.1.0alpha1.md | 2 +-
content/post/2020/02-20_postgis-3.0.1.md | 2 +-
content/post/2020/02-28_postgis-2.5.4.md | 2 +-
content/post/2020/05-31_postgis-2.3.11.md | 2 +-
content/post/2020/07-18_postgis-3.1.0alpha2.md | 2 +-
content/post/2020/08-15_postgis-patches.md | 2 +-
content/post/2020/11-19_postgis-3.1.0alpha3.md | 2 +-
content/post/2020/11-20_postgis-3.0.3.md | 2 +-
content/post/2020/12-09_postgis-3.1.0beta1.md | 2 +-
content/post/2020/12-14_postgis-3.1.0rc1.md | 2 +-
content/post/2020/12-18_postgis-3.1.0.md | 2 +-
content/post/2021/01-28_postgis-3.1.1.md | 2 +-
content/post/2021/05-21_postgis-3.1.2.md | 2 +-
content/post/2021/07-02_postgis-3.1.3.md | 2 +-
content/post/2021/09-04_postgis-patches.md | 2 +-
content/post/2021/09-11_postgis-3.2.0alpha1.md | 2 +-
content/post/2021/10-23_postgis-3.2.0beta1.md | 2 +-
content/post/2021/11-26_postgis-3.2.0beta2.md | 2 +-
content/post/2021/12-04_postgis-3.2.0beta3.md | 2 +-
content/post/2021/12-10_postgis-3.2.0rc1.md | 2 +-
content/post/2021/12-17_olivier-courtin.md | 2 +-
content/post/2021/12-18_postgis-3.2.0.md | 2 +-
content/post/2022/01-14_tip-upgrading-raster-from-2-3.md | 2 +-
content/post/2022/02-01_postgis-3.1.5.md | 2 +-
content/post/2022/02-02_postgis-3.0.5.md | 4 ++--
content/post/2022/02-12_postgis-3.2.1.md | 2 +-
content/post/2022/04-21_postgis-2.5.6.md | 2 +-
95 files changed, 96 insertions(+), 96 deletions(-)
hooks/post-receive
--
postgis.net
More information about the postgis-tickets
mailing list