Source strings

5,579 Strings
100%
Browse Translate
99,720 Words
100%
713,033 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
5,579 99,720 713,033
All strings Browse Translate Zen
5,579 99,720 713,033
Read-only strings Browse Translate Zen
2,052 41,987 301,286
Strings with any failing checks Browse Translate Zen
11 312 2,185
Failing check: Unpluralised Browse Translate Zen
7 137 1,043
Failing check: Ellipsis Browse Translate Zen
2,021 41,105 294,903
Failing check: Multiple failing checks Browse Translate Zen
23 668 5,116
Failing check: Long untranslated Browse Translate Zen
11 145 1,277
Strings with comments Browse Translate Zen

Summary

Project website postgis.net
Project maintainers4 User avatar robeUser avatar strkUser avatar cvvergaraUser avatar komzpa
Project reviewers13 User avatar robeUser avatar strkUser avatar cvvergaraUser avatar dkastlUser avatar komzpaUser avatar astrid_emdeUser avatar jsanzUser avatar andischiUser avatar yoichiUser avatar jefUser avatar thayerayUser avatar yellow73User avatar jonnyforest
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://git.osgeo.org/gitea/postgis/postgis.git
Repository branch master
Last remote commit Add CI status dashboard generator 09f06cab
Darafei Praliaskouski authored 06/26/2026
Last commit in Weblate Add CI status dashboard generator 09f06cab
Darafei Praliaskouski authored 06/26/2026
Weblate repository https://weblate.osgeo.org/git/postgis/postgis-manual/
File mask doc/po/*/postgis-manual.po
Translation file Download doc/po/templates/postgis-manual.pot
Last change June 25, 2026, 2:35 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
06/25/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 5,579 99,720 713,033
Translated 100% 5,579 100% 99,720 100% 713,033
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 5,579 100% 99,720 100% 713,033
Failing checks 36% 2,052 42% 41,987 42% 301,286
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

82 changes 0 changes 44 changes 74 changes 47 changes 29 changes 23 changes 0 changes 0 changes 0 changes 68 changes 146 changes 7 changes 1 change 11 changes 0 changes 1 change 0 changes 0 changes 15 changes 20 changes 0 changes 55 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

99,720
Hosted words
5,579
Hosted strings
100%
Translated
4
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
—
Translated
+100%
+100%
Contributors
—
User avatar None

Resource updated
The “doc/po/templates/postgis-manual.pot” file was changed. 06/25/2026
User avatar None

String added in the repository
Returns a geometry representing the portions of geometries A and B that do not intersect. This is equivalent to <code>ST_Union(A,B) - ST_Intersection(A,B)</code>. It is called a symmetric difference because <code>ST_SymDifference(A,B) = ST_SymDifference(B,A)</code>.
Returns a geometry representing the portions of geometries A and B that do not intersect. This is equivalent to <code>ST_Union(A,B) - ST_Intersection(A,B)</code>. It is called a symmetric difference because <code>ST_SymDifference(A,B) = ST_SymDifference(B,A)</code>.
06/25/2026
User avatar komzpa

Resource updated
Parsing of the “doc/po/templates/postgis-manual.pot” file was enforced. 06/18/2026
User avatar None

Resource updated
The “doc/po/templates/postgis-manual.pot” file was changed. 06/12/2026
User avatar None

String added in the repository
If the optional <code>gridSize</code> parameter is given (GEOS-3.9.0 or higher required), all result vertices are guaranteed to fall on a snap-rounded grid of the specified size. Note that operations performed on a grid may contain small artifacts produced during grid alignment, see <xref linkend="ST_ReducePrecision"/>.
If the optional <code>gridSize</code> parameter is given (GEOS-3.9.0 or higher required), all result vertices are guaranteed to fall on a snap-rounded grid of the specified size. Note that operations performed on a grid may contain small artifacts produced during grid alignment, see <xref linkend="ST_ReducePrecision"/>.
06/12/2026
User avatar None

String added in the repository
For example, consider a linear dataset representing a road network. It may be required to identify all road segments that cross each other, not at a point, but in a line (perhaps to validate a business rule such as ensuring that no two different roads share a common segment). In this case <xref linkend="ST_Crosses"/> does not provide the necessary spatial filter, since for linear features it returns <varname>true</varname> only where they cross at a point.
For example, consider a linear dataset representing a road network. It may be required to identify all road segments that cross each other, not at a point, but in a line (perhaps to validate a business rule such as ensuring that no two different roads share a common segment). In this case <xref linkend="ST_Crosses"/> does not provide the necessary spatial filter, since for linear features it returns <varname>true</varname> only where they cross at a point.
06/12/2026
User avatar None

String added in the repository
The coordinate dimension (2, 3 or 4) of the column. The coordinate dimension is at least 2, representing X and Y coordinates.
The coordinate dimension (2, 3 or 4) of the column. The coordinate dimension is at least 2, representing X and Y coordinates.
06/12/2026
User avatar None

String added in the repository
By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up well with local planar results in good local projections. Over larger areas, the spheroidal calculations will be more accurate than any calculation done on a projected plane. The difference is that the spheroid takes into account the curvature and non-spherical shape of the Earth, whereas planar calculations assume a flat surface.
By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up well with local planar results in good local projections. Over larger areas, the spheroidal calculations will be more accurate than any calculation done on a projected plane. The difference is that the spheroid takes into account the curvature and non-spherical shape of the Earth, whereas planar calculations assume a flat surface.
06/12/2026
User avatar None

String added in the repository
The <varname>geometry</varname> data type is <emphasis>opaque</emphasis>, which means that all access is done via invoking functions on geometry values. Functions allow creating geometry objects, accessing or updating all internal fields, and computing new geometry values. PostGIS supports all the functions specified in the OGC <link xlink:href="https://portal.ogc.org/files/?artifact_id=25354"><emphasis>Simple feature access - Part 2: SQL option</emphasis></link> (SFS) specification, as well many others. See <xref linkend="reference"/> for the full list of functions.
The <varname>geometry</varname> data type is <emphasis>opaque</emphasis>, which means that all access is done via invoking functions on geometry values. Functions allow creating geometry objects, accessing or updating all internal fields, and computing new geometry values. PostGIS supports all the functions specified in the OGC <link xlink:href="https://portal.ogc.org/files/?artifact_id=25354"><emphasis>Simple feature access - Part 2: SQL option</emphasis></link> (SFS) specification, as well many others. See <xref linkend="reference"/> for the full list of functions.
06/12/2026
User avatar None

String added in the repository
A MultiPolygon is a collection of non-overlapping, non-adjacent Polygons. Polygons in the collection may touch only at a finite number of points. (Two polygons are adjacent if they share an edge. They touch if they share only points or edges on their boundaries). For more details on MultiPolygon validity, see <xref linkend="OGC_Validity"/>.
A MultiPolygon is a collection of non-overlapping, non-adjacent Polygons. Polygons in the collection may touch only at a finite number of points. (Two polygons are adjacent if they share an edge. They touch if they share only points or edges on their boundaries). For more details on MultiPolygon validity, see <xref linkend="OGC_Validity"/>.
06/12/2026
Browse all translation changes