Translation status

34 Strings 100%
Browse Translate
797 Words 100%
5,076 Characters 100%

Strings status

Strings Words Characters
34 797 5,076
All strings Browse Translate Zen
34 797 5,076
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
spatial_relationships_exercises 0 0 0 0 0 0 0
geography_exercises 0 0 0 0 0 0 0
joins_exercises 0 0 0 0 0 0 0
projection_exercises 0 0 0 0 0 0 0
advanced_geometry_construction 0 0 0 0 0 0 0
simple_sql_exercises 0 0 0 0 0 0 0
3d 0 0 0 0 0 0 0
backup 0 0 0 0 0 0 0
license 0 0 0 0 0 0 0
installation CC-BY-3.0-US 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar komzpa User avatar yellow73 User avatar dmateos User avatar dkastl User avatar astrid_emde User avatar jsanz User avatar andischi User avatar cvvergara 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 #126 from enockseth/fix-typo 9925f56
Paul Ramsey authored yesterday
Last commit in Weblate Translated using Weblate (Japanese) 0f44c94
Teramoto Ikuhiro authored a month ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/validity.po
Translation file Download postgis-intro/sources/locale/ja/LC_MESSAGES/validity.po
Last change Oct. 31, 2023, 4:23 a.m.
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 34 797 5,076
Translated 100% 34 100% 797 100% 5,076
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 42 changes 0 changes 0 changes 0 changes 31 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 8 changes 0 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

797
Hosted words
34
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. validity
  3. Japanese
Changes committed 9 months 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」の結果となります。
9 months 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」の結果となります。
9 months 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:
データベースがこのポリゴンの面積をどう考えるか見てみましょう:
9 months 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面積単位となる「領域」が見えていることに注意して下さい。
9 months 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:
この図では、もう少しはっきりと不正性が分かります:
9 months 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:
構造が重要である理由の例を示します。このポリゴンは不正です:
9 months ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
The reason the rules are important is because algorithms for geometry calculations depend on consistent structure in the inputs. It is possible to build algorithms that have no structural assumptions, but those routines tend to be very slow, because the first step in any structure-free routine is to *analyze the inputs and build structure into them*.
規則が重要であるのは、ジオメトリ計算用のアルゴリズムが、入力の一貫した構造に依存しているためです。構造についての仮定を持たないアルゴリズムの構築は可能です。しかし、あらゆる構造自由なルーティンの最初に行うことが「入力の解析と構造の組み込み」になるため、これらのルーティンは非常に遅くなる傾向にあります。
9 months ago
User avatar yellow73

Translation changed

  1. postgis-workshop
  2. validity
  3. Japanese
The last three rules are in the arbitrary category. There are other ways to define polygons that are equally self-consistent but the rules above are the ones used by the :term:`OGC` :term:`SFSQL` standard that PostGIS conforms to.
最後の三つの規則は任意カテゴリに含まれます。自己一貫性があるポリゴンを定義する他の方法がありますが、上の規則は、PostGIS がｋ準拠する :term:`OGC` :term:`SFSQL` 標準で使われるものです。
9 months ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. validity
  3. Japanese
The last three rules are in the arbitrary category. There are other ways to define polygons that are equally self-consistent but the rules above are the ones used by the :term:`OGC` :term:`SFSQL` standard that PostGIS conforms to.
最後の三つの規則は任意カテゴリに含まれます。自己一貫性があるポリゴンを定義する他の方法がありますが、上の規則は、PostGIS がｋ準拠する :term:`OGC` :term:`SFSQL` 標準で使われるものです。
9 months ago
Browse all translation changes