postgis @ OSGeo Weblate

Component	Approved	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
PostGIS Manual CC-BY-SA-3.0	6%	42%	53,142	969,663	6,933,874	49,266	5,512	8,759	162

Glossary Glossary	62%	77%	581	815	8,606	581	0	1	0

Overview

Project website	postgis.net
Project maintainers	robe strk komzpa cvvergara
Translation license	CC-BY-SA-3.0 ^{PostGIS Manual}

3 days ago

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		95,544		1,689,542		12,068,134
Source		6,009		105,653		754,772
Approved	1%	371	1%	5,688	1%	42,720
Waiting for review	35%	33,998	35%	606,159	35%	4,308,389
Translated	43%	41,821	42%	719,064	42%	5,125,654
Needs editing	4%	3,876	3%	67,258	4%	485,695
Read-only	7%	7,452	6%	107,217	6%	774,545
Failing checks	5%	5,512	5%	96,668	5%	666,072
Strings with suggestions	9%	8,760	9%	163,296	9%	1,156,365
Untranslated strings	52%	49,847	53%	903,220	53%	6,456,785

Last 12 months Previous

Activity in last 12 months


Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May

Quick numbers

1,689 k

Hosted words

95,544

Hosted strings

43%

Translated

Contributors

and previous 30 days

Trends of last 30 days

+6%

Hosted words

+100%

+7%

Hosted strings

+100%

+3%

Translated

+40%

—

Contributors

+100%

Language	Approved	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English	98%		0	0	0	0	1,632	0	11

Chinese (Simplified)	2%	98%	71	1,238	10,363	71	0	1	0

Danish	0%	1%	5,956	105,434	753,162	5,956	0	0	0

French	2%	98%	71	1,238	10,363	71	0	57	0

Georgian	0%	1%	5,869	105,482	752,966	5,869	0	0	0

German	3%	51%	2,879	50,106	364,182	224	736	146	0

Italian	2%	27%	4,354	81,429	572,427	4,246	214	4,158	0

Japanese	6%		0	0	0	0	611	0	151

Korean	2%	43%	3,372	60,342	438,371	2,941	603	4	0

Polish	2%	4%	5,671	104,323	742,299	5,596	71	6	0

Portuguese (Brazil)	2%	43%	3,371	60,010	436,086	2,975	1,133	6	0

Romanian	2%	2%	5,821	105,180	750,515	5,809	1	6	0

Russian	2%	2%	5,806	105,018	749,047	5,796	3	5	0

Spanish	2%	22%	4,641	85,228	610,238	4,453	209	4,350	0

Swedish	0%		0	0	0	0	299	0	0

Ukrainian	2%	2%	5,841	105,450	752,461	5,840	0	21	0

mt:weblate Suggestion added postgis PostGIS Manual Romanian	English Parameters Romanian 9 characters edited Parametri 3 days ago
None Changes pushed postgis PostGIS Manual	Changes pushed 6 days ago
None Repository notification received postgis PostGIS Manual	Gitea: https://git.osgeo.org/gitea/postgis/postgis, master 6 days ago
None Changes committed postgis PostGIS Manual Swedish	Changes committed 6 days ago
yeager Translation changed postgis PostGIS Manual Swedish	English This query uses a spatial measurement as an ordering value. There are several ways of approaching this problem, but the most efficient is below: Swedish 7 characters edited Current translation Translated Denna fråga använder en spatial mätning som ett ~~beställ~~ordningsvärde. Det finns flera sätt att närma sig detta problem, men det mest effektiva är nedan: 6 days ago
yeager Translation changed postgis PostGIS Manual Swedish	English Prior to PostgreSQL 9, ordering in a subquery can be used. However, sometimes the query plan may not respect the order of the subquery. Swedish 7 characters edited Current translation Translated Före PostgreSQL 9 kan ~~beställ~~ordning i en underfråga användas. Ibland kanske dock frågeplanen inte respekterar ordningen på underfrågan. 6 days ago
yeager Translation changed postgis PostGIS Manual Swedish	English The <varname>=</varname> operator returns <varname>TRUE</varname> if the coordinates and coordinate order geometry/geography A are the same as the coordinates and coordinate order of geometry/geography B. PostgreSQL uses the =, <, and > operators defined for geometries to perform internal orderings and comparison of geometries (ie. in a GROUP BY or ORDER BY clause). Swedish 8 characters edited Current translation Translated Operatorn <varname>=</varname> returnerar <varname>SANT</varname> om koordinaterna och koordinatordningen geometri / geografi A är desamma som koordinaterna och koordinatordningen för geometri / geografi B. PostgreSQL använder operatöorerna =, < och > som definieras för geometrier för att utföra interna ~~beställ~~ordningar och jämförelse av geometrier (dvs. i en GROUP BY- eller ORDER BY-klausul). 6 days ago
yeager Translation changed postgis PostGIS Manual Swedish	English Now issue a query where you use the geometry operator && to search for a bounding box that matches only very few of those rows. Now the query optimizer sees that the table has only 3 pages and 80 rows. It estimates that a sequential scan on such a small table is much faster than using an index. And so it decides to ignore the GIST index. Usually, this estimation is correct. But in our case, the && operator has to fetch every geometry from disk to compare the bounding boxes, thus reading all TOAST pages, too. Swedish 2 characters edited Current translation Translated Ställ nu en fråga där du använder geometrioperatorn & & för att söka efter en avgränsningsbox som bara matchar mycket få av dessa rader. Nu ser frågeoptimeraren att tabellen bara har 3 sidor och 80 rader. Den uppskattar att en sekventiell skanning på en så liten tabell är mycket snabbare än att använda ett index. Och så beslutar den att ignorera GIST-indexet. Vanligtvis är denna uppskattning korrekt. Men i vårt fall måste operat~~öre~~orn hämta varje geometri från disken för att jämföra begränsningsrutorna, vilket innebär att alla TOAST-sidor också måste läsas. 6 days ago
yeager Translation changed postgis PostGIS Manual Swedish	English The above syntax will build a 2-dimensional index. A 3-dimensional index for the geometry type can be created using the 3D operator class: Swedish 1 character edited Current translation Translated Syntaxen ovan bygger upp ett 2-dimensionellt index. Ett 3-dimensionellt index för geometritypen kan skapas med hjälp av operatöorsklassen 3D: 6 days ago
yeager Translation changed postgis PostGIS Manual Swedish	English Currently, only "inclusion support" is provided, meaning that just the <varname>&&</varname>, <varname>~</varname> and <varname>@</varname> operators can be used for the 2D cases (for both <code>geometry</code> and <code>geography</code>), and just the <varname>&&&</varname> operator for 3D geometries. There is currently no support for kNN searches. Swedish 1 character edited Current translation Translated För närvarande finns endast "inclusion support", vilket innebär att endast operatöorerna <varname>&&</varname>, <varname>~</varname> och <varname>@</varname> kan användas för 2D-fall (för både <code>geometri</code> och <code>geografi</code>), och endast operatorn <varname>&&&</varname> för 3D-geometrier. Det finns för närvarande inget stöd för kNN-sökningar. 6 days ago

Browse all project changes

strk

Announcement posted

Translators please make sure NOT to translate XML entities like > as those translation (maybe automated by some browser plugin) tend to often break the system, as shown for example here for the Chinese translation: https://woodie.osgeo.org/repos/30/pipeline/964/22

a year ago

Browse all project changes

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2025-05-26 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2025-05-26 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add