[postgis-tickets] [PostGIS] #5311: ST_Contour bug over the limits of tiles

[PostGIS]

#5311: ST_Contour bug over the limits of tiles
----------------------+---------------------------
  Reporter:  latot    |      Owner:  robe
      Type:  defect   |     Status:  closed
  Priority:  medium   |  Milestone:  PostGIS 3.3.3
 Component:  raster   |    Version:  3.3.x
Resolution:  wontfix  |   Keywords:
----------------------+---------------------------
Changes (by pramsey):

 * status:  new => closed
 * resolution:   => wontfix

Comment:

 The premise of the raster module is small pieces of raster, and users
 build them up as necessary. That's the premise of the whole thing. There's
 no "make it work easier" magic to wave at it. A different raster module
 built on a completely different premise might be more like you expect, but
 that's not what we have.

 Should we get rid of what we have? Maybe! It certainly fills people with
 false hope.

 But "it's in the database so it should be fast" is not actually logical
 reasoning. The database has to handle the same limitations as any other
 software, in terms of access to storage and memory and moving data between
 those things. With the added overhead, in the case of PgSQL of also
 maintaining full transactional integrity over multiple simultaneous
 readers and writers. It's going to end up trading off specific efficiency
 for general purpose utility.

 Maybe explore other ways of processing your rasters, like an imperative
 scripting tool like python rasterio.
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5311#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.