Changes
Translation components API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/components/postgis-workshop/rasters/changes/?format=api&page=3
{ "count": 2273, "next": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/changes/?format=api&page=4", "previous": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/changes/?format=api&page=2", "results": [ { "unit": "https://weblate.osgeo.org/api/units/1515381/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:40:03.352295Z", "action": 5, "target": "Los raster pueden convertirse fácilmente en geometrías.", "id": 2216975, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216975/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514731/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:39:55.162830Z", "action": 5, "target": "Convirtiendo raster en geometrías", "id": 2216974, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216974/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/2274928/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:39:47.728053Z", "action": 5, "target": "De manera predeterminada ST_Clip dejará fuera píxeles donde el centroide del píxel no intersecta la geometría. Esto puede ser molesto para píxeles grandes y puede que prefieras en su lugar incluir un píxel si cualquier parte del píxel toca la geometría. Introducido en PostGIS 3.5, está el argumento touched. Reemplaza tu `ST_Clip(r.rast, g.geom)` con `ST_Clip(r.rast, g.geom, touched => true)` y voilà, cualquier píxel que intersecte tu geometría de cualquier forma será incluido.", "id": 2216973, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216973/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515380/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:39:28.013441Z", "action": 5, "target": "Este ejemplo muestra varias funciones trabajando en conjunto. La función :command:`ST_Intersects` empleada es la que viene con **postgis_raster** y puede intersectar 2 raster o un raster y una geometría. Similar a la función de geometría :command:`ST_Intersects`, el `raster ST_Intersects <https://postgis.net/docs/RT_ST_Intersects.html>`_ puede aprovechar los índices espaciales en las tablas raster o de geometría.", "id": 2216972, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216972/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514510/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:39:18.230368Z", "action": 5, "target": "Esta función es también especial en que utiliza el poder de la geometría para ayudar al análisis raster. Para reducir el número de píxeles que :command:`ST_Union` tiene que manejar, cada raster se recorta primero al área de interés.", "id": 2216971, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216971/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514509/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:39:11.916764Z", "action": 5, "target": "La función `ST_Clip <https://postgis.net/docs/RT_ST_Clip.html>`_ es una de las funciones más utilizadas para raster en PostGIS. La razón principal es que mientras más píxeles necesites inspeccionar o realizar operaciones, más lento será tu procesamiento. **ST_Clip** recorta tu raster solo al área de interés, para que puedas aislar tus operaciones únicamente a esa área.", "id": 2216970, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216970/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515379/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:39:04.483749Z", "action": 5, "target": "Recortando raster con ayuda de ST_Intersects", "id": 2216969, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216969/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514507/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:57.422745Z", "action": 5, "target": "Usar la variante *unionarg[]* de la función :command:`ST_Union`, también te permite reorganizar el orden de las bandas.", "id": 2216968, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216968/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514506/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:51.020496Z", "action": 5, "target": "O quizás quieras usar todas las bandas, pero quieres diferentes estrategias.", "id": 2216967, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216967/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514505/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:41.953990Z", "action": 5, "target": "En otros casos, el tipo de píxel de la banda no cambia y se establece en el valor máximo o se redondea si las cantidades exceden los límites del tipo. ¿Por qué alguien querría contar píxeles que se intersectan en una ubicación? Bueno, supongamos que cada uno de tus raster representa escuadrones de policía e incidentes de arrestos en las áreas. Cada valor podría representar una razón diferente de arresto. Estás haciendo estadísticas sobre cuántos arrestos en cada región, por lo tanto solo te importa el conteo de arrestos.", "id": 2216966, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216966/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514730/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:34.316551Z", "action": 5, "target": "Nota que en el caso del tipo de unión **COUNT**, que cuenta el número de píxeles rellenados y devuelve ese valor, el resultado es siempre un **32BUI** similar a cómo cuando haces un :command:`COUNT` en SQL, el resultado siempre es un bigint, para acomodar conteos grandes.", "id": 2216965, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216965/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514503/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:27.348418Z", "action": 5, "target": "Otra característica del raster :command:`ST_Union` que pasamos por alto, es esta idea de si deberías devolver todas las bandas o solo algunas bandas. Cuando no especificas qué bandas unir, :command:`ST_Union` combinará los números de las mismas bandas y usará la estrategia de unión :command:`LAST`. Si tienes múltiples bandas, esto puede no ser lo que quieras hacer. Quizás solo quieras unir la segunda banda. En este caso, la banda verde, y quieres el conteo de valores de píxel.", "id": 2216964, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216964/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514729/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:19.654541Z", "action": 5, "target": "Ten en cuenta que para geometrías, dado que las geometrías son vectores y, por lo tanto, no tienen valores aparte de estar o no estar, realmente no hay ambigüedad sobre cómo combinar dos vectores cuando se intersectan.", "id": 2216963, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216963/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514728/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:38:11.491662Z", "action": 5, "target": "Así que en lugar de imponerse, tenemos una mezcla de las dos fuerzas. En el caso del tipo de unión :command:`MEAN`, no tiene sentido especificar el orden, porque el resultado sería el promedio de los valores de píxeles superpuestos.", "id": 2216962, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216962/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514727/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:37:14.485846Z", "action": 5, "target": "Pero en ocasiones, **LAST** puede no ser la operación correcta. Supongamos que nuestros raster representan dos conjuntos diferentes de observaciones de dos dispositivos distintos. Estos dispositivos miden lo mismo, y no estamos seguros de cuál es correcto cuando se cruzan, por lo que en su lugar nos gustaría tomar el `MEAN` de los resultados. Haríamos esto:", "id": 2216961, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216961/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514726/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:37:07.020718Z", "action": 5, "target": "El tipo de unión :command:`FIRST` es lo contrario de :command:`LAST`.", "id": 2216960, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216960/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514725/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:59.978326Z", "action": 5, "target": "Entonces *Hello* vence a *Raster* porque Hello ahora es el último superpuesto.", "id": 2216959, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216959/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514724/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:50.319113Z", "action": 5, "target": "Observa, si cambias el orden:", "id": 2216958, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216958/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514723/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:42.425140Z", "action": 5, "target": "Al igual que con la mayoría de los agregados en PostgreSQL, puedes poner una cláusula :command:`ORDER BY` como parte de la llamada a la función, como se hace en el ejemplo anterior. Especificar el orden te permite controlar qué raster tiene prioridad. Así que en nuestro ejemplo anterior, *Raster* venció a *Hello* porque *Raster* es alfabéticamente el último.", "id": 2216957, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216957/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514869/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:34.435332Z", "action": 5, "target": "Una forma importante en que la función `ST_Union(raster) <https://postgis.net/docs/RT_ST_Union.html>`_ difiere de la función `ST_Union(geometry) <https://postgis.net/docs/ST_Union.html>`_ es que permite un argumento llamado *uniontype*. Este argumento por defecto se establece en `LAST` si no lo especificas, lo que significa tomar los valores de píxeles del **LAST** raster en las ocasiones donde los valores de píxeles raster se superponen. Como regla general, los píxeles en una banda que están marcados como no-data se ignoran.", "id": 2216956, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216956/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514499/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:26.224660Z", "action": 5, "target": "Si alguna vez no tienes claro por qué tus raster no tienen el mismo alineamiento, puedes usar la función `ST_SameAlignment <https://postgis.net/docs/RT_ST_SameAlignment.html>`_, que comparará 2 raster o un conjunto de raster y te dirá si tienen el mismo alineamiento. Si tienes los avisos habilitados, el NOTICE te dirá qué está mal con los raster en cuestión. La función `ST_NotSameAlignmentReason <https://postgis.net/docs/RT_ST_NotSameAlignmentReason.html>`_, en lugar de solo un aviso, devolverá la razón. Sin embargo, solo funciona con dos raster a la vez.", "id": 2216955, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216955/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514498/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:18.358330Z", "action": 5, "target": "Voilà, funcionó, y si lo viéramos, veríamos algo como esto:", "id": 2216954, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216954/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514497/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:11.106128Z", "action": 5, "target": "Podemos arreglar esto ajustando ligeramente las coordenadas superiores izquierdas en y y luego probando de nuevo. Si nuestras grillas comienzan a nivel entero, ya que nuestros tamaños de píxel son enteros, entonces los píxeles no se cortarán entre sí.", "id": 2216953, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216953/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514496/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:36:03.045851Z", "action": 5, "target": "De nuevo, el mismo error. Estos son el mismo sistema de referencia espacial, los mismos tamaños de píxel, y aun así no es suficiente. Porque sus grillas no coinciden.", "id": 2216952, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216952/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514495/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:55.825821Z", "action": 5, "target": "Si intentas la misma consulta, pero solo con palabras que colocamos cuidadosamente en Nueva York.", "id": 2216951, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216951/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514494/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:47.913807Z", "action": 5, "target": "Para que los raster se combinen, deben estar en la misma grilla por así decirlo. Esto significa que deben tener los mismos tamaños de píxel, la misma orientación (la inclinación), el mismo sistema de referencia espacial, y sus píxeles no deben cortarse entre sí, es decir, deben compartir la misma grilla de píxeles en el mundo.", "id": 2216950, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216950/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514492/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:36.178673Z", "action": 2, "target": "**ERROR: rt_raster_from_two_rasters: The two rasters provided do not have the same alignment SQL state: XX000**", "id": 2216949, "action_name": "Translation changed", "url": "https://weblate.osgeo.org/api/changes/2216949/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514493/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:32.038309Z", "action": 5, "target": "¿Qué es esto del mismo alineamiento, que impide unir tus preciados raster?", "id": 2216948, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216948/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514492/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:14.676760Z", "action": 5, "target": "**ERROR: rt_raster_from_two_rasters: The two rasters provided do not have the same alignment SQL state: XX000**", "id": 2216947, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216947/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514491/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:09.073316Z", "action": 5, "target": "Serías castigado inmediatamente con un error:", "id": 2216946, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216946/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515617/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:35:03.125742Z", "action": 5, "target": "Si intentaras lo siguiente:", "id": 2216945, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216945/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514489/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:34:54.878650Z", "action": 5, "target": "La función `ST_Union <https://postgis.net/docs/RT_ST_Union.html>`_ para raster, al igual que su equivalente en geometría :command:`ST_Union`, agrega un conjunto de raster en un solo raster. Sin embargo, al igual que con geometría, no todos los raster pueden combinarse, pero las reglas para unir raster son más complicadas que las reglas de geometría. En el caso de geometrías, todo lo que necesitas es tener el mismo sistema de referencia espacial, pero para raster eso no es suficiente.", "id": 2216944, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216944/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515378/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:34:47.746893Z", "action": 5, "target": "Uniendo rasters con ST_Union", "id": 2216943, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216943/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515757/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:34:29.246536Z", "action": 5, "target": "Finalmente necesitas :command:`ST_Intersects` o :command:`&&` para acercarte a los tiles raster que contienen tus áreas de interés. El operador `&&` es un proceso más rápido que :command:`ST_Intersects`. Ambos pueden aprovechar los índices espaciales raster. Cubriremos estas funciones esenciales primero antes de pasar a otras secciones donde las usaremos en conjunto con otras funciones raster y de geometría.", "id": 2216942, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216942/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515756/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:34:17.029491Z", "action": 5, "target": "Necesitas una función como :command:`ST_Union` para reconstituir una región. Debido a que el rendimiento se vuelve lento mientras más píxeles necesita analizar una función, necesitas una función de acción rápida :command:`ST_Clip` para recortar los raster solo a las porciones de interés para tu análisis.", "id": 2216941, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216941/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515614/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:33:28.618734Z", "action": 5, "target": "Además de esas funciones superpuestas, soporta el operador `&&` de solapamiento entre rasters y entre un raster y una geometría. También ofrece muchas funciones que trabajan en conjunto con geometría o que son muy específicas de raster.", "id": 2216940, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216940/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515613/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:33:15.185639Z", "action": 5, "target": "La extensión :command:`postgis_raster` tiene más de 100 funciones para elegir. La funcionalidad raster de PostGIS fue diseñada siguiendo el soporte de geometría de PostGIS. Encontrarás una superposición de funciones entre raster y geometría donde tiene sentido. Algunas comunes que usarás y que tienen equivalentes en el mundo de geometría son: :command:`ST_Intersects`, :command:`ST_SetSRID`, :command:`ST_SRID`, :command:`ST_Union`, :command:`ST_Intersection`, y :command:`ST_Transform`.", "id": 2216939, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216939/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515374/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:33:07.443248Z", "action": 5, "target": "Funciones raster comunes", "id": 2216938, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216938/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/2274927/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:33:01.590808Z", "action": 5, "target": "El `overview_factor` te dice en qué resolución está la fila con respecto a su padre. Un `overview_factor` de `2` significa que 2x2 = 4 tiles pueden caber en un tile overview_2. De manera similar, un overview_factor de `3` significa que 2x2x2 = 8 tiles del original pueden agruparse en un tile overview_3.", "id": 2216937, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216937/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515106/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:32:54.777094Z", "action": 5, "target": "La tabla `raster_overviews` solo te proporciona el overview_factor y el nombre de la tabla padre. Toda esta información es algo que podrías haber deducido tú mismo por la convención de nombres de `raster2pgsql` para overviews.", "id": 2216936, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216936/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515105/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:32:46.691911Z", "action": 5, "target": "y verás la salida:", "id": 2216935, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216935/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515104/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:32:38.476702Z", "action": 5, "target": "Para inspeccionar los overviews, ejecuta:", "id": 2216934, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216934/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515103/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:32:30.322843Z", "action": 5, "target": "Las columnas de raster overview aparecen tanto en el meta-catálogo `raster_columns` como en otro meta-catálogo llamado `raster_overviews`. Los overviews se usan principalmente para acelerar la visualización en niveles de zoom altos. También pueden usarse para análisis rápidos y aproximados, proporcionando estadísticas menos precisas, pero a una velocidad mucho mayor que al aplicar sobre la tabla raster original.", "id": 2216933, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216933/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515102/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:32:10.464820Z", "action": 5, "target": "raster_overviews", "id": 2216932, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216932/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514719/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:32:07.214391Z", "action": 5, "target": "Por ejemplo, si planeas cargar más datos en tu tabla raster, querrás omitir la restricción de extensión ya que eso requeriría que todos los raster estén dentro de la extensión de la restricción.", "id": 2216931, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216931/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514718/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:31:59.849857Z", "action": 5, "target": "Cuanto más puedas restringir todos tus raster, más columnas verás llenas y también más operaciones podrás realizar en todos los tiles de tu raster. Ten en cuenta que en algunos casos puede que no quieras aplicar todas las restricciones.", "id": 2216930, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216930/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514717/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:31:53.311740Z", "action": 5, "target": "Ah, progreso:", "id": 2216929, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216929/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514716/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:31:47.062234Z", "action": 5, "target": "Podemos quizás hacer esto, digamos simplemente que todos nuestros datos están en el sistema de coordenadas state plane de Nueva York.", "id": 2216928, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216928/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514715/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:31:40.915939Z", "action": 5, "target": "Para que las restricciones puedan aplicarse, todos los raster en tu tabla deben ser restringibles por al menos una regla.", "id": 2216927, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216927/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1515101/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/es/?format=api", "user": "https://weblate.osgeo.org/api/users/paulo/?format=api", "author": "https://weblate.osgeo.org/api/users/paulo/?format=api", "timestamp": "2025-09-02T07:31:34.802511Z", "action": 5, "target": "Y serás bombardeado con un montón de avisos sobre cómo tus datos raster son un desastre y nada puede ser restringido. Si vuelves a mirar raster_columns, todavía la misma decepcionante historia de muchas filas en blanco para `rasters`.", "id": 2216926, "action_name": "Translation added", "url": "https://weblate.osgeo.org/api/changes/2216926/?format=api" } ] }