Translation status

15 Strings
100%
Browse Translate
429 Words
100%
2,591 Characters
100%

Strings status

Strings Words Characters
15 429 2,591
All strings Browse Translate Zen
15 429 2,591
Translated strings Browse Translate Zen

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 (Ukrainian) 34c3a85
User avatar dkovshun authored 08/10/2025
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/knn.po
Translation file Download postgis-intro/sources/locale/sv/LC_MESSAGES/knn.po
Last change June 19, 2025, 11:50 p.m.
Last change made by None
Language Swedish
Language code sv
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 13,338,376
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
02/09/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 15 429 2,591
Translated 100% 15 100% 429 100% 2,591
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 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 38 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

429
Hosted words
15
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed
Changes committed 06/19/2025
User avatar yeager

Translation changed
The explain shows the loop on the subway stations, and the index-assisted order by inside the loop where we want it:
Förklaringen visar slingan på tunnelbanestationerna och den indexassisterade beställordningen genom att lägga in slingan där vi vill ha den:
06/19/2025
User avatar yeager

Translation changed
PostgreSQL solves the nearest neighbor problem by introducing an "order by distance" (``<->``) operator that induces the database to use an index to speed up a sorted return set. With an "order by distance" operator in place, a nearest neighbor query can return the "N nearest features" just by adding an ordering and limiting the result set to N entries.
PostgreSQL löser det närmaste grannproblemet genom att införa en "order by distance" (``<->``) operatöor som inducerar databasen att använda ett index för att påskynda en sorterad returuppsättning. Med en "order by distance" -operator på plats kan en närmaste grannfråga returnera "N närmaste funktioner" bara genom att lägga till en beställordning och begränsa resultatuppsättningen till N-poster.
06/19/2025
User avatar yeager

Translation changed
PostgreSQL solves the nearest neighbor problem by introducing an "order by distance" (``<->``) operator that induces the database to use an index to speed up a sorted return set. With an "order by distance" operator in place, a nearest neighbor query can return the "N nearest features" just by adding an ordering and limiting the result set to N entries.
PostgreSQL löser det närmaste grannproblemet genom att införa en "order by distance" (``<->``) operatör som inducerar databasen att använda ett index för att påskynda en sorterad returuppsättning. Med en "order by distance" -operatöor på plats kan en närmaste grannfråga returnera "N närmaste funktioner" bara genom att lägga till en beställning och begränsa resultatuppsättningen till N-poster.
06/19/2025
User avatar None

Changes committed
Changes committed 06/04/2025
User avatar yeager

Translation uploaded
The explain shows the loop on the subway stations, and the index-assisted order by inside the loop where we want it:
Förklaringen visar slingan på tunnelbanestationerna och den indexassisterade beställningen genom att lägga in slingan där vi vill ha den:
06/04/2025
User avatar yeager

Translation uploaded
Note the way the ``CROSS JOIN LATERAL`` acts as the inner part of a loop driven by the subways table. Each record in the subways table gets fed into the lateral subquery, one at a time, so you get a nearest result for each subway record.
Observera hur ``CROSS JOIN LATERAL`` fungerar som den inre delen av en slinga som drivs av tunnelbanetabellen. Varje post i tunnelbanetabellen matas in i den laterala underfrågan, en i taget, så att du får ett närmaste resultat för varje tunnelbanepost.
06/04/2025
User avatar yeager

Translation uploaded
Here we will find the nearest street to each subway station:
Här hittar vi den närmaste gatan till varje tunnelbanestation:
06/04/2025
User avatar yeager

Translation uploaded
Fortunately, there's a SQL language feature that allows us to run a query repeatedly driven in a loop: the `LATERAL join <https://medium.com/kkempin/postgresqls-lateral-join-bfd6bd0199df>`_.
Lyckligtvis finns det en funktion i SQL-språket som gör att vi kan köra en fråga upprepade gånger i en slinga: `LATERAL join <https://medium.com/kkempin/postgresqls-lateral-join-bfd6bd0199df>`_.
06/04/2025
User avatar yeager

Translation uploaded
The index assisted order by operator has one major draw back: it only works with a **single geometry literal** on one side of the operator. This is fine for finding the objects nearest to one query object, but does not help for a spatial join, where the goal is to find the nearest neighbor for each of a full set of candidates.
Den indexassisterade order by-operatorn har en stor nackdel: den fungerar bara med en **enkel geometrilitteral** på ena sidan av operatorn. Detta är bra för att hitta de objekt som ligger närmast ett frågeobjekt, men hjälper inte för en spatial join, där målet är att hitta den närmaste grannen för var och en av en fullständig uppsättning kandidater.
06/04/2025
Browse all translation changes