Opened 14 years ago
Closed 13 years ago
#645 closed defect (fixed)
[raster] more raster/scripts/plpgsql st_setarray.sql, st_sevalues, st_union
Reported by: | robe | Owned by: | pracine |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 2.0.0 |
Component: | raster | Version: | master |
Keywords: | Cc: |
Description
I'm guessing these are still a work in progress since there are several things wrong with them
1) In st_union you have MapAlgebra4... which doesn't start with ST_ like the other functions
2) You have several places where you have band but don't declare the type yielding
ERROR: type band does not exist
3) The st_setarray.sql contains a function called: huh - ST_SetArea
4) st_sevalues.sql (should be called st_setvalues)
Change History (5)
comment:1 by , 14 years ago
Summary: | more raster/scripts/plpgsql st_setarray.sql, st_sevalues, st_union → [raster] more raster/scripts/plpgsql st_setarray.sql, st_sevalues, st_union |
---|
comment:2 by , 14 years ago
comment:3 by , 14 years ago
Status: | new → assigned |
---|
comment:4 by , 14 years ago
Priority: | medium → blocker |
---|
comment:5 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Was just looking at ST_SetValues.sql. Is there a reason why you chose to create a min and max function instead of using the PostgreSQL built-in least and greatest functions?