Opened 9 years ago
Closed 8 years ago
#1307 closed defect (fixed)
Rasql_project() has different bounding box to GDAL
Reported by: | Bang Pham Huu | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 9.3 |
Component: | rasql | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description
When using gdalwarp to reproject from epsg:4326 to epsg:4269 and compare with result from WCPS (it is different in any projection). The origins (bounding box) of Rasql is different to gdalwarp.
Here is the comparison of gdalwarp and Rasql
https://www.diffchecker.com/bv5h2tmd
using gdalwarp
gdalwarp -t_srs 'epsg:4269' -r bilinear -of GTIFF test.tif test_3.tif
WCPS query
for c in (test_projection) return encode(crsTransform(c, { Lat:"http://www.opengis.net/def/crs/EPSG/0/4269", Long:"http://www.opengis.net/def/crs/EPSG/0/4269"}, {}), "tiff")
also data to import if one want to reproduce
Attachments (2)
Change History (3)
by , 9 years ago
Attachment: | ingredient.txt added |
---|
by , 9 years ago
comment:1 by , 8 years ago
Milestone: | 9.2 → 9.3 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
with current WCPS and rasql, it returns the same bounding box, the only difference is the pixel size but it is small (e.g: -91.773493181419440 and -91.773493181429174), see the difference here https://www.diffchecker.com/m4jnpipv, close ticket.