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

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
geometry_returning 0 0 0 0 1 0 0
projection_exercises 0 0 0 0 8 0 0
simple_sql_exercises 0 0 0 0 13 0 0
tuning 0 0 0 0 5 1 0
index CC-BY-3.0-US 0 0 0 0 0 0 0
backup 0 0 0 0 4 0 0
license 0 0 0 0 0 0 0
installation CC-BY-3.0-US 0 0 0 0 0 0 0
equality 0 0 0 0 0 0 0
joins_advanced 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar jef User avatar astrid_emde User avatar dmateos User avatar dkastl User avatar jsanz User avatar andischi User avatar yellow73 User avatar komzpa User avatar cvvergara
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 Merge pull request #146 from AllenSH12/fixups 37f3a52
Regina Obe authored 11 days ago
Last commit in Weblate Translated using Weblate (Spanish) 78c5aae
Weblate authored 3 days ago
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 author None
3 days ago

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 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 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

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

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. knn
  3. Swedish
Changes committed 3 days ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. knn
  3. Swedish
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:
3 days ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. knn
  3. Swedish
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.
3 days ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. knn
  3. Swedish
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.
3 days ago
User avatar None

Changes committed

  1. postgis-workshop
  2. knn
  3. Swedish
Changes committed 2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. knn
  3. Swedish
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:
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. knn
  3. Swedish
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.
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. knn
  3. Swedish
Here we will find the nearest street to each subway station:
Här hittar vi den närmaste gatan till varje tunnelbanestation:
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. knn
  3. Swedish
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>`_.
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. knn
  3. Swedish
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.
2 weeks ago
Browse all translation changes