| 375 | | We have used the most powerfull vector database engine around (PostGIS) to intersect our data buffers with a big raster datasets. For those who already know PostGIS, most of the queries are very familiar. For the newcomers, they might appear a bit complicated, but the speed at which we get the resulting table is worth the effort. The longuest step was to load the data. Once this is done, we can make as many quick queries as we wish. PostGIS with WKT Raster is a serious tool for accomplishing serious analysis work. |
| 376 | | |
| 377 | | You can find more info on PostGIS WKT Raster [wiki:WKTRaster in this page]. All the functions are documented in the [http://postgis.refractions.net/documentation/manual-svn/RT_reference.html WKT Raster Reference]. |
| | 375 | We have used the most powerful vector database engine around (PostGIS) to intersect our data buffers with a big raster datasets. For those who already know PostGIS, most of the queries are very familiar. For the newcomers, they might appear a bit complicated, but the speed at which we get the resulting table is worth the effort. The longuest step was to load the data. Once this is done, we can make as many quick queries as we wish. PostGIS with WKT Raster is a serious tool for accomplishing serious analysis work. |
| | 376 | |
| | 377 | You can find more info on PostGIS WKT Raster [wiki:WKTRaster in this page]. All the functions are documented in the [http://www.postgis.org/documentation/manual-svn/RT_reference.html WKT Raster Reference], [http://www.postgis.org/documentation/manual-svn/RT_FAQ.html WKT Raster FAQ Reference] |
