[SCM] PostGIS branch master updated. 3.4.0rc1-799-gca5a819cf
git at osgeo.org
git at osgeo.org
Sat Nov 25 17:47:55 PST 2023
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 ca5a819cfb2b79cc9aada02eb24368fd15fb690e (commit)
via 4333c01753e3a9fcab3f4cf1d4dc0567e188cd21 (commit)
via 1ce2a87f497e651b85cb35769dff800a286dac00 (commit)
via 47b39be5fac33972a8afb7db8e9f1d5bf8160e94 (commit)
from d333bf1f667b35f683ef59691326d38ae711214e (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 ca5a819cfb2b79cc9aada02eb24368fd15fb690e
Author: Regina Obe <lr at pcorp.us>
Date: Sat Nov 25 20:47:46 2023 -0500
Update pot
diff --git a/doc/po/templates/postgis-manual.pot b/doc/po/templates/postgis-manual.pot
index 511a88823..c50ccc76e 100644
--- a/doc/po/templates/postgis-manual.pot
+++ b/doc/po/templates/postgis-manual.pot
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n"
-"POT-Creation-Date: 2023-11-22 04:19+0000\n"
+"POT-Creation-Date: 2023-11-26 01:47+0000\n"
"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"
@@ -14,6 +14,530 @@ msgstr ""
"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"
@@ -12862,7 +13386,7 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "Example: Projected point at 100,000 meters and bearing 45 degrees"
+msgid "Example: Extends a line 5 units forward and 6 units backward"
msgstr ""
#. Tag: para
@@ -12965,6 +13489,11 @@ msgid ""
"Enhanced: 3.4.0 Allow geometry arguments and two-point form omitting azimuth."
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Example: Projected point at 100,000 meters and bearing 45 degrees"
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid ""
@@ -21890,11 +22419,30 @@ msgstr ""
msgid "Polygon Triangulation"
msgstr ""
+#. Tag: title
+#, no-c-format
+msgid "Same example as ST_Tesselate"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "ST_AsText output"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Original polygon"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Triangulated Polygon"
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid ""
-", <xref linkend=\"ST_ConstrainedDelaunayTriangles\"/>, <xref "
-"linkend=\"ST_Tesselate\"/>"
+", <xref linkend=\"ST_DelaunayTriangles\"/>, <xref linkend=\"ST_Tesselate\"/>"
msgstr ""
#. Tag: refpurpose
@@ -31039,11 +31587,6 @@ msgstr ""
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"
@@ -31063,6 +31606,13 @@ msgid ""
"returns a TIN representation via the process of tessellation using triangles."
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid ""
+"does similar to this function except that it returns a geometry collection "
+"of polygons instead of a TIN and also only works with 2D geometries."
+msgstr ""
+
#. Tag: para
#, no-c-format
msgid "Original Cube"
@@ -31078,11 +31628,6 @@ msgstr ""
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"
@@ -31090,7 +31635,9 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid ", <xref linkend=\"ST_DelaunayTriangles\"/>"
+msgid ""
+", <xref linkend=\"ST_DelaunayTriangles\"/>, <xref "
+"linkend=\"ST_TriangulatePolygon\"/>"
msgstr ""
#. Tag: refpurpose
commit 4333c01753e3a9fcab3f4cf1d4dc0567e188cd21
Author: Regina Obe <lr at pcorp.us>
Date: Sat Nov 25 20:43:27 2023 -0500
Fix what's new and what's changed in this release
in cheatsheets. Closes #5620 for PostGIS 3.5.0dev
diff --git a/doc/xsl/common_cheatsheet.xsl b/doc/xsl/common_cheatsheet.xsl
index 64d85b474..1645cec5d 100644
--- a/doc/xsl/common_cheatsheet.xsl
+++ b/doc/xsl/common_cheatsheet.xsl
@@ -107,10 +107,10 @@
<xsl:value-of select="db:refnamediv/db:refname" />
</a>
</span>
- <xsl:if test="$ref//para[@role=$new_tag and starts-with(./@conformance, $postgis_version)]">
+ <xsl:if test="$ref//db:para[@role=$new_tag and starts-with(@conformance, $postgis_version)]">
<sup>1</sup>
</xsl:if>
- <xsl:if test="$ref//para[@role=$enhanced_tag and starts-with(./@conformance, $postgis_version)]">
+ <xsl:if test="$ref//db:para[@role=$enhanced_tag and starts-with(@conformance, $postgis_version)]">
<sup>2</sup>
</xsl:if>
<xsl:if test="$ref/descendant::*[@conformance=$sqlmm_conformance_tag]">
commit 1ce2a87f497e651b85cb35769dff800a286dac00
Author: Regina Obe <lr at pcorp.us>
Date: Sat Nov 25 20:43:20 2023 -0500
Get rid of useless chapter reference in sfcgal cheatsheet. It's a section not a chapter
diff --git a/doc/xsl/sfcgal_cheatsheet.html.xsl b/doc/xsl/sfcgal_cheatsheet.html.xsl
index bb891878b..701970051 100644
--- a/doc/xsl/sfcgal_cheatsheet.html.xsl
+++ b/doc/xsl/sfcgal_cheatsheet.html.xsl
@@ -18,8 +18,6 @@
<xsl:include href="common_utils.xsl" />
<xsl:include href="common_cheatsheet.xsl" />
- <xsl:variable name="chapter_id" select='"RT_reference"' />
-
<xsl:output method="html" />
<xsl:template match="/">
commit 47b39be5fac33972a8afb7db8e9f1d5bf8160e94
Author: Regina Obe <lr at pcorp.us>
Date: Sat Nov 25 20:10:04 2023 -0500
Fix ST_LineExtend example
closes #5594 for PostGIS 3.5.0dev
diff --git a/doc/reference_editor.xml b/doc/reference_editor.xml
index 6f524ec14..1d03a94e0 100644
--- a/doc/reference_editor.xml
+++ b/doc/reference_editor.xml
@@ -1275,7 +1275,7 @@ SELECT ST_AsText(ST_Multi('POLYGON ((10 30, 30 30, 30 10, 10 10, 10 30))'));
</refsection>
<refsection>
- <title>Example: Projected point at 100,000 meters and bearing 45 degrees </title>
+ <title>Example: Extends a line 5 units forward and 6 units backward</title>
<programlisting>
SELECT ST_AsText(ST_LineExtend('LINESTRING(0 0, 0 10)'::geometry, 5, 6));
-----------------------------------------------------------------------
Summary of changes:
doc/po/templates/postgis-manual.pot | 575 +++++++++++++++++++++++++++++++++++-
doc/reference_editor.xml | 2 +-
doc/xsl/common_cheatsheet.xsl | 4 +-
doc/xsl/sfcgal_cheatsheet.html.xsl | 2 -
4 files changed, 564 insertions(+), 19 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list