Translation status

61 Strings 100%
Browse Translate
1,634 Words 100%
10,453 Characters 100%

Strings status

Strings Words Characters
61 1,634 10,453
All strings Browse Translate Zen
61 1,634 10,453
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
geometry_returning 0 0 0 0 0 0 0
projection_exercises 0 0 0 0 0 0 0
simple_sql_exercises 0 0 0 0 0 0 0
tuning 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
equality 0 0 0 0 0 0 0
joins_advanced 0 0 0 0 0 0 0
security 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 cvvergara User avatar astrid_emde User avatar yellow73 User avatar dmateos User avatar dkastl User avatar jsanz User avatar andischi User avatar komzpa
Translation license Creative Commons Attribution 3.0 United States
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 3 weeks ago
Last commit in Weblate Translated using Weblate (Japanese) 90ade02
Weblate Translation Memory authored 3 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/topology.po
Translation file Download postgis-intro/sources/locale/ja/LC_MESSAGES/topology.po
Last change June 11, 2025, 10:47 a.m.
Last author None
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 1,634 10,453
Translated 100% 61 100% 1,634 100% 10,453
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 205 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 19 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

1,634
Hosted words
61
Hosted strings
100%
Translated
3
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. topology
  3. Japanese
Changes committed 3 weeks ago
User avatar None

Changes committed

  1. postgis-workshop
  2. topology
  3. Japanese
Changes committed 3 weeks ago
User avatar yellow73

Suggestion removed

  1. postgis-workshop
  2. topology
  3. Japanese
「と」「とを」の方が適当です。
What is returned are a set of topolements. A topoelement is represented as an array of 2 integers with the first number being the id of the element, and the second, being the layer (or primitive type) of the element. PostGIS GetTopoElements returns the primitives of a topogeometry with types number 1-3 corresponding to (1: nodes, 2: edges, and 3: faces). All the topoelements for neighborhoods and boroughs are type 3, which corresponds to a topological face. We can use the `ST_GetFaceGeometry <https://postgis.net/docs/ST_GetFaceGeometry.html>`_ to get a visual representation of these shared faces as follows:
トポエレメントの集合が返されます。トポエレメントは二つの整数の配列として表現されます。一つ目は要素識別子、二つ目は要素のレイヤ (またはプリミティブタイプ) です。PostGIS GetTopoElements はタイプ番号 1-3 (1:ノード, 2:エッジ, 3:フェイス) でトポジオメトリのプリミティブを返します。全ての地区と行政区のトポエレメントのタイプ番号は、フェイスに対応する 3 です。 `ST_GetFaceGeometry <https://postgis.net/docs/ja/ST_GetFaceGeometry.html>`_ を使って、これらの共有されたフェイスの視覚表現を得ることができます。次のようにします:
4 weeks ago
User avatar yellow73

Translation completed

  1. postgis-workshop
  2. topology
  3. Japanese
Translation completed 4 weeks ago
User avatar yellow73

Translation changed

  1. postgis-workshop
  2. topology
  3. Japanese
Now we can express declaratively that boros are formed from a collection of neighborhoods by defining a column called *topo* in *nyc_boros_t* table that is of type POLYGON and is a collection of other topogeometries from *nyc_neighborhoods_t.topo* column.
行政区*nyc_boros_t* テーブル内の *topo* というカラムを定義することで、行政区が地区のコレクションから生成されることを宣言的に表現できます。*topo* カラムは、POLYGON タイプであり、かつ *nyc_neighborhoods_t.topo* カラムからの他のにあるトポジオメトリのコレクションである *nyc_boros_t* テーブルの *topo* カラムを定義することで地区のコレクションから形成されることが、宣言的に表現されます。
4 weeks ago
User avatar yellow73

Translation changed

  1. postgis-workshop
  2. topology
  3. Japanese
Which tells us that Queens and Brooklyn are in the middle of border wars. In this query we use the `GetTopoGeomElements <https://postgis.net/docs/GetTopoGeomElements.html>`_ function to declaratively inspect what components are shared across boroughs.
クイーンズやブルックリンが境界戦争の真っただ中にあることを示しています。このクエリでは `GetTopoGeomElements <https://postgis.net/docs/ja/GetTopoGeomElements.html>`_ 関数を使って宣言的に、行政区をまたいで共有する要素を調査します。
4 weeks ago
User avatar yellow73

Suggestion accepted

  1. postgis-workshop
  2. topology
  3. Japanese
We do still have gaps of empty space between neighborhoods caused by intensive simplification. Such issues can be fixed by directly editing the topology using the `Topology Editor family of functions <https://postgis.net/docs/Topology.html#Topology_Editing>`_ and/or filling in the holes and assigning those to neighborhoods.
集中的な単純化によってできた地区間の隙間がまだあります。このような問題は、 `トポロジエディタ の関数ファミリ <https://postgis.net/docs/ja/Topology.html#Topology_Editing>`_ を使ってトポロジを直接編集したり、穴を埋めたり、地区に割り当てるといった方法での訂正が可能です。
4 weeks ago
User avatar yellow73

Translation changed

  1. postgis-workshop
  2. topology
  3. Japanese
What is returned are a set of topolements. A topoelement is represented as an array of 2 integers with the first number being the id of the element, and the second, being the layer (or primitive type) of the element. PostGIS GetTopoElements returns the primitives of a topogeometry with types number 1-3 corresponding to (1: nodes, 2: edges, and 3: faces). All the topoelements for neighborhoods and boroughs are type 3, which corresponds to a topological face. We can use the `ST_GetFaceGeometry <https://postgis.net/docs/ST_GetFaceGeometry.html>`_ to get a visual representation of these shared faces as follows:
トポエレメントの集合が返されます。トポエレメントは二つの整数の配列として表現されます。一つ目は要素識別子、二つ目は要素のレイヤ (またはプリミティブタイプ) です。PostGIS GetTopoElements はタイプ番号 1-3 (1:ノード, 2:エッジ, 3:フェイス) でとトポジオメトリのプリミティブとを返します。全ての地区と行政区のトポエレメントのタイプ番号は、フェイスに対応する 3 です。 `ST_GetFaceGeometry <https://postgis.net/docs/ja/ST_GetFaceGeometry.html>`_ を使って、これらの共有されたフェイスの視覚表現を得ることができます。次のようにします:
4 weeks ago
User avatar mt:weblate-translation-memory

Suggestion added

  1. postgis-workshop
  2. topology
  3. Japanese
We do still have gaps of empty space between neighborhoods caused by intensive simplification. Such issues can be fixed by directly editing the topology using the `Topology Editor family of functions <https://postgis.net/docs/Topology.html#Topology_Editing>`_ and/or filling in the holes and assigning those to neighborhoods.
集中的な単純化によってできた地区間の隙間がまだあります。このような問題は、 `トポロジエディタ の関数ファミリ <https://postgis.net/docs/ja/Topology.html#Topology_Editing>`_ を使ってトポロジを直接編集したり、穴を埋めたり、地区に割り当てるといった方法での訂正が可能です。
4 weeks ago
User avatar mt:weblate-translation-memory

Suggestion added

  1. postgis-workshop
  2. topology
  3. Japanese
What is returned are a set of topolements. A topoelement is represented as an array of 2 integers with the first number being the id of the element, and the second, being the layer (or primitive type) of the element. PostGIS GetTopoElements returns the primitives of a topogeometry with types number 1-3 corresponding to (1: nodes, 2: edges, and 3: faces). All the topoelements for neighborhoods and boroughs are type 3, which corresponds to a topological face. We can use the `ST_GetFaceGeometry <https://postgis.net/docs/ST_GetFaceGeometry.html>`_ to get a visual representation of these shared faces as follows:
トポエレメントの集合が返されます。トポエレメントは二つの整数の配列として表現されます。一つ目は要素識別子、二つ目は要素のレイヤ (またはプリミティブタイプ) です。PostGIS GetTopoElements はタイプ番号 1-3 (1:ノード, 2:エッジ, 3:フェイス) でトポジオメトリのプリミティブを返します。全ての地区と行政区のトポエレメントのタイプ番号は、フェイスに対応する 3 です。 `ST_GetFaceGeometry <https://postgis.net/docs/ja/ST_GetFaceGeometry.html>`_ を使って、これらの共有されたフェイスの視覚表現を得ることができます。次のようにします:
4 weeks ago
Browse all translation changes