Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 0 0 0
German 0% 34 797 5,076 34 0 0 0
Japanese 0 0 0 0 0 0 0
Spanish 5% 32 794 5,055 32 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 dmateos User avatar yellow73 User avatar dkastl User avatar jsanz User avatar andischi User avatar cvvergara 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 Translated using Weblate (Japanese) 0f44c94
Teramoto Ikuhiro authored 7 months ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/validity.po
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 136 3,188 20,304
Source 34 797 5,076
Translated 51% 70 50% 1,597 50% 10,173
Needs editing 0% 0 0% 0 0% 0
Read-only 25% 34 25% 797 25% 5,076
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 48% 66 49% 1,591 49% 10,131
Last 12 months Previous

Activity in last 12 months

8 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 8 changes 3 changes 0 changes 0 changes 0 changes 0 changes 42 changes 0 changes 1 change 0 changes 31 changes 0 changes 0 changes 0 changes
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Quick numbers

3,188
Hosted words
136
Hosted strings
51%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. validity
  3. Spanish
Changes committed 7 months ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. validity
  3. Spanish
Function List
Lista de funciones
7 months ago
User avatar dmateos

Contributor joined

  1. postgis-workshop
  2. validity
  3. Spanish
Contributor joined 7 months ago
User avatar None

Changes committed

  1. postgis-workshop
  2. validity
  3. Japanese
Changes committed a year ago
User avatar yellow73

Translation changed

  1. postgis-workshop
  2. validity
  3. Japanese
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.
ここで何が起こっているのでしょう? 面積計算のアルゴリズムはリングは自己交差インタセクトしない前提で計算しています。行儀の良いリングは常に境界線の一方側 (どちらが内部でもよくて、*一方*でいいです)に (内部に) 区切られた領域を持ちます。しかしながら、行儀の悪い8の字ポリゴン内では、二つある区切られた領域の一つはラインの右側で区切られ、もう一つは左側で区切られます。これによって、両方でキャンセルしあうような面積計算になり (一方が 1 で、もう一方が -1 です)、故に「面積 0」の結果となります。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
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.
ここで何が起こっているのでしょう? 面積計算のアルゴリズムはリングは自己交差しない前提で計算しています。行儀の良いリングは常に境界線の一方側 (どちらが内部でもよくて、*一方*でいいです)に (内部に) 区切られた領域を持ちます。しかしながら、行儀の悪い8の字ポリゴン内では、二つある区切られた領域の一つはラインの右側で区切られ、もう一つは左側で区切られます。これによって、両方でキャンセルしあうような面積計算になり (一方が 1 で、もう一方が -1 です)、故に「面積 0」の結果となります。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
Let's see what the database thinks the area of our polygon is:
データベースがこのポリゴンの面積をどう考えるか見てみましょう:
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
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.
外側リングは実際に算用数字の8の字になっていて、真ん中で自己接触しています。描画ルーティンはポリゴンの内部の色塗りに成功して、二つの1面積単位の正方形からなり、合計2面積単位となる「領域」が見えていることに注意して下さい。
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
You can see the invalidity a little more clearly in this diagram:
この図では、もう少しはっきりと不正性が分かります:
a year ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
Here's an example of why structure matters. This polygon is invalid:
構造が重要である理由の例を示します。このポリゴンは不正です:
a year ago
Browse all component changes