Source strings

61 Strings 100%
Browse Translate
1,634 Words 100%
10,453 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
61 1,634 10,453
All strings Browse Translate Zen
61 1,634 10,453
Read-only strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
geometry_returning 0 0 0 0 1 0 0
projection_exercises 0 0 0 0 8 0 0
simple_sql_exercises 0 0 0 0 13 0 0
tuning 0 0 0 0 6 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 1 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 dmateos User avatar yellow73 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 2 weeks ago
Last commit in Weblate Translated using Weblate (Japanese) 90ade02
Weblate Translation Memory authored 2 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/pot/topology.pot
Last change June 10, 2025, 6:58 p.m.
Last author None
2 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 100% 61 100% 1,634 100% 10,453
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 62 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 5 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

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

Trends of last 30 days

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

Resource updated

  1. postgis-workshop
  2. topology
  3. English
The "postgis-intro/sources/locale/pot/topology.pot" file was changed. 2 weeks ago
User avatar None

String added in the repository

  1. postgis-workshop
  2. topology
  3. English
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.
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.
2 weeks ago
User avatar None

String added in the repository

  1. postgis-workshop
  2. topology
  3. English
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:
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:
2 weeks ago
User avatar None

String added in the repository

  1. postgis-workshop
  2. topology
  3. English
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.
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.
2 weeks ago
User avatar None

String added in the repository

  1. postgis-workshop
  2. topology
  3. English
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.
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.
2 weeks ago
User avatar None

Resource updated

  1. postgis-workshop
  2. topology
  3. English
File postgis-intro/sources/locale/pot/topology.pot was added. a year ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. topology
  3. English
The result of the above is 29 neighborhoods were updated. If you rerun the border dispute queries for neighborhoods and boroughs, you'll find you have no more border disputes.
The result of the above is 29 neighborhoods were updated. If you rerun the border dispute queries for neighborhoods and boroughs, you'll find you have no more border disputes.
a year ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. topology
  3. English
Removing elements from Topogeometries is handled using the `TopoGeom_remElement <https://postgis.net/docs/TopoGeom_remElement.html>`_ function. So lets get on with it, removing duplicaed elements from neighborhoods with the most amount of area as follows:
Removing elements from Topogeometries is handled using the `TopoGeom_remElement <https://postgis.net/docs/TopoGeom_remElement.html>`_ function. So lets get on with it, removing duplicaed elements from neighborhoods with the most amount of area as follows:
a year ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. topology
  3. English
There are a number of ways we could fix this. We could go out surveying asking people what neighbhood do they think they are standing in. Alternatively we could just assign slivers of land to the neighborhood with the least amount of area or to the highest bidder.
There are a number of ways we could fix this. We could go out surveying asking people what neighbhood do they think they are standing in. Alternatively we could just assign slivers of land to the neighborhood with the least amount of area or to the highest bidder.
a year ago
User avatar None

String updated in the repository

  1. postgis-workshop
  2. topology
  3. English
Because boroughs are an aggregation of neighborhoods, we can fix the borough issue by fixing the neighborhood border disputes.
Because boroughs are an aggregation of neighborhoods, we can fix the borough issue by fixing the neighborhood border disputes.
a year ago
Browse all translation changes