Translation status

5,738 Strings
1%
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
91 99 1,133
Translated strings Browse Translate Zen
91 99 1,133
Strings waiting for review Browse Translate Zen
5,647 99,813 714,152
Unfinished strings Browse Translate Zen
5,647 99,813 714,152
Untranslated strings Browse Translate Zen
35 35 519
Translated strings with dismissed checks Browse Translate Zen
Component Approved Translated Unreviewed Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Glossary 0% 0% 159 192 2,252 159
PostGIS Manual CC-BY-SA-3.0 0% 1% 91 5,488 99,621 711,900 5,488

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 Georgian
Language code ka
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 4,324,687
06/18/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 1% 91 1% 99 1% 1,133
Translated 1% 91 1% 99 1% 1,133
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 98% 5,647 99% 99,813 99% 714,152
Last 12 months Previous

Activity in last 12 months

6,018 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 55 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

99,912
Hosted words
5,738
Hosted strings
1%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

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

Resource updated
The “doc/po/ka/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
Browse all changes for this language