Translation status

12 Strings 100%
Browse Translate
397 Words 100%
2,475 Characters 100%

Strings status

Strings Words Characters
12 397 2,475
All strings Browse Translate Zen
12 397 2,475
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
tuning 0 0 0 0 5 1 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
topology CC-BY-3.0-US 0 0 0 0 0 1 0
geography_exercises 0 0 0 0 4 0 0
security 0 0 0 0 1 1 0
clusterindex 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar yellow73 User avatar jef User avatar astrid_emde User avatar dmateos User avatar dkastl User avatar jsanz User avatar cvvergara User avatar andischi User avatar komzpa
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 #155 from osgeoweblate/weblate-postgis-workshop-index 1cb0b08
Regina Obe authored yesterday
Last commit in Weblate Translated using Weblate (Ukrainian) 34c3a85
Denys Kovshun authored a month ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/equality.po
Translation file Download postgis-intro/sources/locale/sv/LC_MESSAGES/equality.po
Last change June 19, 2025, 11:50 p.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 12 397 2,475
Translated 100% 12 100% 397 100% 2,475
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 30 changes 0 changes 0 changes 0 changes 0 changes
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug

Quick numbers

397
Hosted words
12
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. equality
  3. Swedish
Changes committed 3 months ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. equality
  3. Swedish
Exact equality requires, in the worst case, comparison of each and every vertex in the geometry to determine equality. This can be slow, and may not be appropriate for comparing huge numbers of geometries. To allow for speedier comparison, the equal bounds operator, :command:`~=`, is provided. This operates only on the bounding box (rectangle), ensuring that the geometries occupy the same two dimensional extent, but not necessarily the same space.
Exakt likhet kräver, i värsta fall, jämförelse av varje enskilt vertex i geometrin för att fastställa likhet. Detta kan ta lång tid och är kanske inte lämpligt för att jämföra ett stort antal geometrier. För att möjliggöra snabbare jämförelser finns operatorn equal bounds, :command:`~=`. Denna operatöor verkar endast på den avgränsande rutan (rektangeln) och säkerställer att geometrierna har samma tvådimensionella utsträckning, men inte nödvändigtvis samma utrymme.
3 months ago
User avatar None

Changes committed

  1. postgis-workshop
  2. equality
  3. Swedish
Changes committed 3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
As you can see, all of our spatially equal geometries also have equal bounds. Unfortunately, Polygon 5 is also returned as equal under this test, because it shares the same bounding box as the other geometries. Why is this useful, then? Although this will be covered in detail later, the short answer is that this enables the use of spatial indexing that can quickly reduce huge comparison sets into more manageable blocks when joining or filtering data.
Som du kan se har alla våra spatialt lika geometrier också lika gränser. Tyvärr returneras Polygon 5 också som lika i det här testet, eftersom den delar samma bounding box som de andra geometrierna. Varför är då detta användbart? Även om detta kommer att behandlas i detalj senare är det korta svaret att detta möjliggör användning av spatial indexering som snabbt kan reducera enorma jämförelseuppsättningar till mer hanterbara block när data sammanfogas eller filtreras.
3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
Exact equality requires, in the worst case, comparison of each and every vertex in the geometry to determine equality. This can be slow, and may not be appropriate for comparing huge numbers of geometries. To allow for speedier comparison, the equal bounds operator, :command:`~=`, is provided. This operates only on the bounding box (rectangle), ensuring that the geometries occupy the same two dimensional extent, but not necessarily the same space.
Exakt likhet kräver, i värsta fall, jämförelse av varje enskilt vertex i geometrin för att fastställa likhet. Detta kan ta lång tid och är kanske inte lämpligt för att jämföra ett stort antal geometrier. För att möjliggöra snabbare jämförelser finns operatorn equal bounds, :command:`~=`. Denna operatör verkar endast på den avgränsande rutan (rektangeln) och säkerställer att geometrierna har samma tvådimensionella utsträckning, men inte nödvändigtvis samma utrymme.
3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
Equal Bounds
Jämna gränser
3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
These results are more in line with our intuitive understanding of equality. Polygons 1 through 4 are considered equal, since they enclose the same area. Note that neither the direction of the polygon is drawn, the starting point for defining the polygon, nor the number of points used are important here. What is important is that the polygons contain the same space.
Dessa resultat är mer i linje med vår intuitiva förståelse av jämlikhet. Polygonerna 1 till 4 anses vara lika, eftersom de omsluter samma område. Observera att varken polygonens riktning, startpunkten för polygonens definition eller antalet punkter som används är viktiga här. Det viktiga är att polygonerna innehåller samma utrymme.
3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
As we saw above, exact equality does not take into account the spatial nature of the geometries. There is an function, aptly named :command:`ST_Equals`, available to test the spatial equality or equivalence of geometries.
Som vi såg ovan tar exakt likhet inte hänsyn till geometriernas spatiala karaktär. Det finns en funktion, med det passande namnet :command:`ST_Equals`, för att testa geometriers spatiala jämlikhet eller ekvivalens.
3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
Spatially Equal
Spatialt lika
3 months ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. equality
  3. Swedish
In this example, the polygons are only equal to themselves, not to other seemingly equivalent polygons (as in the case of Polygons 1 through 3). In the case of Polygons 1, 2, and 3, the vertices are in identical positions but are defined in differing orders. Polygon 4 has colinear (and thus redundant) vertices on the hexagon edges causing inequality with Polygon 1.
I det här exemplet är polygonerna bara lika med sig själva, inte med andra till synes likvärdiga polygoner (som i fallet med polygonerna 1 till 3). I fallet med polygonerna 1, 2 och 3 är hörnen identiskt placerade men definierade i olika ordning. Polygon 4 har kolinjära (och därmed överflödiga) hörn på hexagonkanterna, vilket orsakar ojämlikhet med polygon 1.
3 months ago
Browse all translation changes