Summary

Project website postgis.net
Project maintainers4 User avatar robeUser avatar strkUser avatar cvvergaraUser avatar komzpa
Project reviewers13 User avatar robeUser avatar strkUser avatar cvvergaraUser avatar dkastlUser avatar komzpaUser avatar astrid_emdeUser avatar jsanzUser avatar andischiUser avatar yoichiUser avatar jefUser avatar thayerayUser avatar yellow73User avatar jonnyforest
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • 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 Fix X3D 2D polygon serialization 226a7ef5
Darafei Praliaskouski authored 06/20/2026
Last commit in Weblate Translated PostGIS Manual using Weblate (Japanese) ac4a2e17
User avatar yellow73 authored 06/22/2026
Weblate repository https://weblate.osgeo.org/git/postgis/postgis-manual/
File mask doc/po/*/postgis-manual.po
Translation file Download doc/po/sv/postgis-manual.po
Last change June 18, 2026, 1:33 p.m.
Last change made by None
Language Swedish
Language code sv
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 13,338,376
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
06/22/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 5,579 99,720 713,033
Approved 0% 0 0% 0 0% 0
Waiting for review 96% 5,359 94% 94,171 94% 671,677
Translated 96% 5,359 94% 94,171 94% 671,677
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 7% 410 4% 4,721 5% 37,956
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 3% 220 5% 5,549 5% 41,356
Last 12 months Previous

Activity in last 12 months

0 changes 12,483 changes 0 changes 187 changes 0 changes 44 changes 0 changes 0 changes 0 changes 0 changes 0 changes 146 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 14 changes 0 changes 0 changes 0 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

99,720
Hosted words
5,579
Hosted strings
96%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
−1%
Translated
+97%
+100%
Contributors
—
User avatar komzpa

Resource updated
Parsing of the “doc/po/sv/postgis-manual.po” file was enforced. 06/18/2026
User avatar None

Resource updated
The “doc/po/sv/postgis-manual.po” file was changed. 06/13/2026
User avatar None

String added in the repository
If the optional <code>gridSize</code> parameter is given (GEOS-3.9.0 or higher required), all result vertices are guaranteed to fall on a snap-rounded grid of the specified size. Note that operations performed on a grid may contain small artifacts produced during grid alignment, see <xref linkend="ST_ReducePrecision"/>.
 
06/13/2026
User avatar None

String added in the repository
For example, consider a linear dataset representing a road network. It may be required to identify all road segments that cross each other, not at a point, but in a line (perhaps to validate a business rule such as ensuring that no two different roads share a common segment). In this case <xref linkend="ST_Crosses"/> does not provide the necessary spatial filter, since for linear features it returns <varname>true</varname> only where they cross at a point.
 
06/13/2026
User avatar None

String added in the repository
The coordinate dimension (2, 3 or 4) of the column. The coordinate dimension is at least 2, representing X and Y coordinates.
 
06/13/2026
User avatar None

String added in the repository
By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up well with local planar results in good local projections. Over larger areas, the spheroidal calculations will be more accurate than any calculation done on a projected plane. The difference is that the spheroid takes into account the curvature and non-spherical shape of the Earth, whereas planar calculations assume a flat surface.
 
06/13/2026
User avatar None

String added in the repository
The <varname>geometry</varname> data type is <emphasis>opaque</emphasis>, which means that all access is done via invoking functions on geometry values. Functions allow creating geometry objects, accessing or updating all internal fields, and computing new geometry values. PostGIS supports all the functions specified in the OGC <link xlink:href="https://portal.ogc.org/files/?artifact_id=25354"><emphasis>Simple feature access - Part 2: SQL option</emphasis></link> (SFS) specification, as well many others. See <xref linkend="reference"/> for the full list of functions.
 
06/13/2026
User avatar None

String added in the repository
A MultiPolygon is a collection of non-overlapping, non-adjacent Polygons. Polygons in the collection may touch only at a finite number of points. (Two polygons are adjacent if they share an edge. They touch if they share only points or edges on their boundaries). For more details on MultiPolygon validity, see <xref linkend="OGC_Validity"/>.
 
06/13/2026
User avatar None

String added in the repository
The OGC geometry model defines validity rules for each geometry type. These rules ensure that geometry values represents realistic situations (e.g. it is possible to specify a polygon with a hole lying outside its shell, but this makes no sense geometrically and is thus invalid). PostGIS also allows storing and manipulating invalid geometry values. This allows detecting and fixing them if needed. See <xref linkend="OGC_Validity"/>
 
06/13/2026
User avatar None

String added in the repository
The geometry model allows evaluating topological spatial relationships as described in <xref linkend="DE-9IM"/>. To support this the concepts of <emphasis role="bold">interior</emphasis>, <emphasis role="bold">boundary</emphasis> and <emphasis role="bold">exterior</emphasis> are defined for each geometry type. Geometries are topologically closed, so they always contain their boundary. The boundary is a geometry of dimension one less than that of the geometry itself. For example, the boundary of a Polygon is its rings (LineStrings), the boundary of a LineString is its endpoints (Points), and the boundary of a Point is empty.
 
06/13/2026
Browse all translation changes