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=46
{ "count": 2273, "next": null, "previous": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/changes/?format=api&page=45", "results": [ { "unit": "https://weblate.osgeo.org/api/units/1514391/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.085048Z", "action": 59, "target": "What is this same alignment thing, that is preventing you from unioning your precious rasters?", "id": 1096489, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096489/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514390/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.084974Z", "action": 59, "target": "**ERROR: rt_raster_from_two_rasters: The two rasters provided do not have the same alignment SQL state: XX000**", "id": 1096488, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096488/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514389/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.084901Z", "action": 59, "target": "You'd be summarily punished with an error:", "id": 1096487, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096487/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514387/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.084752Z", "action": 59, "target": "The `ST_Union <https://postgis.net/docs/RT_ST_Union.html>`_ function for raster, just as the geometry equivalent :command:`ST_Union`, aggregates a set of rasters together into a single raster. However, just as with geometry, not all rasters can be combined together, but the rules for raster unioning are more complicated than geometry rules. In the case of geometries, all you need is to have the same spatial reference system, but for rasters that is not sufficient.", "id": 1096485, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096485/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514383/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.084429Z", "action": 59, "target": "Observe the metadata of the New York entries. They have the New York state plane meter spatial reference system. They also have the same scale. Since each unit is 1x1 meter, the width of the word **Raster** is now wider than **Hello**.", "id": 1096481, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096481/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514382/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.084356Z", "action": 59, "target": "What is more telling, if we rerun the", "id": 1096480, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096480/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514378/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.084044Z", "action": 59, "target": "You can think of a rasters exoskeletal as a geometry. A matrix encased in a geometric envelop. In order to do useful analysis, we need to georeference our rasters, meaning we want each pixel (rectangle) to represent some meaningful plot of space.", "id": 1096476, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096476/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514377/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083971Z", "action": 59, "target": "For the rasters created thus far, we didn't specify the number of bands nor did we even define their relation to earth. As such our rasters have an unknown spatial reference system (0).", "id": 1096475, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096475/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514376/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083897Z", "action": 59, "target": "Run the below query and copy and paste the output into the address bar of your web browser.", "id": 1096474, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096474/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514375/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083824Z", "action": 59, "target": "Each new connection to the database will use that setting.", "id": 1096473, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096473/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514374/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083749Z", "action": 59, "target": "If you don't want to have to do this for each connection, you can set at the database level using:", "id": 1096472, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096472/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514371/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083490Z", "action": 59, "target": "Viewing Rasters in Browser", "id": 1096469, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096469/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514370/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083351Z", "action": 59, "target": "Note how all the rasters have a 150x150 dimension. This is not ideal. This means that in order to force that, our rasters, are squished in all sorts of ways. If only we could see the ugliness of the rasters before us.", "id": 1096468, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096468/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514366/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.083054Z", "action": 59, "target": "We'll start off by first creating raster data from vector data, and then move on to the more exciting approach of loading data from a raster source. You will find that raster data is available in abundance and often free from various government sites.", "id": 1096464, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096464/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514365/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.082982Z", "action": 59, "target": "Creating Rasters From Geometries", "id": 1096463, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096463/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514361/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.082676Z", "action": 59, "target": "Although pretty pictures such as those you see on your TV screen are rasters, rasters may not be that exciting to look at. In a nutshell, a raster is a matrix, pinned on a coordinate system, that has values that can represent anything you want them to represent.", "id": 1096459, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096459/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514360/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.082595Z", "action": 59, "target": "PostGIS supports another kind of spatial data type called a *raster*. Raster data, much like geometry data, uses **Cartesian coordinates** and a spatial reference system. However instead of vector data, raster data is represented as an n-dimensional matrix consisting of pixels and bands. The bands defines the number of matrices you have. Each pixel stores a value corresponding to each band. So a 3-banded raster such as an RGB image, would have 3 values for each pixel corresponding to the Red-Green-Blue bands.", "id": 1096458, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096458/?format=api" }, { "unit": "https://weblate.osgeo.org/api/units/1514359/?format=api", "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/rasters/en/?format=api", "user": null, "author": null, "timestamp": "2023-01-08T03:23:27.082444Z", "action": 59, "target": "Rasters", "id": 1096457, "action_name": "String updated in the repository", "url": "https://weblate.osgeo.org/api/changes/1096457/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": null, "user": null, "author": null, "timestamp": "2023-01-08T03:23:25.914635Z", "action": 60, "target": "weblate.autotranslate.autotranslate", "id": 1096456, "action_name": "Add-on installed", "url": "https://weblate.osgeo.org/api/changes/1096456/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": null, "user": null, "author": null, "timestamp": "2023-01-08T03:23:25.902678Z", "action": 60, "target": "weblate.gettext.authors", "id": 1096455, "action_name": "Add-on installed", "url": "https://weblate.osgeo.org/api/changes/1096455/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": null, "user": null, "author": null, "timestamp": "2023-01-08T03:23:25.891334Z", "action": 60, "target": "weblate.gettext.customize", "id": 1096454, "action_name": "Add-on installed", "url": "https://weblate.osgeo.org/api/changes/1096454/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": null, "user": null, "author": null, "timestamp": "2023-01-08T03:23:25.807771Z", "action": 60, "target": "weblate.gettext.msgmerge", "id": 1096453, "action_name": "Add-on installed", "url": "https://weblate.osgeo.org/api/changes/1096453/?format=api" }, { "unit": null, "component": "https://weblate.osgeo.org/api/components/postgis-workshop/rasters/?format=api", "translation": null, "user": null, "author": null, "timestamp": "2023-01-08T03:23:25.792628Z", "action": 51, "target": "", "id": 1096452, "action_name": "Component created", "url": "https://weblate.osgeo.org/api/changes/1096452/?format=api" } ] }