postgis-workshop

3d

	Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
	English		0	0	0	0	0	0	0

	Chinese (Simplified)	23%	30	742	4,695	30	0	0	0

	German	0%	39	835	5,149	39	0	0	0

	Italian	0%	39	835	5,149	39	0	0	0

	Japanese		0	0	0	0	0	0	0

	Spanish	0%	39	835	5,149	39	0	0	0

Please sign in to see the alerts.

Overview

Project website	postgis.net/workshops/postgis-intro
Project maintainers	dkastl komzpa strk dmateos andischi darkblueb yellow73 jsanz astrid_emde robe cvvergara 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 #50 from osgeoweblate/weblate-postgis-workshop-index `228f9a2` Darafei Praliaskouski authored a month ago
Last commit in Weblate	Translated using Weblate (Japanese) `ef6f5f2` Teramoto Ikuhiro authored 2 weeks ago
Weblate repository	`https://weblate.osgeo.org/git/postgis-workshop/index/`
File mask	`postgis-intro/sources/locale/*/LC_MESSAGES/3d.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		234		5,010		30,894
Source		39		835		5,149
Translated	37%	87	35%	1,763	34%	10,752
Needs editing	0%	0	0%	0	0%	0
Read-only	16%	39	16%	835	16%	5,149
Failing checks	0%	0	0%	0	0%	0
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	62%	147	64%	3,247	65%	20,142

Last 12 months Previous

Activity in last 12 months


Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug

Quick numbers

5,010

Hosted words

234

Hosted strings

37%

Translated

2

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

—

Hosted strings

—

+16%

Translated

—

+100%

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2022-08-30 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2022-08-30 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English The results should be the same. In general the N-D index is very slightly slower than the 2-D index, so only use the N-D index where you are certain that N-D queries will improve the selectivity of your queries. Japanese 99 characters edited Current translation Translated 結果は同じなはずです。一般にN次元インデックスは2次元インデックスと比べて少し遅いです。N次元インデックスの使用は、N次元クエリで実行するクエリの選択性が向上すると確信できる場合だけにしてください。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English To search the ``nyc_streets`` table using the N-D index, just replace the usual ``&&`` 2-D index operator with the ``&&&`` operator. Japanese 81 characters edited Current translation Translated N次元インデックスを使って``nyc_streets``テーブル内を探索するには、2次元インデックス演算子``&&``から``&&&``演算子に変更するだけです。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English Once you have the index built, you can use it in queries with the ``&&&`` index operator. ``&&&`` has the same semantics as ``&&``, "bounding boxes interact", but applies those semantics using all the dimensions of the input geometries. Geometries with mis-matching dimensionality do not interact. Japanese 153 characters edited Current translation Translated インデックスを構築すると、クエリ内でインデックス演算子``&&&``によってインデックスを使えるようになります。``&&&``は「バウンディングボックスの相互作用」としては``&&``と同じ意味ですが、入力ジオメトリの次元の全てを使うという意味が適用されます。次元が合致しないジオメトリは相互作用しません。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English You can create a multi-dimensional index on data of any dimensionality (even mixed dimensionality). For example, to create a multi-dimensional index on the ``nyc_streets`` table, Japanese 0 characters edited Current translation Translated 多次元インデックスを任意次元のデータに作ることができます (混合次元であっても)。たとえば、``nyc_streets``テーブル上に多次元インデックスを作るには次のようにします。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English A set of GPS traces in X/Y/T space might be a good candidate for a 3-D index, if the GPS tracks overlapped each other frequently in all dimensions (for example, driving the same route over and over at different times), since there would be large variability in all dimensions of the data set. Japanese 0 characters edited Current translation Translated X/Y/T空間でのGPSトラックは、GPSトラックが互いに周期的に全ての次元に及ぶ (たとえば同じ道程を違う時刻に何度も通る)場合には、3次元インデックスの「良い」候補になるかも知れません。データセットの全ての次元で大きなばらつきが出るためです。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English A set of DEM points would probably be a poor candidate for a 3-D index, since the queries would usually be extracting a 2-D box of points, and rarely attempting to select a Z-slice of points. Japanese 16 characters edited Current translation Translated DEMポイント集合は3次元インデックスの「不十分な」候補になるかも知れません。クエリはがポイントの2次元ボックスを~~展開するためです。まれに~~抽出することになり、ポイント集合をZ値で薄切りにしようとすることがはほぼありますせん。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English Indexes are only useful when they allow the database to drastically reduce the number of return rows as a result of a WHERE condition. For a higher dimension index to be useful, the data must cover a wide range of that dimension, relative to the kinds of queries you are constructing. Japanese 43 characters edited Current translation Translated インデックスはデータベースがWHERE条件の結果として返す行を大幅に削減する~~ためには~~場合に限って使えます。高次元インデックスを有効に使用するには、~~データは次元の広い範囲にわたり、ユーザが作ろうとするクエリの種類~~ユーザが作ろうとするクエリに対してデータが次元の広い範囲にわたっていなければなりません。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English Once you have data in higher dimensions it may make sense to index it. However, you should think carefully about the distribution of your data in all dimensions before applying a multi-dimensional index. Japanese 0 characters edited Current translation Translated 高次元データを持つと、インデックスを有効にすることになるかも知れません。しかしながら、多次元インデックスを適用する前に全ての次元内でのデータの分布について十分に検討するべきです。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English In addition to higher-dimensional forms of the standard types, PostGIS includes a few new types that make sense in a 3-D space: Japanese 5 characters edited Current translation Translated 標準タイプの高次元形式だけでなく、PostGISには3次元空間で意味を持つ新タイプが、は次の通り~~ありま~~です。 2 weeks ago
yellow73 Translation uploaded postgis-workshop / 3d — Japanese	English For 3-D and 4-D geometries, the extra dimensions are added as extra coordinates for each vertex in the geometry, and the geometry type is enhanced to indicate how to interpret the extra dimensions. Adding the extra dimensions results in three extra possible geometry types for each geometry primitive: Japanese 113 characters edited Current translation Translated 3次元と4次元のジオメトリでは、座標次元は頂点の座標値として追加され、追加次元をどう解釈するかを示すようにジオメトリタイプが拡張されます。追加次元によってプリミティブなジオメトリから三つずつの拡張ジオメトリタイプが作られます。 2 weeks ago

Browse all component changes