Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-3.0-US 0 0 0 0 3 0 0
German CC-BY-3.0-US 0% 209 5,958 38,078 209 0 2 0
Japanese CC-BY-3.0-US 0 0 0 0 0 0 0
Korean CC-BY-3.0-US 0% 209 5,958 38,078 209 0 2 0
Spanish CC-BY-3.0-US 1% 208 5,957 38,068 208 0 0 0
Swedish CC-BY-3.0-US 0 0 0 0 4 0 0
Please sign in to see the alerts.

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar yellow73 User avatar jef User avatar cvvergara User avatar astrid_emde User avatar dmateos 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 4 weeks ago
Last commit in Weblate Translated using Weblate (Spanish) 71b2709
Weblate authored 3 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/rasters.po
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,254 35,748 228,468
Source 209 5,958 38,078
Translated 50% 628 50% 17,875 50% 114,244
Needs editing 0% 0 0% 0 0% 0
Read-only 16% 209 16% 5,958 16% 38,078
Failing checks 1% 7 1% 157 1% 1,050
Strings with suggestions 1% 4 1% 4 1% 44
Untranslated strings 49% 626 49% 17,873 49% 114,224
Last 12 months Previous

Activity in last 12 months

0 changes 1 change 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 53 changes 31 changes 0 changes 213 changes 0 changes 205 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 2 changes 470 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

35,748
Hosted words
1,254
Hosted strings
50%
Translated
3
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. rasters
  3. Spanish
Changes committed 3 weeks ago
User avatar paulo

Suggestion accepted

  1. postgis-workshop
  2. rasters
  3. Spanish
Statistics
Estadísticas
3 weeks ago
User avatar paulo

Contributor joined

  1. postgis-workshop
  2. rasters
  3. Spanish
Contributor joined 3 weeks ago
User avatar None

Changes committed

  1. postgis-workshop
  2. rasters
  3. Swedish
Changes committed 3 weeks ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. rasters
  3. Swedish
PostGIS raster comes packaged with a number of functions for editing rasters. These functions are both used for editing as well as creating derivative raster data sets. You will find these listed in `Raster Editors <https://postgis.net/docs/RT_reference.html#Raster_Editors>`_ and `Raster Management <https://postgis.net/docs/RT_reference.html#Raster_Management_Functions>`_.
PostGIS raster levereras med ett antal funktioner för att redigera raster. Dessa funktioner används både för att redigera och för att skapa derivata rasterdatauppsättningar. Du hittar dessa listade i `Raster Editors-redigerare <https://postgis.net/docs/RT_reference.html#Raster_Editors>`_ och `Raster Management <https://postgis.net/docs/RT_reference.html#Raster_Management_Functions>`_.
3 weeks ago
User avatar None

Changes committed

  1. postgis-workshop
  2. rasters
  3. Swedish
Changes committed 3 weeks ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. rasters
  3. Swedish
If this were a classification scheme we preferred, we could create a new table using the ST_Reclass to recompute each tile.
Om det här var ett klassificeringssystem som vi föredrog skulle vi kunna skapa en ny tabell med ST_Reclass för att räkna om varje brickplatta.
4 weeks ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. rasters
  3. Swedish
The `overview_factor` tells you at what resolution the row is with respect to it's parent. An `overview_factor` of `2` means that 2x2 = 4 tiles can fit into one overview_2 tile. Similarly an overview_factor of `3` meants that 2x2x2 = 8 tiles of the original can be shoved into an overview_3 tile.
Overview-faktorn anger vilken upplösning raden har i förhållande till sin överordnade enhet. En `overview_factor` på `2` innebär att 2x2 = 4 brickplattor får plats på en overview_2-brickplatta. På samma sätt innebär en overview_factor på `3` att 2x2x2 = 8 brickplattor av originalet kan tryckas in i en overview_3-brickplatta.
4 weeks ago
User avatar yeager

Translation replaced

  1. postgis-workshop
  2. rasters
  3. Swedish
A better approach, albeit a bit slower, is to define your own coverage tile structure from scratch using `ST_MakeEmptyCoverage <https://postgis.net/docs/RT_ST_MakeEmptyCoverage.html>`_ and then find the intersecting tiles for each new tile, and ST_Union these and then use `ST_Transform(ref, ST_Union...)` to create each tile.
Ett bättre tillvägagångssätt, om än lite långsammare, är att definiera din egen täckningsstruktur från början med `ST_MakeEmptyCoverage <https://postgis.net/docs/RT_ST_MakeEmptyCoverage.html>`_ och sedan hitta de korsande plattorna för varje ny kakelplatta, och ST_Union dessa och sedan använda `ST_Transform(ref, ST_Union...)` för att skapa varje kakelplatta.
4 weeks ago
User avatar yeager

Translation replaced

  1. postgis-workshop
  2. rasters
  3. Swedish
You'll often hear in PostGIS lingo, the term **raster tile** and **raster** used somewhat interchangeably. A raster tile really corresponds to a particular raster in a raster column which is a subset of a bigger raster, such as this NYC dem data we just loaded. This is because when rasters are loaded into PostGIS from big raster files, they chopped into many rows to make them manageable. Each raster in each row then is a part of a bigger raster. Each tile covers same size area denoted by the blocksize you specified. Rasters are sadly limited by the 1GB PostgreSQL `TOAST <https://www.postgresql.org/docs/current/storage-toast.html>`_ limit and also the slow process of detoasting and so we need to chop up in order to achieve decent performance or to even store them.
I PostGIS-lingo används ofta termerna **raster tile** och **raster** omväxlande. En rasterplatta motsvarar egentligen ett visst raster i en rasterkolumn som är en delmängd av ett större raster, till exempel NYC dem-data som vi just laddade. Detta beror på att när raster laddas in i PostGIS från stora rasterfiler, hackas de i många rader för att göra dem hanterbara. Varje raster i varje rad är då en del av ett större raster. Varje kakelplatta täcker samma storlek på området som anges av den blockstorlek du angav. Rasters är tyvärr begränsade av 1 GB PostgreSQL `TOAST <https://www.postgresql.org/docs/current/storage-toast.html>`_-gränsen och även den långsamma processen med detoasting och så måste vi hugga upp för att uppnå anständig prestanda eller till och med lagra dem.
4 weeks ago
Browse all component changes