|
126 | 126 | <p>This smoother is called Empirical <i>Bayes</i> because it borrows strength from a <i>prior</i> distribution to correct for the variance instability associated with rates that have a small base. It is <i>empirical</i> because the prior distribution is based on global characteristics of the existing observations.</p>
|
127 | 127 | <h3>
|
128 | 128 | <a name="ebstand">Empirical Bayes Standardization</a></h3>
|
129 |
| -<p>While the Empirical Bayes (EB) smoother adjusts for variance instability through a weighted averaging of rates based on a reference rate, EB standardization directly standardizes raw rates to obtain a constant variance. While <a href="#smooth">smoothing</a> is based on weighting rates, standardization rescales rates. The original raw rate is replaced with a standardized rate with mean zero and standard deviation of one. GeoDa implements the EB standardization procedure suggested by <a href="/node/396#ebstandf">Assuncao and Reis</a> in its <a href="#gmoran">global Moran scatter plot</a> and <a href="#lisa2">LISA</a> maps.</p> |
| 129 | +<p>While the Empirical Bayes (EB) smoother adjusts for variance instability through a weighted averaging of rates based on a reference rate, EB standardization directly standardizes raw rates to obtain a constant variance. While <a href="#smooth">smoothing</a> is based on weighting rates, standardization rescales rates. The original raw rate is replaced with a standardized rate with mean zero and standard deviation of one. GeoDa implements the EB standardization procedure suggested by <a href="refs.html">Assuncao and Reis</a> in its <a href="#gmoran">global Moran scatter plot</a> and <a href="#lisa2">LISA</a> maps.</p> |
130 | 130 | <h3>
|
131 | 131 | <a name="esda">ESDA</a></h3>
|
132 | 132 | <p>ESDA stands for <i>Exploratory Spatial Data Analysis</i>. It refers to a set of techniques to interactively visualize and explore data where space matters, in order to detect potentially interesting and explicable patterns. It can also be used to generate hypotheses and to visually assess model results and diagnostics (e.g., by visualizing patterns of residuals that were saved in the regression process). In addition, it is a useful tool for data quality control (e.g., using the weights histogram).</p>
|
@@ -185,14 +185,14 @@ <h3>
|
185 | 185 | <p>K Nearest Neighbors (KNN) is a distance-based definition of neighbors where "k" refers to the number of neighbors of a location. It is computed as the distance between a point and the number (k) of nearest neighbor points (i.e. the distance between the <a href="#centralpt">central points</a> of polygons). It is often applied when areas (such as counties) have different sizes to ensure that every location has the same number of neighbors, independently how large the neighboring areas are.</p>
|
186 | 186 |
|
187 | 187 | <p><a name="crash"></a></p>
|
188 |
| -<p>K Nearest Neighbors weights matrices can be created in GeoDa. They are asymmetric (e.g., point A is B's nearest neighbor but point B does not have to be point A's nearest neighbor). Because of this asymmetry, it is not possible to correctly estimate spatial lag or error models with KNN weights and Maximum Likelihood Estimators in GeoDa However, you can do this with other spatial estimators and KNN weights in <ahref=?GeoDaSpace?>GeoDaSpace</a>.</p> |
| 188 | +<p>K Nearest Neighbors weights matrices can be created in GeoDa. They are asymmetric (e.g., point A is B's nearest neighbor but point B does not have to be point A's nearest neighbor). Because of this asymmetry, it is not possible to correctly estimate spatial lag or error models with KNN weights and Maximum Likelihood Estimators in GeoDa However, you can do this with other spatial estimators and KNN weights in <ahref="GeoDaSpace">GeoDaSpace</a>.</p> |
189 | 189 |
|
190 | 190 | <p> </p>
|
191 | 191 | <h3>
|
192 | 192 | <a name="l"><b>L</b></a></h3>
|
193 | 193 | <h3>
|
194 | 194 | <a name="lattice">Lattice Data</a></h3>
|
195 |
| -<p>Lattice data refers to point or polygon data that represent discrete areal units (such as counties), i.e. areas where there is no uncertainty as to their location, as opposed to events or sample points whose location is not certain. For more details, see <a href="/node/396#baily">Bailey & Gatrell</a> (introductory) or <a href="/node/396#cressie">Cressie (1991)</a> (advanced).</p> |
| 195 | +<p>Lattice data refers to point or polygon data that represent discrete areal units (such as counties), i.e. areas where there is no uncertainty as to their location, as opposed to events or sample points whose location is not certain. For more details, see <a href="https://spatial.uchicago.edu/spatial-analysis-references">Bailey & Gatrell (introductory) or Cressie (1991)</a> (advanced).</p> |
196 | 196 | <h3>
|
197 | 197 | <a name="layer">Layer</a></h3>
|
198 | 198 | <p>When more than one <a href="#shape">shape file</a> is loaded in GeoDa or in a <a href="#gis">GIS</a>, the shape file is referred to as a layer. Layers share the same (or part of the same) geographic extent and display different characteristics of this geography, such as census tracts (polygons), businesses (points), and streets (lines) in the same city.</p>
|
|
0 commit comments