Translation status

39 Strings 100%
Browse Translate
835 Words 100%
5,149 Characters 100%

Strings status

Strings Words Characters
39 835 5,149
All strings Browse Translate Zen
39 835 5,149
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
geography_exercises 0 0 0 0 0 0 0
projection_exercises 0 0 0 0 1 0 0
advanced_geometry_construction 0 0 0 0 0 0 0
simple_sql_exercises 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
clusterindex 0 0 0 0 0 0 0
loading_data 0 0 0 0 0 0 0
about_data 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 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 #141 from osgeoweblate/weblate-postgis-workshop-index 742f800
Regina Obe authored 2 weeks ago
Last commit in Weblate Translated using Weblate (Chinese (Simplified)) 99c5eb6
Wangdapeng authored 3 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/3d.po
Translation file Download postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/3d.po
Last change April 1, 2025, 9:39 a.m.
Last author None
9 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 39 835 5,149
Translated 100% 39 100% 835 100% 5,149
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 23 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

835
Hosted words
39
Hosted strings
100%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
Changes committed 3 weeks ago
User avatar xinbo

Translation completed

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
Translation completed 3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
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.
查询结果应当保持一致。需注意的是，N维索引的性能通常略低于二维索引，因此建议仅在以下场景使用。
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
To search the ``nyc_streets`` table using the N-D index, just replace the usual ``&&`` 2-D index operator with the ``&&&`` operator.
要在 ``nyc_streets`` 表中启用N维索引搜索，只需将常规的二维索引运算符``&&`` 替换为多维运算符``&&&`` 即可。
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
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.
建立索引后，即可在查询中使用 ``&&&``索引运算符。 ``&&&``与``&&``具有相同的"边界框相交"语义，但会应用在输入几何图形的所有维度上。需注意：维度不匹配的几何图形将被判定为不相交。
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
The ``gist_geometry_ops_nd`` parameter tells PostGIS to use the N-D index instead of the standard 2-D index.
参数 ``gist_geometry_ops_nd`` 用于指示 PostGIS 启用N维索引而非标准的二维索引。
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
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,
您可以为任意维度的数据（甚至混合维度数据）创建多维索引。例如，在``nyc_streets``表上创建多维索引的方法如下，
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
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.
在X/Y/时间三维空间中的GPS轨迹数据，若满足以下条件则可成为三维索引的理想应用场景：当轨迹数据在所有维度上均存在频繁重叠（例如车辆在不同时段重复行驶相同路线），此时数据集在各维度上均会呈现显著的可变性。
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
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.
数字高程模型（DEM）点集数据通常*不适合*建立三维索引，因为绝大多数查询仅涉及二维空间范围的点提取，极少需要按高程值（Z轴切片）进行筛选。
3 weeks ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. 3d
  3. Chinese (Simplified)
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.
索引的有效性取决于其通过WHERE条件大幅减少返回行数的能力。对于高维索引而言，只有当数据在相关维度上具有足够大的值域范围（相对于查询条件的设计）时，索引才能发挥效用。
3 weeks ago
Browse all translation changes