Translation status

5,738 Strings
4%
Browse Translate
99,912 Words
1%
715,285 Characters
1%

Strings status

Strings Words Characters
5,738 99,912 715,285
All strings Browse Translate Zen
125 138 1,722
Read-only strings Browse Translate Zen
292 1,234 11,595
Translated strings Browse Translate Zen
167 1,096 9,873
Strings waiting for review Browse Translate Zen
5,446 98,678 703,690
Unfinished strings Browse Translate Zen
5,372 97,824 695,673
Untranslated strings Browse Translate Zen
74 854 8,017
Strings marked for edit Browse Translate Zen
5 5 103
Strings with suggestions Browse Translate Zen
5,441 98,673 703,587
Unfinished strings without suggestions Browse Translate Zen
116 1,167 10,644
Strings with any failing checks Browse Translate Zen
47 317 2,639
Translated strings with any failing checks Browse Translate Zen
37 116 1,136
Failing check: Unchanged translation Browse Translate Zen
4 111 921
Failing check: Double space Browse Translate Zen
15 377 2,544
Failing check: Mismatched full stop Browse Translate Zen
2 23 161
Failing check: Mismatched colon Browse Translate Zen
2 4 37
Failing check: Mismatched question mark Browse Translate Zen
8 91 1,722
Failing check: Multiple capitals Browse Translate Zen
66 846 7,951
Failing check: Has been translated Browse Translate Zen
1 56 400
Failing check: Mismatching line breaks Browse Translate Zen
10 114 2,166
Failing check: XML markup Browse Translate Zen
4 157 1,077
Failing check: Chars around XML tags Browse Translate Zen
2 3 34
Failing check: Prohibited initial character Browse Translate Zen
Component Approved Translated Unreviewed Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Glossary 78% 79% 2 32 52 490 32 2
PostGIS Manual CC-BY-SA-3.0 0% 2% 165 5,414 98,626 703,200 5,340 114 5

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
Language Polish
Language code pl
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 41,500,500
06/13/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 5,738 99,912 715,285
Approved 0% 0 0% 0 0% 0
Waiting for review 2% 167 1% 1,096 1% 9,873
Translated 5% 292 1% 1,234 1% 11,595
Needs editing 1% 74 1% 854 1% 8,017
Read-only 2% 125 1% 138 1% 1,722
Failing checks 2% 116 1% 1,167 1% 10,644
Strings with suggestions 1% 5 1% 5 1% 103
Untranslated strings 93% 5,372 97% 97,824 97% 695,673
Last 12 months Previous

Activity in last 12 months

82 changes 0 changes 44 changes 74 changes 47 changes 21 changes 23 changes 0 changes 0 changes 0 changes 64 changes 146 changes 7 changes 0 changes 11 changes 0 changes 0 changes 0 changes 0 changes 14 changes 19 changes 0 changes 57 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

98,946
Hosted words
5,701
Hosted strings
5%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated
The “doc/po/pl/postgis-manual.po” file was changed. 06/13/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"/>.
 
06/13/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.
 
06/13/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.
 
06/13/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.
 
06/13/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.
 
06/13/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"/>.
 
06/13/2026
User avatar None

String added in the repository
The OGC geometry model defines validity rules for each geometry type. These rules ensure that geometry values represents realistic situations (e.g. it is possible to specify a polygon with a hole lying outside its shell, but this makes no sense geometrically and is thus invalid). PostGIS also allows storing and manipulating invalid geometry values. This allows detecting and fixing them if needed. See <xref linkend="OGC_Validity"/>
 
06/13/2026
User avatar None

String added in the repository
The geometry model allows evaluating topological spatial relationships as described in <xref linkend="DE-9IM"/>. To support this the concepts of <emphasis role="bold">interior</emphasis>, <emphasis role="bold">boundary</emphasis> and <emphasis role="bold">exterior</emphasis> are defined for each geometry type. Geometries are topologically closed, so they always contain their boundary. The boundary is a geometry of dimension one less than that of the geometry itself. For example, the boundary of a Polygon is its rings (LineStrings), the boundary of a LineString is its endpoints (Points), and the boundary of a Point is empty.
 
06/13/2026
User avatar None

String added in the repository
The geometry <emphasis role="bold">dimension</emphasis> is a property of geometry types. Point types have dimension 0, linear types have dimension 1, polygonal types have dimension 2, and solid types have dimension 3. Collections have the dimension of the maximum element dimension.
 
06/13/2026
Browse all changes for this language