Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English
German 0% 34 797 5,076 34
Japanese
Spanish
Swedish
Ukrainian 100% 1
Please sign in to see the alerts.

Summary

Project website postgis.net/workshops/postgis-intro
Project maintainers9 User avatar cvvergaraUser avatar dkastlUser avatar komzpaUser avatar astrid_emdeUser avatar dmateosUser avatar jsanzUser avatar andischiUser avatar jefUser avatar yellow73
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://github.com/postgis/postgis-workshops.git
Repository branch master
Last remote commit Update sql cheat sheet with makevalid example 5f99414
Paul Ramsey authored 10/30/2025
Last commit in Weblate Translated using Weblate (Spanish) d58b65f
Weblate authored 09/26/2025
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/validity.po
02/10/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 204 4,782 30,456
Source 34 797 5,076
Translated 83% 170 83% 3,985 83% 25,380
Needs editing 0% 0 0% 0 0% 0
Read-only 16% 34 16% 797 16% 5,076
Failing checks 1% 1 1% 2 1% 13
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 16% 34 16% 797 16% 5,076
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 17 changes 0 changes 0 changes 0 changes 0 changes 3 changes 82 changes 0 changes 0 changes 0 changes 77 changes 0 changes 23 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

4,782
Hosted words
204
Hosted strings
83%
Translated
7
Contributors
0
Components
6
Languages
6
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

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

Alert triggered
Duplicated file mask. 02/18/2026
User avatar None

Alert triggered
Broken project website URL 12/27/2025
User avatar robe

Changes committed
Changes committed 09/26/2025
User avatar robe

Translation changed
What's going on here? The algorithm that calculates area assumes that rings do not self-intersect. A well-behaved ring will always have the area that is bounded (the interior) on one side of the bounding line (it doesn't matter which side, just that it is on *one* side). However, in our (poorly behaved) figure-eight, the bounded area is to the right of the line for one lobe and to the left for the other. This causes the areas calculated for each lobe to cancel out (one comes out as 1, the other as -1) hence the "zero area" result.
¿Qué ocurre aquí? El algoritmo que calcula el área asume que los anillos no se auto-intersecan. Un anillo que se comporte bien siempre tendrá el área delimitada (el interior) a un lado de la línea de delimitación (no importa a qué lado, sólo que sea a *un* lado). Sin embargo, en nuestro (mal comportamiento) ocho, el área delimitada está a la derecha de la línea para un lóbulo y a la izquierda para el otro. Esto hace que las áreas calculadas para cada lóbulo se anulen (una sale como 1, la otra como -1), de ahí el resultado de «"área cero»".
09/26/2025
User avatar robe

Translation changed
The outer ring is actually a figure-eight, with a self-intersection in the middle. Note that the graphic routines successfully render the polygon fill, so that visually it is appears to be an "area": two one-unit squares, so a total area of two units of area.
El anillo exterior es en realidad una figura de ocho, con una auto-intersección en el centro. Obsérvese que las rutinas gráficas representan correctamente el relleno del polígono, de modo que visualmente parece un «"área»": dos cuadrados de una unidad, es decir, un área total de dos unidades de área.
09/26/2025
User avatar robe

Translation changed
In 90% of the cases the answer to the question, "why is my query giving me a 'TopologyException' error" is "one or more of the inputs are invalid". Which begs the question: what does it mean to be invalid, and why should we care?
En el 90% de los casos, la respuesta a la pregunta «"¿por qué mi consulta da un error “'TopologyException”?»'?" es «"una o varias de las entradas no son válidas»". Lo que nos lleva a preguntarnos: ¿qué significa que no sea válida y por qué debería importarnos?
09/26/2025
User avatar None

Changes committed
Changes committed 09/04/2025
User avatar paulo

Translation changed
What is Validity
¿Qué es la Validez?
09/04/2025
User avatar None

Changes committed
Changes committed 08/31/2025
User avatar paulo

Translation completed
Translation completed 08/31/2025
Browse all component changes