The first shows an application of the second.(It is noteworthy that these formulas do not require that the locations be distinct: the calculation works just fine, and makes perfect sense, even when multiple values are available at some locations.)
That's not for IDW to do. Instead, you need to compute a distance grid for each source location and use Map Algebra to calculate the w(i) from those and form the desired linear combination. Distance grids can be computed in any way that is appropriate: using CostDistance to approximate travel times, for instance, or even just the Euclidean distances.
JamalSpatial Analyst and Geostatistical Analyst use the same equation for IDW, please see page 114 in http://dusk.geo.orst.edu/gis/geostat_analyst.pdfIf you have anymore questions regarding this equation then please email me at slynch@esri.comSteve
What is your evidence for this? A surface may look more or less smooth at different scales and different resolutions: that would be an artifact of display and discretization, respectively. But it will be the same surface regardless of the units of distance.The reason I am sceptical of this claim is that when the distance units change, all distances are multiplied by some constant r (such as 1/1000 when converting from meters to kilometers) This multiplies all weights by r^(-p) and that factor cancels out in the formula, whence the interpolated values do not change at all.Please notice, too, that a change of "units" between meters and decimal degrees is not actually a change of units: it is a projection or unprojection. This nonlinear transformation of locations will necessarily cause the IDW interpolated values to change.There's always the possibility of a bug in the calculations, but that's the last thing to consider, after other plausible explanations are ruled out.
No argument there. But sometimes the coder has a different understanding of the references they are using than do other readers. Thus, as documentation of the software, the developer can do very well by describing how they interpreted the equations and implemented in them in the software. This closes the loop from equation to software back to equation. Furthermore, by not forcing software users to reference the literature (which often is academic papers not freely available), this makes explicit documentation available to all users, not just the privileged ones with good library access.A recent (nice) example of the value of explicit documentation compared to a mere reference appears at on the StackExchange GIS Q&A site, where a user of open source GIS software found a problem not by testing the software, but by seeing something strange in the documentation (which, because this is OSS, includes the code itself, which is not an option with ArcGIS). The code was based on good references but mis-interpreted them (and made a few additional mistakes along the way...).I, for one, have appreciated the accessibility of the Python source code in some of the ArcToolboxes, because it goes a long way to showing that these tools are doing what I expect and are doing it correctly. Otherwise, when working on important projects (and all projects for clients are important!), I have to test the software extensively, because the documentation tends to be non-technical and vague.
JamalIt is often better to cite a reference rather than copy from it. This will give you more insight into the inner workings and assumptions around these equations. Which is what we have done for IDW and Kernel Density.Steve
JamalA search would have led you to a thread Dan participated in 7 years ago, viz.,http://forums.esri.com/Thread.asp?c=93&f=995&t=176542What are the problems that you are seeing?Steve
ESRI generally doesn't post the equations that they use, but may give reference to cited papers and/or books. You can be assured that the IDW equation implemented is not of their own making but has a long history of implementation.
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.