[postgis-tickets] [SCM] PostGIS branch master updated. 3.4.0rc1-603-g4aa6f56e3

[git at osgeo.org]

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, master has been updated
       via  4aa6f56e30736a40e77fbce1844ca500e78e51a4 (commit)
      from  063401d10376a3642e7ae7afd7489d8dd03ad73d (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 4aa6f56e30736a40e77fbce1844ca500e78e51a4
Author: Sandro Santilli <strk at kbt.io>
Date:   Wed Sep 20 09:58:32 2023 +0200

    Have the pot file sorted by input filename (normalized)
    
    Also take the chance for sorting XML filenames in the Makefile too

diff --git a/doc/Makefile.in b/doc/Makefile.in
index 5ab84e16f..7c5496c3f 100644
--- a/doc/Makefile.in
+++ b/doc/Makefile.in
@@ -157,22 +157,23 @@ endif
 all: $(BUILD_TARGET)
 
 XML_SOURCES = \
-    extras_address_standardizer.xml \
+	administration.xml \
+	database_tuning.xml \
+	extras_address_standardizer.xml \
 	extras_historytable.xml \
 	extras_tigergeocoder.xml \
 	extras_topology.xml \
 	extras.xml \
 	installation.xml \
-	administration.xml \
-	database_tuning.xml \
 	introduction.xml \
 	performance_tips.xml \
-	postgis.xml \
 	postgis_special.xml \
+	postgis.xml \
 	reference_accessor.xml \
 	reference_bbox.xml \
 	reference_cluster.xml \
 	reference_constructor.xml \
+	reference_coverage.xml \
 	reference_editor.xml \
 	reference_exception.xml \
 	reference_guc.xml \
@@ -180,14 +181,13 @@ XML_SOURCES = \
 	reference_lrs.xml \
 	reference_management.xml \
 	reference_measure.xml \
-	reference_sfcgal.xml \
 	reference_operator.xml \
 	reference_output.xml \
 	reference_overlay.xml \
 	reference_processing.xml \
-	reference_coverage.xml \
 	reference_raster.xml \
 	reference_relationship.xml \
+	reference_sfcgal.xml \
 	reference_srs.xml \
 	reference_trajectory.xml \
 	reference_transaction.xml \
@@ -325,7 +325,7 @@ $(XML_SOURCE_POTS): %.xml.pot: %.xml po/strip_untranslatable.sh
 update-pot: $(XML_UNIFIED_POT)
 
 $(XML_UNIFIED_POT): $(XML_SOURCE_POTS)
-	@$(MSGCAT) --use-first --no-location -o $@.tmp $(XML_SOURCE_POTS)
+	@$(MSGCAT) --sort-by-file --use-first --no-location -o $@.tmp $(XML_SOURCE_POTS)
 	@if test -f $@; then \
     if test -n "$$($(MSGCOMM) --unique $@.tmp $@ | tail -1)"; then \
       $(MSGMERGE) -U $@ $@.tmp || exit 1; \
diff --git a/doc/po/templates/postgis-manual.pot b/doc/po/templates/postgis-manual.pot
index 24c841a6b..39cb649ea 100644
--- a/doc/po/templates/postgis-manual.pot
+++ b/doc/po/templates/postgis-manual.pot
@@ -10,11 +10,751 @@ msgstr ""
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
 "Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
-"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
+#. Tag: chapter
+#, no-c-format
+msgid "&database_tuning;"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "PostGIS Administration"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Configuring raster support"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you enabled raster support you may want to read below how to properly "
+"configure it."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"As of PostGIS 2.1.3, out-of-db rasters and all raster drivers are disabled "
+"by default. In order to re-enable these, you need to set the following "
+"environment variables <varname>POSTGIS_GDAL_ENABLED_DRIVERS</varname> and "
+"<varname>POSTGIS_ENABLE_OUTDB_RASTERS</varname> in the server environment. "
+"For PostGIS 2.2, you can use the more cross-platform approach of setting the "
+"corresponding <xref linkend=\"PostGIS_GUC\"/>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you want to enable offline raster:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Any other setting or no setting at all will disable out of db rasters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"In order to enable all GDAL drivers available in your GDAL install, set this "
+"environment variable as follows"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you want to only enable specific drivers, set your environment variable "
+"as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are on windows, do not quote the driver list"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Setting environment variables varies depending on OS. For PostgreSQL "
+"installed on Ubuntu or Debian via apt-postgresql, the preferred way is to "
+"edit <filename>/etc/postgresql/<replaceable>10</replaceable>/"
+"<replaceable>main</replaceable>/environment</filename> where 10 refers to "
+"version of PostgreSQL and main refers to the cluster."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"On windows, if you are running as a service, you can set via System "
+"variables which for Windows 7 you can get to by right-clicking on Computer-"
+">Properties Advanced System Settings or in explorer navigating to "
+"<varname>Control Panel\\All Control Panel Items\\System</varname>. Then "
+"clicking <emphasis>Advanced System Settings ->Advanced->Environment "
+"Variables</emphasis> and adding new system variables."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"After you set the environment variables, you'll need to restart your "
+"PostgreSQL service for the changes to take effect."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Creating spatial databases"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Spatially enable database using EXTENSION"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you are using PostgreSQL 9.1+ and have compiled and installed the "
+"extensions/postgis modules, you can turn a database into a spatial one using "
+"the EXTENSION mechanism."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Core postgis extension includes geometry, geography, spatial_ref_sys and all "
+"the functions and comments. Raster and topology are packaged as a separate "
+"extension."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Run the following SQL snippet in the database you want to enable spatially:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Spatially enable database without using EXTENSION (discouraged)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This is generally only needed if you cannot or don't want to get PostGIS "
+"installed in the PostgreSQL extension directory (for example during testing, "
+"development or in a restricted environment)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Adding PostGIS objects and function definitions into your database is done "
+"by loading the various sql files located in <filename>[prefix]/share/"
+"contrib</filename> as specified during the build phase."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The core PostGIS objects (geometry and geography types, and their support "
+"functions) are in the <filename>postgis.sql</filename> script. Raster "
+"objects are in the <filename>rtpostgis.sql</filename> script. Topology "
+"objects are in the <filename>topology.sql</filename> script."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"For a complete set of EPSG coordinate system definition identifiers, you can "
+"also load the <filename>spatial_ref_sys.sql</filename> definitions file and "
+"populate the <varname>spatial_ref_sys</varname> table. This will permit you "
+"to perform ST_Transform() operations on geometries."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you wish to add comments to the PostGIS functions, you can find them in "
+"the <filename>postgis_comments.sql</filename> script. Comments can be viewed "
+"by simply typing <command>\\dd [function_name]</command> from a "
+"<command>psql</command> terminal window."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Run the following Shell commands in your terminal:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Upgrading spatial databases"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Upgrading existing spatial databases can be tricky as it requires "
+"replacement or introduction of new PostGIS object definitions."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Unfortunately not all definitions can be easily replaced in a live database, "
+"so sometimes your best bet is a dump/reload process."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"PostGIS provides a SOFT UPGRADE procedure for minor or bugfix releases, and "
+"a HARD UPGRADE procedure for major releases."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Before attempting to upgrade PostGIS, it is always worth to backup your "
+"data. If you use the -Fc flag to pg_dump you will always be able to restore "
+"the dump with a HARD UPGRADE."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Soft upgrade"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you installed your database using extensions, you'll need to upgrade "
+"using the extension model as well. If you installed using the old sql script "
+"way, you are advised to switch your install to extensions because the script "
+"way is no longer supported."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Soft Upgrade 9.1+ using extensions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you originally installed PostGIS with extensions, then you need to "
+"upgrade using extensions as well. Doing a minor upgrade with extensions, is "
+"fairly painless."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you are running PostGIS 3 or above, then you should use the <xref "
+"linkend=\"PostGIS_Extensions_Upgrade\"/> function to upgrade to the latest "
+"version you have installed."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you are running PostGIS 2.5 or lower, then do the following:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you have multiple versions of PostGIS installed, and you don't want to "
+"upgrade to the latest, you can explicitly specify the version as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you get an error notice something like:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Then you'll need to backup your database, create a fresh one as described in "
+"<xref linkend=\"create_new_db_extensions\"/> and then restore your backup on "
+"top of this new database."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you get a notice message like:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Then everything is already up to date and you can safely ignore it. "
+"<emphasis role=\"bold\">UNLESS</emphasis> you're attempting to upgrade from "
+"an development version to the next (which doesn't get a new version number); "
+"in that case you can append \"next\" to the version string, and next time "
+"you'll need to drop the \"next\" suffix again:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you installed PostGIS originally without a version specified, you can "
+"often skip the reinstallation of postgis extension before restoring since "
+"the backup just has <code>CREATE EXTENSION postgis</code> and thus picks up "
+"the newest latest version during restore."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you are upgrading PostGIS extension from a version prior to 3.0.0, you "
+"will have a new extension <emphasis>postgis_raster</emphasis> which you can "
+"safely drop, if you don't need raster support. You can drop as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Soft Upgrade Pre 9.1+ or without extensions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This section applies only to those who installed PostGIS not using "
+"extensions. If you have extensions and try to upgrade with this approach "
+"you'll get messages like:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"NOTE: if you are moving from PostGIS 1.* to PostGIS 2.* or from PostGIS 2.* "
+"prior to r7409, you cannot use this procedure but would rather need to do a "
+"<link linkend=\"hard_upgrade\">HARD UPGRADE</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"After compiling and installing (make install) you should find a set of "
+"<filename>*_upgrade.sql</filename> files in the installation folders. You "
+"can list them all with:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Load them all in turn, starting from <filename>postgis_upgrade.sql</"
+"filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The same procedure applies to raster, topology and sfcgal extensions, with "
+"upgrade files named <filename>rtpostgis_upgrade.sql</filename>, "
+"<filename>topology_upgrade.sql</filename> and <filename>sfcgal_upgrade.sql</"
+"filename> respectively. If you need them:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You are advised to switch to an extension based install by running"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you can't find the <filename>postgis_upgrade.sql</filename> specific for "
+"upgrading your version you are using a version too early for a soft upgrade "
+"and need to do a <link linkend=\"hard_upgrade\">HARD UPGRADE</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The <xref linkend=\"PostGIS_Full_Version\"/> function should inform you "
+"about the need to run this kind of upgrade using a \"procs need upgrade\" "
+"message."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Hard upgrade"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"By HARD UPGRADE we mean full dump/reload of postgis-enabled databases. You "
+"need a HARD UPGRADE when PostGIS objects' internal storage changes or when "
+"SOFT UPGRADE is not possible. The <link linkend=\"release_notes\">Release "
+"Notes</link> appendix reports for each version whether you need a dump/"
+"reload (HARD UPGRADE) to upgrade."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The dump/reload process is assisted by the postgis_restore script which "
+"takes care of skipping from the dump all definitions which belong to PostGIS "
+"(including old ones), allowing you to restore your schemas and data into a "
+"database with PostGIS installed without getting duplicate symbol errors or "
+"bringing forward deprecated objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Supplementary instructions for windows users are available at <link xlink:"
+"href=\"http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade\">Windows Hard "
+"upgrade</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Procedure is as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Create a \"custom-format\" dump of the database you want to upgrade (let's "
+"call it <varname>olddb</varname>) include binary blobs (-b) and verbose (-v) "
+"output. The user can be the owner of the db, need not be postgres super "
+"account."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Do a fresh install of PostGIS in a new database -- we'll refer to this "
+"database as <varname>newdb</varname>. Please refer to <xref "
+"linkend=\"create_new_db\"/> and <xref linkend=\"create_new_db_extensions\"/> "
+"for instructions on how to do this."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The spatial_ref_sys entries found in your dump will be restored, but they "
+"will not override existing ones in spatial_ref_sys. This is to ensure that "
+"fixes in the official set will be properly propagated to restored databases. "
+"If for any reason you really want your own overrides of standard entries "
+"just don't load the spatial_ref_sys.sql file when creating the new db."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If your database is really old or you know you've been using long deprecated "
+"functions in your views and functions, you might need to load "
+"<filename>legacy.sql</filename> for all your functions and views etc. to "
+"properly come back. Only do this if _really_ needed. Consider upgrading your "
+"views and functions before dumping instead, if possible. The deprecated "
+"functions can be later removed by loading <filename>uninstall_legacy.sql</"
+"filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Restore your backup into your fresh <varname>newdb</varname> database using "
+"postgis_restore. Unexpected errors, if any, will be printed to the standard "
+"error stream by psql. Keep a log of those."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Errors may arise in the following cases:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Some of your views or functions make use of deprecated PostGIS objects. In "
+"order to fix this you may try loading <filename>legacy.sql</filename> script "
+"prior to restore or you'll have to restore to a version of PostGIS which "
+"still contains those objects and try a migration again after porting your "
+"code. If the <filename>legacy.sql</filename> way works for you, don't forget "
+"to fix your code to stop using deprecated functions and drop them loading "
+"<filename>uninstall_legacy.sql</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Some custom records of spatial_ref_sys in dump file have an invalid SRID "
+"value. Valid SRID values are bigger than 0 and smaller than 999000. Values "
+"in the 999000.999999 range are reserved for internal use while values > "
+"999999 can't be used at all. All your custom records with invalid SRIDs will "
+"be retained, with those > 999999 moved into the reserved range, but the "
+"spatial_ref_sys table would lose a check constraint guarding for that "
+"invariant to hold and possibly also its primary key ( when multiple invalid "
+"SRIDS get converted to the same reserved SRID value )."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"In order to fix this you should copy your custom SRS to a SRID with a valid "
+"value (maybe in the 910000..910999 range), convert all your tables to the "
+"new srid (see <xref linkend=\"UpdateGeometrySRID\"/>), delete the invalid "
+"entry from spatial_ref_sys and re-construct the check(s) with:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If you are upgrading an old database containing french <link xlink:"
+"href=\"https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national\"> "
+"IGN </link> cartography, you will have probably SRIDs out of range and you "
+"will see, when importing your database, issues like this :"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"In this case, you can try following steps : first throw out completely the "
+"IGN from the sql which is resulting from postgis_restore. So, after having "
+"run :"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "run this command :"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Create then your newdb, activate the required Postgis extensions, and insert "
+"properly the french system IGN with : <link xlink:href=\"https://raw."
+"githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/"
+"Put_IGN_SRS_into_Postgis.sql\"> this script </link> After these operations, "
+"import your data :"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Performance Tuning"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Tuning for PostGIS performance is much like tuning for any PostgreSQL "
+"workload. The only additional consideration is that geometries and rasters "
+"are usually large, so memory-related optimizations generally have more of an "
+"impact on PostGIS than other types of PostgreSQL queries."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"For general details about optimizing PostgreSQL, refer to <link xlink:"
+"href=\"https://wiki.postgresql.org/wiki/"
+"Tuning_Your_PostgreSQL_Server\">Tuning your PostgreSQL Server</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"For PostgreSQL 9.4+ configuration can be set at the server level without "
+"touching <code>postgresql.conf</code> or <code>postgresql.auto.conf</code> "
+"by using the <code>ALTER SYSTEM</code> command."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"In addition to the Postgres settings, PostGIS has some custom settings which "
+"are listed in <xref linkend=\"PostGIS_GUC\"/>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Startup"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "These settings are configured in <code>postgresql.conf</code>:"
+msgstr ""
+
+#. Tag: link
+#, no-c-format
+msgid "constraint_exclusion"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Default: partition"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This is generally used for table partitioning. The default for this is set "
+"to \"partition\" which is ideal for PostgreSQL 8.4 and above since it will "
+"force the planner to only analyze tables for constraint consideration if "
+"they are in an inherited hierarchy and not pay the planner penalty otherwise."
+msgstr ""
+
+#. Tag: link
+#, no-c-format
+msgid "shared_buffers"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Default: ~128MB in PostgreSQL 9.6"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Set to about 25% to 40% of available RAM. On windows you may not be able to "
+"set as high."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<link xlink:href=\"https://www.postgresql.org/docs/current/static/runtime-"
+"config-resource.html#GUC-MAX-WORKER-PROCESSES\">max_worker_processes</link> "
+"This setting is only available for PostgreSQL 9.4+. For PostgreSQL 9.6+ this "
+"setting has additional importance in that it controls the max number of "
+"processes you can have for parallel queries."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Default: 8"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Sets the maximum number of background processes that the system can support. "
+"This parameter can only be set at server start."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Runtime"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<link xlink:href=\"http://www.postgresql.org/docs/current/static/runtime-"
+"config-resource.html#GUC-WORK-MEM\">work_mem</link> - sets the size of "
+"memory used for sort operations and complex queries"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Default: 1-4MB"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Adjust up for large dbs, complex queries, lots of RAM"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Adjust down for many concurrent users or low RAM."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you have lots of RAM and few developers:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<link xlink:href=\"http://www.postgresql.org/docs/current/static/runtime-"
+"config-resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</link> "
+"- the memory size used for VACUUM, CREATE INDEX, etc."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Default: 16-64MB"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Generally too low - ties up I/O, locks objects while swapping memory"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Recommend 32MB to 1GB on production servers w/lots of RAM, but depends on "
+"the # of concurrent users. If you have lots of RAM and few developers:"
+msgstr ""
+
+#. Tag: link
+#, no-c-format
+msgid "max_parallel_workers_per_gather"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This setting is only available for PostgreSQL 9.6+ and will only affect "
+"PostGIS 2.3+, since only PostGIS 2.3+ supports parallel queries. If set to "
+"higher than 0, then some queries such as those involving relation functions "
+"like <code>ST_Intersects</code> can use multiple processes and can run more "
+"than twice as fast when doing so. If you have a lot of processors to spare, "
+"you should change the value of this to as many processors as you have. Also "
+"make sure to bump up <code>max_worker_processes</code> to at least as high "
+"as this number."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Default: 0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Sets the maximum number of workers that can be started by a single "
+"<varname>Gather</varname> node. Parallel workers are taken from the pool of "
+"processes established by <varname>max_worker_processes</varname>. Note that "
+"the requested number of workers may not actually be available at run time. "
+"If this occurs, the plan will run with fewer workers than expected, which "
+"may be inefficient. Setting this value to 0, which is the default, disables "
+"parallel query execution."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "PostGIS Extras"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This chapter documents features found in the extras folder of the PostGIS "
+"source tarballs and source repository. These are not always packaged with "
+"PostGIS binary releases, but are usually PL/pgSQL based or standard shell "
+"scripts that can be run as is."
+msgstr ""
+
+#. Tag: chapter
+#, no-c-format
+msgid "&extras_address_standardizer; &extras_tigergeocoder;"
+msgstr ""
+
 #. Tag: title
 #, no-c-format
 msgid "Address Standardizer"
@@ -5328,25 +6068,6 @@ msgid ""
 "topology (say a spatially-simplified version of the starting topology)."
 msgstr ""
 
-#. Tag: title
-#, no-c-format
-msgid "PostGIS Extras"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This chapter documents features found in the extras folder of the PostGIS "
-"source tarballs and source repository. These are not always packaged with "
-"PostGIS binary releases, but are usually PL/pgSQL based or standard shell "
-"scripts that can be run as is."
-msgstr ""
-
-#. Tag: chapter
-#, no-c-format
-msgid "&extras_address_standardizer; &extras_tigergeocoder;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Installation"
@@ -6472,15 +7193,15 @@ msgstr ""
 #. Tag: para
 #, no-c-format
 msgid ""
-"For each state you want to load data for, generate a state script <xref "
-"linkend=\"Loader_Generate_Script\"/>."
+"DO NOT Generate the state script until you have already loaded the nation "
+"data, because the state script utilizes county list loaded by nation script."
 msgstr ""
 
 #. Tag: para
 #, no-c-format
 msgid ""
-"DO NOT Generate the state script until you have already loaded the nation "
-"data, because the state script utilizes county list loaded by nation script."
+"For each state you want to load data for, generate a state script <xref "
+"linkend=\"Loader_Generate_Script\"/>."
 msgstr ""
 
 #. Tag: para
@@ -6742,728 +7463,6 @@ msgid ""
 "varname> variables have been set correctly."
 msgstr ""
 
-#. Tag: title
-#, no-c-format
-msgid "PostGIS Administration"
-msgstr ""
-
-#. Tag: chapter
-#, no-c-format
-msgid "&database_tuning;"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Configuring raster support"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you enabled raster support you may want to read below how to properly "
-"configure it."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"As of PostGIS 2.1.3, out-of-db rasters and all raster drivers are disabled "
-"by default. In order to re-enable these, you need to set the following "
-"environment variables <varname>POSTGIS_GDAL_ENABLED_DRIVERS</varname> and "
-"<varname>POSTGIS_ENABLE_OUTDB_RASTERS</varname> in the server environment. "
-"For PostGIS 2.2, you can use the more cross-platform approach of setting the "
-"corresponding <xref linkend=\"PostGIS_GUC\"/>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you want to enable offline raster:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Any other setting or no setting at all will disable out of db rasters."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"In order to enable all GDAL drivers available in your GDAL install, set this "
-"environment variable as follows"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you want to only enable specific drivers, set your environment variable "
-"as follows:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you are on windows, do not quote the driver list"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Setting environment variables varies depending on OS. For PostgreSQL "
-"installed on Ubuntu or Debian via apt-postgresql, the preferred way is to "
-"edit <filename>/etc/postgresql/<replaceable>10</replaceable>/"
-"<replaceable>main</replaceable>/environment</filename> where 10 refers to "
-"version of PostgreSQL and main refers to the cluster."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"On windows, if you are running as a service, you can set via System "
-"variables which for Windows 7 you can get to by right-clicking on Computer-"
-">Properties Advanced System Settings or in explorer navigating to "
-"<varname>Control Panel\\All Control Panel Items\\System</varname>. Then "
-"clicking <emphasis>Advanced System Settings ->Advanced->Environment "
-"Variables</emphasis> and adding new system variables."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"After you set the environment variables, you'll need to restart your "
-"PostgreSQL service for the changes to take effect."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Creating spatial databases"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Spatially enable database using EXTENSION"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you are using PostgreSQL 9.1+ and have compiled and installed the "
-"extensions/postgis modules, you can turn a database into a spatial one using "
-"the EXTENSION mechanism."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Core postgis extension includes geometry, geography, spatial_ref_sys and all "
-"the functions and comments. Raster and topology are packaged as a separate "
-"extension."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Run the following SQL snippet in the database you want to enable spatially:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Spatially enable database without using EXTENSION (discouraged)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This is generally only needed if you cannot or don't want to get PostGIS "
-"installed in the PostgreSQL extension directory (for example during testing, "
-"development or in a restricted environment)."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Adding PostGIS objects and function definitions into your database is done "
-"by loading the various sql files located in <filename>[prefix]/share/"
-"contrib</filename> as specified during the build phase."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The core PostGIS objects (geometry and geography types, and their support "
-"functions) are in the <filename>postgis.sql</filename> script. Raster "
-"objects are in the <filename>rtpostgis.sql</filename> script. Topology "
-"objects are in the <filename>topology.sql</filename> script."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"For a complete set of EPSG coordinate system definition identifiers, you can "
-"also load the <filename>spatial_ref_sys.sql</filename> definitions file and "
-"populate the <varname>spatial_ref_sys</varname> table. This will permit you "
-"to perform ST_Transform() operations on geometries."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you wish to add comments to the PostGIS functions, you can find them in "
-"the <filename>postgis_comments.sql</filename> script. Comments can be viewed "
-"by simply typing <command>\\dd [function_name]</command> from a "
-"<command>psql</command> terminal window."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Run the following Shell commands in your terminal:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Upgrading spatial databases"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Upgrading existing spatial databases can be tricky as it requires "
-"replacement or introduction of new PostGIS object definitions."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Unfortunately not all definitions can be easily replaced in a live database, "
-"so sometimes your best bet is a dump/reload process."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"PostGIS provides a SOFT UPGRADE procedure for minor or bugfix releases, and "
-"a HARD UPGRADE procedure for major releases."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Before attempting to upgrade PostGIS, it is always worth to backup your "
-"data. If you use the -Fc flag to pg_dump you will always be able to restore "
-"the dump with a HARD UPGRADE."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Soft upgrade"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you installed your database using extensions, you'll need to upgrade "
-"using the extension model as well. If you installed using the old sql script "
-"way, you are advised to switch your install to extensions because the script "
-"way is no longer supported."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Soft Upgrade 9.1+ using extensions"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you originally installed PostGIS with extensions, then you need to "
-"upgrade using extensions as well. Doing a minor upgrade with extensions, is "
-"fairly painless."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you are running PostGIS 3 or above, then you should use the <xref "
-"linkend=\"PostGIS_Extensions_Upgrade\"/> function to upgrade to the latest "
-"version you have installed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you are running PostGIS 2.5 or lower, then do the following:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you have multiple versions of PostGIS installed, and you don't want to "
-"upgrade to the latest, you can explicitly specify the version as follows:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you get an error notice something like:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Then you'll need to backup your database, create a fresh one as described in "
-"<xref linkend=\"create_new_db_extensions\"/> and then restore your backup on "
-"top of this new database."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you get a notice message like:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Then everything is already up to date and you can safely ignore it. "
-"<emphasis role=\"bold\">UNLESS</emphasis> you're attempting to upgrade from "
-"an development version to the next (which doesn't get a new version number); "
-"in that case you can append \"next\" to the version string, and next time "
-"you'll need to drop the \"next\" suffix again:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you installed PostGIS originally without a version specified, you can "
-"often skip the reinstallation of postgis extension before restoring since "
-"the backup just has <code>CREATE EXTENSION postgis</code> and thus picks up "
-"the newest latest version during restore."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you are upgrading PostGIS extension from a version prior to 3.0.0, you "
-"will have a new extension <emphasis>postgis_raster</emphasis> which you can "
-"safely drop, if you don't need raster support. You can drop as follows:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Soft Upgrade Pre 9.1+ or without extensions"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This section applies only to those who installed PostGIS not using "
-"extensions. If you have extensions and try to upgrade with this approach "
-"you'll get messages like:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"NOTE: if you are moving from PostGIS 1.* to PostGIS 2.* or from PostGIS 2.* "
-"prior to r7409, you cannot use this procedure but would rather need to do a "
-"<link linkend=\"hard_upgrade\">HARD UPGRADE</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"After compiling and installing (make install) you should find a set of "
-"<filename>*_upgrade.sql</filename> files in the installation folders. You "
-"can list them all with:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Load them all in turn, starting from <filename>postgis_upgrade.sql</"
-"filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The same procedure applies to raster, topology and sfcgal extensions, with "
-"upgrade files named <filename>rtpostgis_upgrade.sql</filename>, "
-"<filename>topology_upgrade.sql</filename> and <filename>sfcgal_upgrade.sql</"
-"filename> respectively. If you need them:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You are advised to switch to an extension based install by running"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you can't find the <filename>postgis_upgrade.sql</filename> specific for "
-"upgrading your version you are using a version too early for a soft upgrade "
-"and need to do a <link linkend=\"hard_upgrade\">HARD UPGRADE</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The <xref linkend=\"PostGIS_Full_Version\"/> function should inform you "
-"about the need to run this kind of upgrade using a \"procs need upgrade\" "
-"message."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Hard upgrade"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"By HARD UPGRADE we mean full dump/reload of postgis-enabled databases. You "
-"need a HARD UPGRADE when PostGIS objects' internal storage changes or when "
-"SOFT UPGRADE is not possible. The <link linkend=\"release_notes\">Release "
-"Notes</link> appendix reports for each version whether you need a dump/"
-"reload (HARD UPGRADE) to upgrade."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The dump/reload process is assisted by the postgis_restore script which "
-"takes care of skipping from the dump all definitions which belong to PostGIS "
-"(including old ones), allowing you to restore your schemas and data into a "
-"database with PostGIS installed without getting duplicate symbol errors or "
-"bringing forward deprecated objects."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Supplementary instructions for windows users are available at <link xlink:"
-"href=\"http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade\">Windows Hard "
-"upgrade</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The Procedure is as follows:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Create a \"custom-format\" dump of the database you want to upgrade (let's "
-"call it <varname>olddb</varname>) include binary blobs (-b) and verbose (-v) "
-"output. The user can be the owner of the db, need not be postgres super "
-"account."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Do a fresh install of PostGIS in a new database -- we'll refer to this "
-"database as <varname>newdb</varname>. Please refer to <xref "
-"linkend=\"create_new_db\"/> and <xref linkend=\"create_new_db_extensions\"/> "
-"for instructions on how to do this."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The spatial_ref_sys entries found in your dump will be restored, but they "
-"will not override existing ones in spatial_ref_sys. This is to ensure that "
-"fixes in the official set will be properly propagated to restored databases. "
-"If for any reason you really want your own overrides of standard entries "
-"just don't load the spatial_ref_sys.sql file when creating the new db."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If your database is really old or you know you've been using long deprecated "
-"functions in your views and functions, you might need to load "
-"<filename>legacy.sql</filename> for all your functions and views etc. to "
-"properly come back. Only do this if _really_ needed. Consider upgrading your "
-"views and functions before dumping instead, if possible. The deprecated "
-"functions can be later removed by loading <filename>uninstall_legacy.sql</"
-"filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Restore your backup into your fresh <varname>newdb</varname> database using "
-"postgis_restore. Unexpected errors, if any, will be printed to the standard "
-"error stream by psql. Keep a log of those."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Errors may arise in the following cases:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Some of your views or functions make use of deprecated PostGIS objects. In "
-"order to fix this you may try loading <filename>legacy.sql</filename> script "
-"prior to restore or you'll have to restore to a version of PostGIS which "
-"still contains those objects and try a migration again after porting your "
-"code. If the <filename>legacy.sql</filename> way works for you, don't forget "
-"to fix your code to stop using deprecated functions and drop them loading "
-"<filename>uninstall_legacy.sql</filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Some custom records of spatial_ref_sys in dump file have an invalid SRID "
-"value. Valid SRID values are bigger than 0 and smaller than 999000. Values "
-"in the 999000.999999 range are reserved for internal use while values > "
-"999999 can't be used at all. All your custom records with invalid SRIDs will "
-"be retained, with those > 999999 moved into the reserved range, but the "
-"spatial_ref_sys table would lose a check constraint guarding for that "
-"invariant to hold and possibly also its primary key ( when multiple invalid "
-"SRIDS get converted to the same reserved SRID value )."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"In order to fix this you should copy your custom SRS to a SRID with a valid "
-"value (maybe in the 910000..910999 range), convert all your tables to the "
-"new srid (see <xref linkend=\"UpdateGeometrySRID\"/>), delete the invalid "
-"entry from spatial_ref_sys and re-construct the check(s) with:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If you are upgrading an old database containing french <link xlink:"
-"href=\"https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national\"> "
-"IGN </link> cartography, you will have probably SRIDs out of range and you "
-"will see, when importing your database, issues like this :"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"In this case, you can try following steps : first throw out completely the "
-"IGN from the sql which is resulting from postgis_restore. So, after having "
-"run :"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "run this command :"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Create then your newdb, activate the required Postgis extensions, and insert "
-"properly the french system IGN with : <link xlink:href=\"https://raw."
-"githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/"
-"Put_IGN_SRS_into_Postgis.sql\"> this script </link> After these operations, "
-"import your data :"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Performance Tuning"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Tuning for PostGIS performance is much like tuning for any PostgreSQL "
-"workload. The only additional consideration is that geometries and rasters "
-"are usually large, so memory-related optimizations generally have more of an "
-"impact on PostGIS than other types of PostgreSQL queries."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"For general details about optimizing PostgreSQL, refer to <link xlink:"
-"href=\"https://wiki.postgresql.org/wiki/"
-"Tuning_Your_PostgreSQL_Server\">Tuning your PostgreSQL Server</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"For PostgreSQL 9.4+ configuration can be set at the server level without "
-"touching <code>postgresql.conf</code> or <code>postgresql.auto.conf</code> "
-"by using the <code>ALTER SYSTEM</code> command."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"In addition to the Postgres settings, PostGIS has some custom settings which "
-"are listed in <xref linkend=\"PostGIS_GUC\"/>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Startup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "These settings are configured in <code>postgresql.conf</code>:"
-msgstr ""
-
-#. Tag: link
-#, no-c-format
-msgid "constraint_exclusion"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Default: partition"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This is generally used for table partitioning. The default for this is set "
-"to \"partition\" which is ideal for PostgreSQL 8.4 and above since it will "
-"force the planner to only analyze tables for constraint consideration if "
-"they are in an inherited hierarchy and not pay the planner penalty otherwise."
-msgstr ""
-
-#. Tag: link
-#, no-c-format
-msgid "shared_buffers"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Default: ~128MB in PostgreSQL 9.6"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Set to about 25% to 40% of available RAM. On windows you may not be able to "
-"set as high."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<link xlink:href=\"https://www.postgresql.org/docs/current/static/runtime-"
-"config-resource.html#GUC-MAX-WORKER-PROCESSES\">max_worker_processes</link> "
-"This setting is only available for PostgreSQL 9.4+. For PostgreSQL 9.6+ this "
-"setting has additional importance in that it controls the max number of "
-"processes you can have for parallel queries."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Default: 8"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Sets the maximum number of background processes that the system can support. "
-"This parameter can only be set at server start."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Runtime"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<link xlink:href=\"http://www.postgresql.org/docs/current/static/runtime-"
-"config-resource.html#GUC-WORK-MEM\">work_mem</link> - sets the size of "
-"memory used for sort operations and complex queries"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Default: 1-4MB"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Adjust up for large dbs, complex queries, lots of RAM"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Adjust down for many concurrent users or low RAM."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you have lots of RAM and few developers:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<link xlink:href=\"http://www.postgresql.org/docs/current/static/runtime-"
-"config-resource.html#GUC-MAINTENANCE-WORK-MEM\">maintenance_work_mem</link> "
-"- the memory size used for VACUUM, CREATE INDEX, etc."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Default: 16-64MB"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Generally too low - ties up I/O, locks objects while swapping memory"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Recommend 32MB to 1GB on production servers w/lots of RAM, but depends on "
-"the # of concurrent users. If you have lots of RAM and few developers:"
-msgstr ""
-
-#. Tag: link
-#, no-c-format
-msgid "max_parallel_workers_per_gather"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This setting is only available for PostgreSQL 9.6+ and will only affect "
-"PostGIS 2.3+, since only PostGIS 2.3+ supports parallel queries. If set to "
-"higher than 0, then some queries such as those involving relation functions "
-"like <code>ST_Intersects</code> can use multiple processes and can run more "
-"than twice as fast when doing so. If you have a lot of processors to spare, "
-"you should change the value of this to as many processors as you have. Also "
-"make sure to bump up <code>max_worker_processes</code> to at least as high "
-"as this number."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Default: 0"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Sets the maximum number of workers that can be started by a single "
-"<varname>Gather</varname> node. Parallel workers are taken from the pool of "
-"processes established by <varname>max_worker_processes</varname>. Note that "
-"the requested number of workers may not actually be available at run time. "
-"If this occurs, the plan will run with fewer workers than expected, which "
-"may be inefficient. Setting this value to 0, which is the default, disables "
-"parallel query execution."
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "Introduction"
@@ -8929,6 +8928,11 @@ msgstr ""
 msgid "PostGIS Aggregate Functions"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_aggregates;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -8937,16 +8941,16 @@ msgid ""
 "<code>average</code>."
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_aggregates;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Window Functions"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_window_functions;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -8956,16 +8960,16 @@ msgid ""
 "code> clause."
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_window_functions;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS SQL-MM Compliant Functions"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_sqlmm_functions;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -8973,11 +8977,6 @@ msgid ""
 "standard"
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_sqlmm_functions;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Geography Support Functions"
@@ -9030,6 +9029,11 @@ msgstr ""
 msgid "PostGIS Geometry / Geography / Raster Dump Functions"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_dump_functions;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -9038,11 +9042,6 @@ msgid ""
 "link> or <link linkend=\"geomval\">geomval</link> data type object."
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_dump_functions;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Box Functions"
@@ -9067,6 +9066,11 @@ msgstr ""
 msgid "PostGIS Functions that support 3D"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_3d_functions;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -9074,16 +9078,16 @@ msgid ""
 "Index."
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_3d_functions;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Curved Geometry Support Functions"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_curved_geometry_functions;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -9091,16 +9095,16 @@ msgid ""
 "CURVEPOLYGON, and other curved geometry types"
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_curved_geometry_functions;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Polyhedral Surface Support Functions"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_polyhedral_geometry_functions;"
+msgstr ""
+
 #. Tag: para
 #, no-c-format
 msgid ""
@@ -9108,11 +9112,6 @@ msgid ""
 "POLYHEDRALSURFACE, POLYHEDRALSURFACEM geometries"
 msgstr ""
 
-#. Tag: section
-#, no-c-format
-msgid "&list_polyhedral_geometry_functions;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "PostGIS Function Support Matrix"
@@ -9240,14 +9239,52 @@ msgstr ""
 msgid "&table_body_function_support_matrix;"
 msgstr ""
 
+#. Tag: section
+#, no-c-format
+msgid "&list_new_functions;"
+msgstr ""
+
 #. Tag: title
 #, no-c-format
 msgid "New, Enhanced or changed PostGIS Functions"
 msgstr ""
 
-#. Tag: section
+#. Tag: title
 #, no-c-format
-msgid "&list_new_functions;"
+msgid "PostGIS Reference"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The functions given below are the ones which a user of PostGIS is likely to "
+"need. There are other functions which are required support functions to the "
+"PostGIS objects which are not of use to a general user."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"PostGIS has begun a transition from the existing naming convention to an SQL-"
+"MM-centric convention. As a result, most of the functions that you know and "
+"love have been renamed using the standard spatial type (ST) prefix. Previous "
+"functions are still available, though are not listed in this document where "
+"updated functions are equivalent. The non ST_ functions not listed in this "
+"documentation are deprecated and will be removed in a future release so STOP "
+"USING THEM."
+msgstr ""
+
+#. Tag: chapter
+#, no-c-format
+msgid ""
+"&reference_type; &reference_management; &reference_constructor; "
+"&reference_accessor; &reference_editor; &reference_validation; "
+"&reference_srs; &reference_input; &reference_output; &reference_operator; "
+"&reference_relationship; &reference_measure; &reference_overlay; "
+"&reference_processing; &reference_coverage; &reference_transformation; "
+"&reference_cluster; &reference_bbox; &reference_lrs; &reference_trajectory; "
+"&reference_sfcgal; &reference_transaction; &reference_version; "
+"&reference_guc; &reference_troubleshooting;"
 msgstr ""
 
 #. Tag: title
@@ -12494,6 +12531,186 @@ msgstr ""
 msgid ", <xref linkend=\"ST_Scale\"/>, <xref linkend=\"ST_Translate\"/>"
 msgstr ""
 
+#. Tag: title
+#, no-c-format
+msgid "Coverages"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"These functions operate on sets of polygonal geometry that form \"implicit "
+"coverages\". To form a valid coverage polygons must not overlap, and the "
+"vertices of adjacent edges must match exactly. Coverages are fast to "
+"process, and can be operated on with window functions, which retain the "
+"coverage topology inside the window partition while altering the edges."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Window function that finds locations where polygons fail to form a valid "
+"coverage."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"A window function which checks if the polygons in the window partition form "
+"a valid polygonal coverage. It returns linear indicators showing the "
+"location of invalid edges (if any) in each polygon."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"A set of valid polygons is a valid coverage if the following conditions hold:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">Non-overlapping</emphasis> - polygons do not overlap "
+"(their interiors do not intersect)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">Edge-Matched</emphasis> - vertices along shared "
+"edges are identical"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"As a window function a value is returned for every input polygon. For "
+"polygons which violate one or more of the validity conditions the return "
+"value is a MULTILINESTRING containing the problematic edges. Coverage-valid "
+"polygons return the value NULL. Non-polygonal or empty geometries also "
+"produce NULL values."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The conditions allow a valid coverage to contain holes (gaps between "
+"polygons), as long as the surrounding polygons are edge-matched. However, "
+"very narrow gaps are often undesirable. If the <parameter>tolerance</"
+"parameter> parameter is specified with a non-zero distance, edges forming "
+"narrower gaps will also be returned as invalid."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The polygons being checked for coverage validity must also be valid "
+"geometries. This can be checked with <xref linkend=\"ST_IsValid\"/>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Requires GEOS >= 3.12.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Invalid edges caused by overlap and non-matching vertices"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+", <xref linkend=\"ST_CoverageUnion\"/>, <xref "
+"linkend=\"ST_CoverageSimplify\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Window function that simplifies the edges of a polygonal coverage."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"A window function which simplifies the edges of polygons in a polygonal "
+"coverage. The simplification preserves the coverage topology. This means the "
+"simplified output polygons are consisent along shared edges, and still form "
+"a valid coverage."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The simplification uses a variant of the <link xlink:href=\"https://en."
+"wikipedia.org/wiki/Visvalingam%E2%80%93Whyatt_algorithm\">Visvalingam–Whyatt "
+"algorithm</link>. The <parameter>tolerance</parameter> parameter has units "
+"of distance, and is roughly equal to the square root of triangular areas to "
+"be simplified."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"To simplify only the \"internal\" edges of the coverage (those that are "
+"shared by two polygons) set the <parameter>simplifyBoundary</parameter> "
+"parameter to false."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If the input is not a valid coverage there may be unexpected artifacts in "
+"the output (such as boundary intersections, or separated boundaries which "
+"appeared to be shared). Use <xref linkend=\"ST_CoverageInvalidEdges\"/> to "
+"determine if a coverage is valid."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Input coverage"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Simplified coverage"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Computes the union of a set of polygons forming a coverage by removing "
+"shared edges."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"An aggregate function which unions a set of polygons forming a polygonal "
+"coverage. The result is a polygonal geometry covering the same area as the "
+"coverage. This function produces the same result as <xref "
+"linkend=\"ST_Union\"/>, but uses the coverage structure to compute the union "
+"much faster."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If the input is not a valid coverage there may be unexpected artifacts in "
+"the output (such as unmerged or overlapping polygons). Use <xref "
+"linkend=\"ST_CoverageInvalidEdges\"/> to determine if a coverage is valid."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Availability: 3.4.0 - requires GEOS >= 3.8.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Union result"
+msgstr ""
+
 #. Tag: title
 #, no-c-format
 msgid "Geometry Editors"
@@ -17254,619 +17471,6 @@ msgid ""
 "<xref linkend=\"ST_ShortestLine\"/>, <xref linkend=\"ST_3DMaxDistance\"/>"
 msgstr ""
 
-#. Tag: title
-#, no-c-format
-msgid "SFCGAL Functions"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"SFCGAL is a C++ wrapper library around CGAL that provides advanced 2D and 3D "
-"spatial functions. For robustness, geometry coordinates have an exact "
-"rational number representation."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Installation instructions for the library can be found on the SFCGAL home "
-"page (<link xlink:href=\"http://www.sfcgal.org\">http://www.sfcgal.org</"
-"link>). To enable the functions use <code>create extension postgis_sfcgal</"
-"code>."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "<refpurpose>Returns the version of SFCGAL in use</refpurpose>"
-msgstr ""
-
-#. Tag: funcdef
-#, no-c-format
-msgid "text <function>postgis_sfcgal_version</function>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<para>Returns the version of SFCGAL in use</para>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&sfcgal_required;"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"<refpurpose>Returns the full version of SFCGAL in use including CGAL and "
-"Boost versions</refpurpose>"
-msgstr ""
-
-#. Tag: funcdef
-#, no-c-format
-msgid "text <function>postgis_sfcgal_full_version</function>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<para>Returns the full version of SFCGAL in use including CGAL and Boost "
-"versions</para>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Computes area of 3D surface geometries. Will return 0 for solids."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&sqlmm_compliant; SQL-MM IEC 13249-3: 8.1, 10.5"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Note: By default a PolyhedralSurface built from WKT is a surface geometry, "
-"not solid. It therefore has surface area. Once converted to a solid, no area."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-", <xref linkend=\"ST_MakeSolid\"/>, <xref linkend=\"ST_IsSolid\"/>, <xref "
-"linkend=\"ST_Area\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Computes the 3D convex hull of a geometry."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original geometry overlaid with 3D convex hull"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ", <xref linkend=\"ST_AsX3D\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Perform 3D intersection"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Return a geometry that is the shared portion between geom1 and geom2."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"3D images were generated using PostGIS <xref linkend=\"ST_AsX3D\"/> and "
-"rendering in HTML using <link xlink:href=\"http://www.x3dom.org\">X3Dom HTML "
-"Javascript rendering library</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original 3D geometries overlaid. geom2 is shown semi-transparent"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Intersection of geom1 and geom2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "3D linestrings and polygons"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Cube (closed Polyhedral Surface) and Polygon Z"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Intersection of 2 solids that result in volumetric intersection is also a "
-"solid (ST_Dimension returns 3)"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Perform 3D difference"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Returns that part of geom1 that is not part of geom2."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Original 3D geometries overlaid. geom2 is the part that will be removed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "What's left after removing geom2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-", <xref linkend=\"ST_AsX3D\"/>, <xref linkend=\"ST_3DIntersection\"/> <xref "
-"linkend=\"ST_3DUnion\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Perform 3D union."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Availability: 3.3.0 aggregate variant was added"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Aggregate variant:</emphasis> returns a geometry "
-"that is the 3D union of a rowset of geometries. The ST_3DUnion() function is "
-"an \"aggregate\" function in the terminology of PostgreSQL. That means that "
-"it operates on rows of data, in the same way the SUM() and AVG() functions "
-"do and like most aggregates, it also ignores NULL geometries."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original 3D geometries overlaid. geom2 is the one with transparency."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Union of geom1 and geom2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-", <xref linkend=\"ST_AsX3D\"/>, <xref linkend=\"ST_3DIntersection\"/> <xref "
-"linkend=\"ST_3DDifference\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Computes an Alpha-shape enclosing a geometry"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Computes the <link xlink:href=\"https://en.wikipedia.org/wiki/"
-"Alpha_shape\">Alpha-Shape</link> of the points in a geometry. An alpha-shape "
-"is a (usually) concave polygonal geometry which contains all the vertices of "
-"the input, and whose vertices are a subset of the input vertices. An alpha-"
-"shape provides a closer fit to the shape of the input than the shape "
-"produced by the <link linkend=\"ST_ConvexHull\">convex hull</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The \"closeness of fit\" is controlled by the <varname>alpha</varname> "
-"parameter, which can have values from 0 to infinity. Smaller alpha values "
-"produce more concave results. Alpha values greater than some data-dependent "
-"value produce the convex hull of the input."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Following the CGAL implementation, the alpha value is the <emphasis>square</"
-"emphasis> of the radius of the disc used in the Alpha-Shape algorithm to "
-"\"erode\" the Delaunay Triangulation of the input points. See <link xlink:"
-"href=\"https://doc.cgal.org/latest/Alpha_shapes_2/index."
-"html#Chapter_2D_Alpha_Shapes\">CGAL Alpha-Shapes</link> for more "
-"information. This is different from the original definition of alpha-shapes, "
-"which defines alpha as the radius of the eroding disc."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The computed shape does not contain holes unless the optional "
-"<varname>allow_holes</varname> argument is specified as true."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This function effectively computes a concave hull of a geometry in a similar "
-"way to <xref linkend=\"ST_ConcaveHull\"/>, but uses CGAL and a different "
-"algorithm."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Availability: 3.3.0 - requires SFCGAL >= 1.4.1."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Alpha-shape of a MultiPoint (same example As <xref "
-"linkend=\"ST_OptimalAlphaShape\"/>)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Alpha-shape of a MultiPoint, allowing holes (same example as <xref "
-"linkend=\"ST_OptimalAlphaShape\"/>)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Alpha-shape of a MultiPoint, allowing holes (same example as <xref "
-"linkend=\"ST_ConcaveHull\"/>)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ", <xref linkend=\"ST_OptimalAlphaShape\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Compute the approximate medial axis of an areal geometry."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Return an approximate medial axis for the areal input based on its straight "
-"skeleton. Uses an SFCGAL specific API when built against a capable version "
-"(1.2.0+). Otherwise the function is just a wrapper around "
-"ST_StraightSkeleton (slower case)."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "A polygon and its approximate medial axis"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Return a constrained Delaunay triangulation around the given input geometry."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Return a <link xlink:href=\"https://en.wikipedia.org/wiki/"
-"Constrained_Delaunay_triangulation\">Constrained Delaunay triangulation</"
-"link> around the vertices of the input geometry. Output is a TIN."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "ST_ConstrainedDelaunayTriangles of 2 polygons"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "of 2 polygons. Triangle edges cross polygon boundaries."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-", <xref linkend=\"ST_TriangulatePolygon\"/>, <xref linkend=\"ST_Tesselate\"/"
-">, <xref linkend=\"ST_ConcaveHull\"/>, <xref linkend=\"ST_Dump\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Extrude a surface to a related volume"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original octagon formed from buffering point"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Hexagon extruded 30 units along Z produces a PolyhedralSurfaceZ"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original linestring"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "LineString Extruded along Z produces a PolyhedralSurfaceZ"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Force LHR orientation"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Check if a surface is or not planar"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Availability: 2.2.0: This was documented in 2.1.0 but got accidentally left "
-"out in 2.1 release."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Test if the geometry is a solid. No validity check is performed."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Cast the geometry into a solid. No check is performed. To obtain a valid "
-"solid, the input geometry must be a closed Polyhedral Surface or a closed "
-"TIN."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Performs Minkowski sum"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"This function performs a 2D minkowski sum of a point, line or polygon with a "
-"polygon."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"A minkowski sum of two geometries A and B is the set of all points that are "
-"the sum of any point in A and B. Minkowski sums are often used in motion "
-"planning and computer-aided design. More details on <link xlink:"
-"href=\"https://en.wikipedia.org/wiki/Minkowski_addition\">Wikipedia "
-"Minkowski addition</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The first parameter can be any 2D geometry (point, linestring, polygon). If "
-"a 3D geometry is passed, it will be converted to 2D by forcing Z to 0, "
-"leading to possible cases of invalidity. The second parameter must be a 2D "
-"polygon."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Implementation utilizes <link xlink:href=\"http://doc.cgal.org/latest/"
-"Minkowski_sum_2/\">CGAL 2D Minkowskisum</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Minkowski Sum of Linestring and circle polygon where Linestring cuts thru "
-"the circle"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Before Summing"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "After summing"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Minkowski Sum of a polygon and multipoint"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"After summing: polygon is duplicated and translated to position of points"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Computes an Alpha-shape enclosing a geometry using an \"optimal\" alpha "
-"value."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Computes the \"optimal\" alpha-shape of the points in a geometry. The alpha-"
-"shape is computed using a value of α chosen so that:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"the number of polygon elements is equal to or smaller than "
-"<varname>nb_components</varname> (which defaults to 1)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "all input points are contained in the shape"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The result will not contain holes unless the optional <varname>allow_holes</"
-"varname> argument is specified as true."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Optimal alpha-shape of a MultiPoint (same example as <xref "
-"linkend=\"ST_AlphaShape\"/>)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Optimal alpha-shape of a MultiPoint, allowing holes (same example as <xref "
-"linkend=\"ST_AlphaShape\"/>)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ", <xref linkend=\"ST_AlphaShape\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Determine surface orientation"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The function only applies to polygons. It returns -1 if the polygon is "
-"counterclockwise oriented and 1 if the polygon is clockwise oriented."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Compute a straight skeleton from a geometry"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original polygon"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Straight Skeleton of polygon"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Perform surface Tesselation of a polygon or polyhedralsurface and returns as "
-"a TIN or collection of TINS"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Takes as input a surface such a MULTI(POLYGON) or POLYHEDRALSURFACE and "
-"returns a TIN representation via the process of tessellation using triangles."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Original Cube"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "ST_AsText output:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Tesselated Cube with triangles colored"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "ST_AsText output"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Tesselated Polygon"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ", <xref linkend=\"ST_DelaunayTriangles\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Computes the volume of a 3D solid. If applied to surface (even closed) "
-"geometries will return 0."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "&sqlmm_compliant; SQL-MM IEC 13249-3: 9.1 (same as ST_3DVolume)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"When closed surfaces are created with WKT, they are treated as areal rather "
-"than solid. To make them solid, you need to use <xref "
-"linkend=\"ST_MakeSolid\"/>. Areal geometries have no volume. Here is an "
-"example to demonstrate."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ", <xref linkend=\"ST_MakeSolid\"/>, <xref linkend=\"ST_IsSolid\"/>"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "Operators"
@@ -22833,186 +22437,6 @@ msgstr ""
 msgid ", <xref linkend=\"ST_VoronoiLines\"/>"
 msgstr ""
 
-#. Tag: title
-#, no-c-format
-msgid "Coverages"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"These functions operate on sets of polygonal geometry that form \"implicit "
-"coverages\". To form a valid coverage polygons must not overlap, and the "
-"vertices of adjacent edges must match exactly. Coverages are fast to "
-"process, and can be operated on with window functions, which retain the "
-"coverage topology inside the window partition while altering the edges."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Window function that finds locations where polygons fail to form a valid "
-"coverage."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"A window function which checks if the polygons in the window partition form "
-"a valid polygonal coverage. It returns linear indicators showing the "
-"location of invalid edges (if any) in each polygon."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"A set of valid polygons is a valid coverage if the following conditions hold:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Non-overlapping</emphasis> - polygons do not overlap "
-"(their interiors do not intersect)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<emphasis role=\"bold\">Edge-Matched</emphasis> - vertices along shared "
-"edges are identical"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"As a window function a value is returned for every input polygon. For "
-"polygons which violate one or more of the validity conditions the return "
-"value is a MULTILINESTRING containing the problematic edges. Coverage-valid "
-"polygons return the value NULL. Non-polygonal or empty geometries also "
-"produce NULL values."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The conditions allow a valid coverage to contain holes (gaps between "
-"polygons), as long as the surrounding polygons are edge-matched. However, "
-"very narrow gaps are often undesirable. If the <parameter>tolerance</"
-"parameter> parameter is specified with a non-zero distance, edges forming "
-"narrower gaps will also be returned as invalid."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The polygons being checked for coverage validity must also be valid "
-"geometries. This can be checked with <xref linkend=\"ST_IsValid\"/>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Requires GEOS >= 3.12.0"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Invalid edges caused by overlap and non-matching vertices"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-", <xref linkend=\"ST_CoverageUnion\"/>, <xref "
-"linkend=\"ST_CoverageSimplify\"/>"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid "Window function that simplifies the edges of a polygonal coverage."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"A window function which simplifies the edges of polygons in a polygonal "
-"coverage. The simplification preserves the coverage topology. This means the "
-"simplified output polygons are consisent along shared edges, and still form "
-"a valid coverage."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The simplification uses a variant of the <link xlink:href=\"https://en."
-"wikipedia.org/wiki/Visvalingam%E2%80%93Whyatt_algorithm\">Visvalingam–Whyatt "
-"algorithm</link>. The <parameter>tolerance</parameter> parameter has units "
-"of distance, and is roughly equal to the square root of triangular areas to "
-"be simplified."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"To simplify only the \"internal\" edges of the coverage (those that are "
-"shared by two polygons) set the <parameter>simplifyBoundary</parameter> "
-"parameter to false."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If the input is not a valid coverage there may be unexpected artifacts in "
-"the output (such as boundary intersections, or separated boundaries which "
-"appeared to be shared). Use <xref linkend=\"ST_CoverageInvalidEdges\"/> to "
-"determine if a coverage is valid."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Input coverage"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Simplified coverage"
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Computes the union of a set of polygons forming a coverage by removing "
-"shared edges."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"An aggregate function which unions a set of polygons forming a polygonal "
-"coverage. The result is a polygonal geometry covering the same area as the "
-"coverage. This function produces the same result as <xref "
-"linkend=\"ST_Union\"/>, but uses the coverage structure to compute the union "
-"much faster."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If the input is not a valid coverage there may be unexpected artifacts in "
-"the output (such as unmerged or overlapping polygons). Use <xref "
-"linkend=\"ST_CoverageInvalidEdges\"/> to determine if a coverage is valid."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Availability: 3.4.0 - requires GEOS >= 3.8.0"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Union result"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "Raster Reference"
@@ -24432,12 +23856,12 @@ msgstr ""
 
 #. Tag: para
 #, no-c-format
-msgid "Pixel Width: Pixel size in the i direction"
+msgid "Pixel Height: Pixel size in the j direction"
 msgstr ""
 
 #. Tag: para
 #, no-c-format
-msgid "Pixel Height: Pixel size in the j direction"
+msgid "Pixel Width: Pixel size in the i direction"
 msgstr ""
 
 #. Tag: refpurpose
@@ -31490,6 +30914,619 @@ msgstr ""
 msgid "Changed: 2.2.0 In prior versions this was called ST_Point_Inside_Circle"
 msgstr ""
 
+#. Tag: title
+#, no-c-format
+msgid "SFCGAL Functions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"SFCGAL is a C++ wrapper library around CGAL that provides advanced 2D and 3D "
+"spatial functions. For robustness, geometry coordinates have an exact "
+"rational number representation."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Installation instructions for the library can be found on the SFCGAL home "
+"page (<link xlink:href=\"http://www.sfcgal.org\">http://www.sfcgal.org</"
+"link>). To enable the functions use <code>create extension postgis_sfcgal</"
+"code>."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "<refpurpose>Returns the version of SFCGAL in use</refpurpose>"
+msgstr ""
+
+#. Tag: funcdef
+#, no-c-format
+msgid "text <function>postgis_sfcgal_version</function>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<para>Returns the version of SFCGAL in use</para>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "&sfcgal_required;"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"<refpurpose>Returns the full version of SFCGAL in use including CGAL and "
+"Boost versions</refpurpose>"
+msgstr ""
+
+#. Tag: funcdef
+#, no-c-format
+msgid "text <function>postgis_sfcgal_full_version</function>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<para>Returns the full version of SFCGAL in use including CGAL and Boost "
+"versions</para>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Computes area of 3D surface geometries. Will return 0 for solids."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "&sqlmm_compliant; SQL-MM IEC 13249-3: 8.1, 10.5"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Note: By default a PolyhedralSurface built from WKT is a surface geometry, "
+"not solid. It therefore has surface area. Once converted to a solid, no area."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+", <xref linkend=\"ST_MakeSolid\"/>, <xref linkend=\"ST_IsSolid\"/>, <xref "
+"linkend=\"ST_Area\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Computes the 3D convex hull of a geometry."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original geometry overlaid with 3D convex hull"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ", <xref linkend=\"ST_AsX3D\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Perform 3D intersection"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return a geometry that is the shared portion between geom1 and geom2."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"3D images were generated using PostGIS <xref linkend=\"ST_AsX3D\"/> and "
+"rendering in HTML using <link xlink:href=\"http://www.x3dom.org\">X3Dom HTML "
+"Javascript rendering library</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original 3D geometries overlaid. geom2 is shown semi-transparent"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Intersection of geom1 and geom2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "3D linestrings and polygons"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Cube (closed Polyhedral Surface) and Polygon Z"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Intersection of 2 solids that result in volumetric intersection is also a "
+"solid (ST_Dimension returns 3)"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Perform 3D difference"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Returns that part of geom1 that is not part of geom2."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Original 3D geometries overlaid. geom2 is the part that will be removed."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "What's left after removing geom2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+", <xref linkend=\"ST_AsX3D\"/>, <xref linkend=\"ST_3DIntersection\"/> <xref "
+"linkend=\"ST_3DUnion\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Perform 3D union."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Availability: 3.3.0 aggregate variant was added"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<emphasis role=\"bold\">Aggregate variant:</emphasis> returns a geometry "
+"that is the 3D union of a rowset of geometries. The ST_3DUnion() function is "
+"an \"aggregate\" function in the terminology of PostgreSQL. That means that "
+"it operates on rows of data, in the same way the SUM() and AVG() functions "
+"do and like most aggregates, it also ignores NULL geometries."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original 3D geometries overlaid. geom2 is the one with transparency."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Union of geom1 and geom2"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+", <xref linkend=\"ST_AsX3D\"/>, <xref linkend=\"ST_3DIntersection\"/> <xref "
+"linkend=\"ST_3DDifference\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Computes an Alpha-shape enclosing a geometry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Computes the <link xlink:href=\"https://en.wikipedia.org/wiki/"
+"Alpha_shape\">Alpha-Shape</link> of the points in a geometry. An alpha-shape "
+"is a (usually) concave polygonal geometry which contains all the vertices of "
+"the input, and whose vertices are a subset of the input vertices. An alpha-"
+"shape provides a closer fit to the shape of the input than the shape "
+"produced by the <link linkend=\"ST_ConvexHull\">convex hull</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The \"closeness of fit\" is controlled by the <varname>alpha</varname> "
+"parameter, which can have values from 0 to infinity. Smaller alpha values "
+"produce more concave results. Alpha values greater than some data-dependent "
+"value produce the convex hull of the input."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Following the CGAL implementation, the alpha value is the <emphasis>square</"
+"emphasis> of the radius of the disc used in the Alpha-Shape algorithm to "
+"\"erode\" the Delaunay Triangulation of the input points. See <link xlink:"
+"href=\"https://doc.cgal.org/latest/Alpha_shapes_2/index."
+"html#Chapter_2D_Alpha_Shapes\">CGAL Alpha-Shapes</link> for more "
+"information. This is different from the original definition of alpha-shapes, "
+"which defines alpha as the radius of the eroding disc."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The computed shape does not contain holes unless the optional "
+"<varname>allow_holes</varname> argument is specified as true."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This function effectively computes a concave hull of a geometry in a similar "
+"way to <xref linkend=\"ST_ConcaveHull\"/>, but uses CGAL and a different "
+"algorithm."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Availability: 3.3.0 - requires SFCGAL >= 1.4.1."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Alpha-shape of a MultiPoint (same example As <xref "
+"linkend=\"ST_OptimalAlphaShape\"/>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Alpha-shape of a MultiPoint, allowing holes (same example as <xref "
+"linkend=\"ST_OptimalAlphaShape\"/>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Alpha-shape of a MultiPoint, allowing holes (same example as <xref "
+"linkend=\"ST_ConcaveHull\"/>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ", <xref linkend=\"ST_OptimalAlphaShape\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Compute the approximate medial axis of an areal geometry."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Return an approximate medial axis for the areal input based on its straight "
+"skeleton. Uses an SFCGAL specific API when built against a capable version "
+"(1.2.0+). Otherwise the function is just a wrapper around "
+"ST_StraightSkeleton (slower case)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A polygon and its approximate medial axis"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Return a constrained Delaunay triangulation around the given input geometry."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Return a <link xlink:href=\"https://en.wikipedia.org/wiki/"
+"Constrained_Delaunay_triangulation\">Constrained Delaunay triangulation</"
+"link> around the vertices of the input geometry. Output is a TIN."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ST_ConstrainedDelaunayTriangles of 2 polygons"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "of 2 polygons. Triangle edges cross polygon boundaries."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+", <xref linkend=\"ST_TriangulatePolygon\"/>, <xref linkend=\"ST_Tesselate\"/"
+">, <xref linkend=\"ST_ConcaveHull\"/>, <xref linkend=\"ST_Dump\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Extrude a surface to a related volume"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original octagon formed from buffering point"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Hexagon extruded 30 units along Z produces a PolyhedralSurfaceZ"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original linestring"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "LineString Extruded along Z produces a PolyhedralSurfaceZ"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Force LHR orientation"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Check if a surface is or not planar"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Availability: 2.2.0: This was documented in 2.1.0 but got accidentally left "
+"out in 2.1 release."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Test if the geometry is a solid. No validity check is performed."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Cast the geometry into a solid. No check is performed. To obtain a valid "
+"solid, the input geometry must be a closed Polyhedral Surface or a closed "
+"TIN."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Performs Minkowski sum"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"This function performs a 2D minkowski sum of a point, line or polygon with a "
+"polygon."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"A minkowski sum of two geometries A and B is the set of all points that are "
+"the sum of any point in A and B. Minkowski sums are often used in motion "
+"planning and computer-aided design. More details on <link xlink:"
+"href=\"https://en.wikipedia.org/wiki/Minkowski_addition\">Wikipedia "
+"Minkowski addition</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The first parameter can be any 2D geometry (point, linestring, polygon). If "
+"a 3D geometry is passed, it will be converted to 2D by forcing Z to 0, "
+"leading to possible cases of invalidity. The second parameter must be a 2D "
+"polygon."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Implementation utilizes <link xlink:href=\"http://doc.cgal.org/latest/"
+"Minkowski_sum_2/\">CGAL 2D Minkowskisum</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Minkowski Sum of Linestring and circle polygon where Linestring cuts thru "
+"the circle"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Before Summing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "After summing"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Minkowski Sum of a polygon and multipoint"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"After summing: polygon is duplicated and translated to position of points"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Computes an Alpha-shape enclosing a geometry using an \"optimal\" alpha "
+"value."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Computes the \"optimal\" alpha-shape of the points in a geometry. The alpha-"
+"shape is computed using a value of α chosen so that:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"the number of polygon elements is equal to or smaller than "
+"<varname>nb_components</varname> (which defaults to 1)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "all input points are contained in the shape"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The result will not contain holes unless the optional <varname>allow_holes</"
+"varname> argument is specified as true."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Optimal alpha-shape of a MultiPoint (same example as <xref "
+"linkend=\"ST_AlphaShape\"/>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Optimal alpha-shape of a MultiPoint, allowing holes (same example as <xref "
+"linkend=\"ST_AlphaShape\"/>)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ", <xref linkend=\"ST_AlphaShape\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Determine surface orientation"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The function only applies to polygons. It returns -1 if the polygon is "
+"counterclockwise oriented and 1 if the polygon is clockwise oriented."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid "Compute a straight skeleton from a geometry"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original polygon"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Straight Skeleton of polygon"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Perform surface Tesselation of a polygon or polyhedralsurface and returns as "
+"a TIN or collection of TINS"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Takes as input a surface such a MULTI(POLYGON) or POLYHEDRALSURFACE and "
+"returns a TIN representation via the process of tessellation using triangles."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original Cube"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ST_AsText output:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Tesselated Cube with triangles colored"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ST_AsText output"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Tesselated Polygon"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ", <xref linkend=\"ST_DelaunayTriangles\"/>"
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Computes the volume of a 3D solid. If applied to surface (even closed) "
+"geometries will return 0."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "&sqlmm_compliant; SQL-MM IEC 13249-3: 9.1 (same as ST_3DVolume)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"When closed surfaces are created with WKT, they are treated as areal rather "
+"than solid. To make them solid, you need to use <xref "
+"linkend=\"ST_MakeSolid\"/>. Areal geometries have no volume. Here is an "
+"example to demonstrate."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ", <xref linkend=\"ST_MakeSolid\"/>, <xref linkend=\"ST_IsSolid\"/>"
+msgstr ""
+
 #. Tag: title
 #, no-c-format
 msgid "Spatial Reference System Functions"
@@ -33384,44 +33421,6 @@ msgid ""
 ">, <xref linkend=\"PostGIS_PROJ_Version\"/>"
 msgstr ""
 
-#. Tag: title
-#, no-c-format
-msgid "PostGIS Reference"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The functions given below are the ones which a user of PostGIS is likely to "
-"need. There are other functions which are required support functions to the "
-"PostGIS objects which are not of use to a general user."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"PostGIS has begun a transition from the existing naming convention to an SQL-"
-"MM-centric convention. As a result, most of the functions that you know and "
-"love have been renamed using the standard spatial type (ST) prefix. Previous "
-"functions are still available, though are not listed in this document where "
-"updated functions are equivalent. The non ST_ functions not listed in this "
-"documentation are deprecated and will be removed in a future release so STOP "
-"USING THEM."
-msgstr ""
-
-#. Tag: chapter
-#, no-c-format
-msgid ""
-"&reference_type; &reference_management; &reference_constructor; "
-"&reference_accessor; &reference_editor; &reference_validation; "
-"&reference_srs; &reference_input; &reference_output; &reference_operator; "
-"&reference_relationship; &reference_measure; &reference_overlay; "
-"&reference_processing; &reference_coverage; &reference_transformation; "
-"&reference_cluster; &reference_bbox; &reference_lrs; &reference_trajectory; "
-"&reference_sfcgal; &reference_transaction; &reference_version; "
-"&reference_guc; &reference_troubleshooting;"
-msgstr ""
-
 #. Tag: title
 #, no-c-format
 msgid "Appendix"

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

Summary of changes:
 doc/Makefile.in                     |    14 +-
 doc/po/templates/postgis-manual.pot | 18543 +++++++++++++++++-----------------
 2 files changed, 9278 insertions(+), 9279 deletions(-)


hooks/post-receive
-- 
PostGIS