Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Glossary 0% 0% 159 192 2,252 159 0 0 0
PostGIS Manual CC-BY-SA-3.0 0% 1% 5,796 106,698 763,139 5,796 0 0 0

Overview

Project website postgis.net
Project maintainers User avatar komzpa User avatar strk User avatar robe User avatar cvvergara
Translation license CC-BY-SA-3.0 PostGIS Manual
4 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 6,052 106,996 766,608
Approved 0% 0 0% 0 0% 0
Waiting for review 1% 97 1% 106 1% 1,217
Translated 1% 97 1% 106 1% 1,217
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,955 99% 106,890 99% 765,391
Last 12 months Previous

Activity in last 12 months

0 changes 64 changes 0 changes 7 changes 0 changes 11 changes 0 changes 0 changes 0 changes 0 changes 0 changes 19 changes 0 changes 55 changes 6,018 changes 0 changes 44 changes 74 changes 47 changes 21 changes 23 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

106 k
Hosted words
6,052
Hosted strings
1%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated

  1. postgis
  2. PostGIS Manual
  3. Georgian
The "doc/po/ka/postgis-manual.po" file was changed. 6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
BRIN stands for "Block Range Index". It is a general-purpose index method provided by PostgreSQL. BRIN is a <emphasis>lossy</emphasis> index method, meaning that a secondary check is required to confirm that a record matches a given search condition (which is the case for all provided spatial indexes). It provides much faster index creation and much smaller index size, with reasonable read performance. Its primary purpose is to support indexing very large tables on columns which have a correlation with their physical location within the table. In addition to spatial indexing, BRIN can speed up searches on various kinds of attribute data structures (integer, arrays etc). For more information see the <link xlink:href="https://www.postgresql.org/docs/current/brin.html">PostgreSQL manual</link>.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
Like the geometry data type, geography data is associated with a spatial reference system via a spatial reference system identifier (SRID). Any geodetic (long/lat based) spatial reference system defined in the <varname>spatial_ref_sys</varname> table can be used. You can add your own custom geodetic spatial reference system as described in <xref linkend="user-spatial-ref-sys"/>.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
Keep collapsed of "true" means geometry components that collapse to a lower dimensionality will be retained.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
Keep collapsed of "false" is the default, and means that geometry components that collapse to a lower dimensionality, for example a one-point linestring will be dropped.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
The "keepcollapsed" key is only valid for the "structure" algorithm, and takes a value of "true" or "false".
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
"structure" is an algorithm that distinguishes between interior and exterior rings, building new geometry by unioning exterior rings, and then differencing all interior rings. The results tend to be more intuitive, where collapsed lines are discarded in the output.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
"linework" is the default algorithm, and builds valid geometries by first extracting all lines, noding that linework together, then building a value output from the linework. The requirement that no vertices are lost can generate complex collections as outputs.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
Changed 3.7.0, the polygonization honours PostgreSQL interrupts so cancellations and statement timeouts halt processing promptly.
 
6 days ago
User avatar None

String added in the repository

  1. postgis
  2. PostGIS Manual
  3. Georgian
Complete example of tiles of a coverage.
 
6 days ago
Browse all changes for this language