592 | | * Discussed with mentor and people from postgis-devel list. Found myself got blocked at this point: |
593 | | <br> |
594 | | As to the source dat, I think I would agree that we don't really want to rasterize the source geometries because we want to utilize the vector/raster seamless interactions featured and provided by PostGIS Raster. The solution I could think of was to calculate the distance based on the coordinates of the source geometries and the coordinates of the center of the resulted pixel derived from georeferencing info and then create a raster with those distance values as the pixel values. |
595 | | <br> |
| 592 | * Discussed with mentor and people from postgis-devel list (see comments part from [http://trac.osgeo.org/postgis/wiki/PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools#Week4Report Week 4 Report]). Found myself got blocked at this point: |
| 593 | |
| 594 | As to the source data, I think I would agree that we don't really want to rasterize the source geometries because we want to utilize the vector/raster seamless interactions featured and provided by PostGIS Raster. The solution I could think of was to calculate the distance based on the coordinates of the source geometries and the coordinates of the center of the resulted pixel derived from georeferencing info and then create a raster with those distance values as the pixel values. |
| 595 | |