Opened 13 years ago

Last modified 11 years ago

#826 closed enhancement

[raster] raster2pgsql should not pad tiles with NODATA — at Version 7

Reported by: pracine Owned by: Bborie Park
Priority: high Milestone: PostGIS 2.1.0
Component: raster Version: master
Keywords: history Cc:

Description (last modified by Bborie Park)

This would be as part of the changes described in #2122.

Change History (7)

comment:1 by pracine, 13 years ago

-Another interesting option would allow not loading tiles containing only nodata -Another interesting option would trim complete row or columns of nodata values at the borders of loading tiles

comment:2 by pracine, 13 years ago

Milestone: PostGIS 2.0.0 → PostGIS Raster Future

comment:3 by Bborie Park, 12 years ago

Summary: [raster] There should be an option in raster2pgsql.py to prevent completing tiles with nodata → [raster] There should be an option in raster2pgsql to prevent completing tiles with nodata

comment:4 by pracine, 12 years ago

Milestone: PostGIS Raster Future → PostGIS Future

comment:5 by Bborie Park, 11 years ago

Milestone: PostGIS Future → PostGIS 2.1.0
Owner: changed from pracine to Bborie Park
Priority: low → high
Status: new → assigned

comment:6 by Bborie Park, 11 years ago

Summary: [raster] There should be an option in raster2pgsql to prevent completing tiles with nodata → [raster] raster2pgsql should not pad tiles with NODATA

comment:7 by Bborie Park, 11 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.