Overview

Project website postgis.net
Project maintainers User avatar komzpa User avatar cvvergara User avatar strk User avatar robe
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://git.osgeo.org/gitea/postgis/postgis.git
Repository branch master
Last remote commit Have skip signature generator scan full postgis upgrade script 5e05bc3e7
Sandro Santilli authored 17 hours ago
Last commit in Weblate Translated reference_coverage using Weblate (French) af45bca00
Vincent Bre authored 3 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis/postgis/
File mask doc/po/*/using_postgis_query.xml.po
Translation file Download doc/po/ru/using_postgis_query.xml.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 109 2,128 16,517
Approved 0% 0 0% 0 0% 0
Waiting for review 0% 0 0% 0 0% 0
Translated 0% 0 0% 0 0% 0
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 100% 109 100% 2,128 100% 16,517
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 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 20 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

2,128
Hosted words
109
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

New strings to translate

postgis / using_postgis_query.xml — Russian

18 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

postgis / using_postgis_query.xml — Russian

The "doc/po/ru/using_postgis_query.xml.po" file was changed. a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

SELECT gid, name, ST_Area(geom) AS area
FROM bc_municipality
WHERE ST_NRings(geom) > 1
ORDER BY area DESC LIMIT 1;

gid | name | area
-----+--------------+------------------
12 | SPALLUMCHEEN | 257374619.430216
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

SELECT
sum(ST_Length(r.geom))/1000 AS kilometers
FROM bc_roads r
JOIN bc_municipality m
ON ST_Intersects(m.geom, r.geom
WHERE
r.name = 'Douglas St'
AND m.name = 'VICTORIA';

kilometers
------------------
4.89151904172838
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

CREATE TABLE pg_roads as
SELECT
ST_Intersection(r.geom, m.geom) AS intersection_geom,
ST_Length(r.geom) AS rd_orig_length,
r.*
FROM bc_roads AS r
JOIN bc_municipality AS m
ON ST_Intersects(r.geom, m.geom)
WHERE
m.name = 'PRINCE GEORGE';
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

This is an example of an "overlay", which takes in two tables and outputs a new table that consists of spatially clipped or cut resultants. Unlike the "spatial join" demonstrated above, this query creates new geometries. An overlay is like a turbo-charged spatial join, and is useful for more exact analysis work:
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

This query takes a while, because every road in the table is summarized into the final result (about 250K roads for the example table). For smaller datsets (several thousand records on several hundred) the response can be very fast.
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

SELECT
m.name,
sum(ST_Length(r.geom))/1000 as roads_km
FROM bc_roads AS r
JOIN bc_municipality AS m
ON ST_Contains(m.geom, r.geom)
GROUP BY m.name
ORDER BY roads_km;

name | roads_km
----------------------------+------------------
SURREY | 1539.47553551242
VANCOUVER | 1450.33093486576
LANGLEY DISTRICT | 833.793392535662
BURNABY | 773.769091404338
PRINCE GEORGE | 694.37554369147
...
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

This is an example of a "spatial join", which brings together data from two tables (with a join) using a spatial interaction ("contained") as the join condition (rather than the usual relational approach of joining on a common key):
 
a year ago
User avatar None

String updated in the repository

postgis / using_postgis_query.xml — Russian

Note that in order to answer this query we have to calculate the area of every polygon. If we were doing this a lot it would make sense to add an area column to the table that could be indexed for performance. By ordering the results in a descending direction, and them using the PostgreSQL "LIMIT" command we can easily select just the largest value without using an aggregate function like MAX().
 
a year ago
Browse all translation changes