Opened 9 years ago
Last modified 7 years ago
#3318 assigned defect
ST_MapAlgebra with mask seems to hard-code distance 1 instead of inferring distance from mask matrix
Reported by: | robe | Owned by: | dustymugs |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | raster | Version: | master |
Keywords: | Cc: |
Description (last modified by )
I've moved this from the now closed mask documentation #2603 to here, I'm still having issue with this even as of r14198 even though dusty has made some changes.
DROP TABLE IF EXISTS shapes; CREATE TABLE shapes(rid integer, rast raster); INSERT INTO shapes(rid,rast) VALUES ( 1, ST_AsRaster( ST_Buffer( ST_GeomFromText('LINESTRING(50 50,150 150,150 50)'), 10,'join=bevel'), 200,200,ARRAY['8BUI'], ARRAY[118], ARRAY[0]) ); SELECT st_mapalgebra(rast,1,'st_mean4ma(double precision[], int[], text[])'::regprocedure,'{{1,0,1,1,1}, {1,0,1,1,1}, {1,0,1,1,1}, {1,0,1,1,1}, {1,0,1,1,1}}'::double precision[],false) FROM shapes;
Gives error:
ERROR: rt_pixel_set_array: mask dimensions 5 x 5 do not match given dims 3 x 3
It's my understanding based on dusty's comments that the neighborhood size should be inferred from the mask size, so there seems to me something wrong here.
Bborie's comments copied from other ticket
Distance is two pixels left, right, up, down from the pixel of interest…
2 2 2 2 2 2 1 1 1 2 2 1 0 1 2 2 1 1 1 2 2 2 2 2 2
So the distance x/y are correct. As for that error message, I'll need to dig.
Change History (13)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
Component: | postgis → raster |
---|---|
Owner: | changed from | to
comment:3 by , 9 years ago
Milestone: | PostGIS 2.3.0 → PostGIS 2.2.1 |
---|
comment:4 by , 9 years ago
Status: | new → assigned |
---|
comment:5 by , 9 years ago
Priority: | medium → critical |
---|
comment:6 by , 9 years ago
Milestone: | PostGIS 2.2.1 → PostGIS 2.3.0 |
---|
comment:8 by , 9 years ago
Milestone: | PostGIS 2.3.0 → PostGIS 2.2.1 |
---|
okay I'll switch back then. Hurry Hurry PostgreSQL 9.5.0 is already been stamped.
comment:9 by , 9 years ago
Milestone: | PostGIS 2.2.1 → PostGIS 2.2.2 |
---|
comment:10 by , 9 years ago
Milestone: | PostGIS 2.2.2 → PostGIS 2.2.3 |
---|
comment:11 by , 8 years ago
Milestone: | PostGIS 2.2.3 → PostGIS 2.4.0 |
---|
comment:12 by , 7 years ago
Milestone: | PostGIS 2.4.0 → PostGIS Future |
---|---|
Priority: | critical → medium |
Bborie,
I'm guessing you won't have time to look at this within the next day or so, so pushing to 2.3. If you do feel free to push back. I'll push to 2.2.2 after release.