| 20 | | * RASTER is a new column type (like the PostGIS GEOMETRY type) |
| 21 | | * one table with a column of type raster = one raster coverage (like a one table PostGIS vector coverage) |
| 22 | | * one table row with a column of type raster = one tile (like a vector coverage in which one row = one geometry) |
| 23 | | * each tile has: a pixel size, a width and a height, a georeference, a certain number of band, a pixeltype per band and a nodata value per band; everything essential to do basic GIS raster operations. |
| 24 | | |
| 25 | | * '''is an extension of PostGIS to be installed separately''' |
| | 19 | * RASTER is a new column type (like the PostGIS GEOMETRY type) |
| | 20 | * one table with a column of type raster = one raster coverage (like a one table PostGIS vector coverage) |
| | 21 | * one table row with a column of type raster = one tile (like a vector coverage in which one row = one geometry) |
| | 22 | * each tile has: a pixel size, a width and a height, a georeference, a certain number of band, a pixeltype per band and a nodata value per band; everything essential to do basic GIS raster operations. |
| | 23 | |
| | 24 | '''...is an extension of PostGIS to be installed separately...''' |
| 29 | | * '''has a loader similar to shp2pgsql.exe (gdal2wktraster.py)...''' |
| 30 | | |
| 31 | | * allowing loading of a single raster or a set of rasters (using wildcard) into a tiled coverage. |
| 32 | | * supporting as many file format as GDAL does. |
| 33 | | |
| 34 | | * '''allows easy conversion from raster to geometry...''' |
| 35 | | |
| 36 | | * RT_AsPolygon(raster) -> geometry |
| 37 | | |
| 38 | | * '''introduces raster/geometry seamless geometry constructors...''' |
| 39 | | |
| 40 | | * so you don't have to bother whether the layers you are working with are in raster or vector form when using analysis functions. |
| 41 | | |
| 42 | | * RT_Intersection(raster|geometry, raster|geometry, "raster"|"geometry") -> raster/geometry |
| 43 | | |
| 44 | | * '''and seamless geometry operators...''' |
| 45 | | |
| 46 | | * raster|geometry && raster|geometry -> boolean |
| 47 | | * RT_Intersects(raster|geometry, raster|geometry) -> boolean |
| 48 | | |
| 49 | | * '''allows raster storage INSIDE the database (as WKB)...''' |
| 50 | | |
| 51 | | * for efficient overlay analysis operations between vector and raster layers... |
| 52 | | |
| 53 | | * '''or OUTSIDE the database (as JPEG or TIFF)...''' |
| 54 | | |
| 55 | | * so desktop and web applications can quickly access and load raster tiles and nevertheless benefits from the powerful PostGIS GiST spatial index. Every WKT Raster SQL functions working with in-the-db raster tiles work seamlessly with out-the-db raster tiles. |
| 56 | | |
| 57 | | * '''is much more simple than PGRaster and Oracle GeoRaster! WKT Raster supports...''' |
| 58 | | |
| 59 | | * only one type (instead of two in Oracle Spatial: SDO_GEORASTER & SDO_RASTER). In WKT Raster there are no differences between rasters and tiles: a tile is a raster and a raster is a tile. i.e. one row = one tile = one raster; one table = one raster coverage. |
| 60 | | * no metadata (like PostGIS) |
| 61 | | * no masks (you can create a mask as a band) |
| 62 | | * no multiple dimensions (only two: x, y) |
| 63 | | * no pyramids (reduced resolution coverages can be stored as a separate layer) |
| | 28 | '''...has a loader similar to shp2pgsql.exe (gdal2wktraster.py)...''' |
| | 29 | |
| | 30 | * allowing loading of a single raster or a set of rasters (using wildcard) into a tiled coverage. |
| | 31 | * supporting as many file format as GDAL does. |
| | 32 | |
| | 33 | '''...allows easy conversion from raster to geometry...''' |
| | 34 | |
| | 35 | * RT_AsPolygon(raster) -> geometry |
| | 36 | |
| | 37 | '''...introduces raster/geometry seamless geometry constructors...''' |
| | 38 | |
| | 39 | * so you don't have to bother whether the layers you are working with are in raster or vector form when using analysis functions. |
| | 40 | |
| | 41 | * RT_Intersection(raster|geometry, raster|geometry, "raster"|"geometry") -> raster/geometry |
| | 42 | |
| | 43 | '''...and seamless geometry operators...''' |
| | 44 | |
| | 45 | * raster|geometry && raster|geometry -> boolean |
| | 46 | * RT_Intersects(raster|geometry, raster|geometry) -> boolean |
| | 47 | |
| | 48 | '''...allows raster storage INSIDE the database (as WKB)...''' |
| | 49 | |
| | 50 | * for efficient overlay analysis operations between vector and raster layers... |
| | 51 | |
| | 52 | '''...or OUTSIDE the database (as JPEG or TIFF)...''' |
| | 53 | |
| | 54 | * so desktop and web applications can quickly access and load raster tiles and nevertheless benefits from the powerful PostGIS GiST spatial index. Every WKT Raster SQL functions working with in-the-db raster tiles work seamlessly with out-the-db raster tiles. |
| | 55 | |
| | 56 | '''...is much more simple than PGRaster and Oracle GeoRaster! WKT Raster supports...''' |
| | 57 | |
| | 58 | * only one type (instead of two in Oracle Spatial: SDO_GEORASTER & SDO_RASTER). In WKT Raster there are no differences between rasters and tiles: a tile is a raster and a raster is a tile. i.e. one row = one tile = one raster; one table = one raster coverage. |
| | 59 | * no metadata (like PostGIS) |
| | 60 | * no masks (you can create a mask as a band) |
| | 61 | * no multiple dimensions (only two: x, y) |
| | 62 | * no pyramids (reduced resolution coverages can be stored as a separate layer) |
