block and output grid size in block kriging

The drawing (thanks!) suggests that you think that the point over which
a kriging block is centered is not the center point of a grid cell. This
is wrong: the coordinates of grid cells, obtained e.g. by

require(sp)
demo(meuse, ask = FALSE)
coordinates(meuse.grid)

are grid cell centers. You can verify this, e.g. for the first 20 grid
cells / pixels with

plot(as(meuse.grid[1:20,], "SpatialPolygons"))
points(meuse.grid[1:20,])

I also tried to point out in my previous answer that you are not looking
at "ordinary kriging" vs "block kriging", but at "ordinary point
kriging" vs. "ordinary block kriging". If your observations are not
constant and you don't use a pure nugget model, point kriging and block
kriging estimates will always be different.

Dear Edzer,

Thanks for the clarification.Still it not clear to me.

I added an image below showing the block and the grids. If my visualization
is correct then for a block of (40,40), there is only 1 grid points. If Yes,
then ordinary kriging estimate and block kriging estimate for block size
(40,40) should be same.

<http://r-sig-geo.2731867.n2.nabble.com/file/n7587782/block_kriging_framework.png> 

Thanks in advance



--
View this message in context: http://r-sig-geo.2731867.n2.nabble.com/block-and-output-grid-size-in-block-kriging-tp7587770p7587782.html
Sent from the R-sig-geo mailing list archive at Nabble.com.

_______________________________________________
R-sig-Geo mailing list
R-sig-Geo at r-project.org
https://stat.ethz.ch/mailman/listinfo/r-sig-geo

Edzer Pebesma
Institute for Geoinformatics, University of M?nster,
Heisenbergstra?e 2, 48149 M?nster, Germany; +49 251 83 33081
Journal of Statistical Software:   http://www.jstatsoft.org/
Computers & Geosciences: http://elsevier.com/locate/inca/398

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <https://stat.ethz.ch/pipermail/r-sig-geo/attachments/20150212/557e67f7/attachment.bin>