Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 0 0 0
Chinese (Simplified) 0% 12 397 2,475 12 0 0 0
German 0% 12 397 2,475 12 0 0 0
Japanese 0 0 0 0 0 0 0
Spanish 0% 12 397 2,475 12 0 0 0
Please sign in to see the alerts.

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar komzpa User avatar cvvergara User avatar dmateos User avatar dkastl User avatar jsanz User avatar andischi User avatar yellow73 User avatar astrid_emde User avatar jef
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 #137 from latot/topo_intro 5ca8351
Regina Obe authored a month ago
Last commit in Weblate Merge pull request #117 from osgeoweblate/weblate-postgis-workshop-index e91022e
Regina Obe authored 10 months ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/equality.po
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 60 1,985 12,375
Source 12 397 2,475
Translated 40% 24 40% 794 40% 4,950
Needs editing 0% 0 0% 0 0% 0
Read-only 20% 12 20% 397 20% 2,475
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 60% 36 60% 1,191 60% 7,425
Last 12 months Previous

Activity in last 12 months

4 changes 0 changes 0 changes 15 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 24 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Quick numbers

1,985
Hosted words
60
Hosted strings
40%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Alert triggered

  1. postgis-workshop
  2. equality
Component seems unused. 6 months ago
User avatar zcw5

Resource updated

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
File postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/equality.po was added. 11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
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.
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
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.
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
Equal Bounds
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
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.
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
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.
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
Spatially Equal
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
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.
 
11 months ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. equality
  3. Chinese (Simplified)
Exact equality is determined by comparing two geometries, vertex by vertex, in order, to ensure they are identical in position. The following examples show how this method can be limited in its effectiveness.
 
11 months ago
Browse all component changes