Which versions of ArcGIS is the STARS toolset compatible with?
The STARS toolset is available for ArcGIS versions 10.2.x, and 10.1.x (STARS version 2.0.0) and ArcGIS version 9.3.1 (STARS version 1.0.2).
Do I need to use the FLoWS and STARS toolsets?
If you are working with STARS version < 2.0.0, you will need to use both the FLoWS and STARS toolsets for ArcGIS version 9.3.1. In STARS version 2.0.0 for ArcGIS versions 10.1.x and 10.2.x, the relevant FLoWS tools were incorporated into the STARS toolset, which provides all of the functionality needed to calculate the spatial data needed to fit spatial stream-network models.
When I run the Check Network Topology tool, I get the error ‘ImportError: No module named win32com.client’.
How would the anisotropy differ based on the orientation of the close points in the systematic/clustered design?
Anisotropy is a concept that doesn’t translate well to branching, linear stream networks. Obviously, you don’t have directional correlations related E-W/N-S. It seems natural to think that upstream sites are correlated with downstream sites, while downstream sites are uncorrelated with upstream sites; however, this is not the case. Even though water doesn’t flow from the downstream site to the upstream site, the measurement at the downstream site still provides information about the values upstream. However, I suppose that anisotropy might exist in the Euclidean component – it’s not something that we considered in the survey design work we’ve done. Though, you could also try to account for those anisotropic patterns using covariates, such as geology type, elevation, etc.
How does the STARS toolset address edges and dem valley floors that don't match? Is there a stream drop or burning step?
We don’t provide any specific tools to deal with these issues. However, we do walk people through the steps of burning streams into a DEM in the STARS tutorial.
Is the ratio value for site location on a reach calculated automatically or manually?
The ratio value for each site is calculated automatically when you use the Snap Sites to Landscape Network tool. That’s why you have to snap sites even if they already lie directly on the line segment.
Can you export polygons into the .ssn directory for mapping in R?
Yes – you could export polygons into the .ssn directory and then map them in R. You’ll have to do it manually because polygons aren’t exported in the Create SSN Object tool. Store them in shapefile format in the .ssn directory. The polygons won’t be part of the SpatialStreamNetwork object in R, but you should be able to plot them in R – have a look at the sp package if you haven’t worked with spatial data in R before.
How are multiple streams draining to a waterbody or lake handled in the Landscape Network?
Multiple streams are often treated as artificial connections in the stream network datasets, which are used to route flow through waterbodies. We don’t include lakes in the LSN and so we rely on these artificial connections to keep everything ‘connected’ up- and down-stream of the waterbody. If there was not an outlet from the lake (i.e. all segments flow into the lake and none flow out), each segment that flows in would have to be considered an outlet segment.
If I'm starting with NHD Plus data (which already has contributing areas and many other attributes available), could I skip many of the pre-processing steps in the STARS tutorial? Which would I still have to do?
Yes, you can skip some of the pre-processing steps if you’re using the NHDPlus – specifically the Create Cost RCAs and accumulating the watershed area using the Accumulate Attributes Downstream tool. You’ll have to run every other STARS tool in order to format the .ssn object properly.
If you use watershed area to generate the Segment PI values, does this alleviate the need to normalize covariates by watershed area (i.e. % urban in the watershed)?
No. Using drainage area as the segment PI doesn’t alleviate the need to normalize covariates such as % urban in the watershed. You’ll still need to do that yourself. The Segment PI values are used to generate the spatial weights, while the covariates are used in the mean model.
Does the SpatialStreamNetwork object inherit from the ESRI Network object?
The SpatialStreamNetwork object is not related to the ESRI Network object. It is an object we defined in R and it is a modification of other spatial objects used in the sp package, such as the SpatialPointsDataFrame and the SpatialLinesDataFrame. See the documentation for the sp package or Ver Hoef et al. (2014) for additional information. There is also a book: Analysing Spatial Data with R by Bivand and others (2008) that provides a thorough and accessible overview of spatial data objects in R.
For each monitoring site, where does the observed value(s) such as temperature, reside? In the observed sites shapefile?
The observed temperature values are stored in the sites shapefile attribute table. When the .ssn object is imported into R, these values reside in the SpatialStreamNetwork object. More specifically, they are stored in the observed sites point.data data.frame. Please see the help for the SpatialStreamNetwork class object in R for more information (just type help(“SpatialStreamNetwork-class”)). Also, the getSSNdata.frame() function can be used to easily extract this data.frame from the SpatialStreamNetwork object.
Why would you see spatial pattern in residuals if after fitting a spatial statistical model? Does a spatial pattern in the residuals suggest that more modelling is needed?
No - the residuals represent the unexplained variability after accounting for the covariates and the spatial patterns that you observe are essentially what the spatial component is describing. So, it doesn’t necessarily mean that more modelling is required.
Why are the R-squared values for the models that included spatial autocorrelation substantially lower compared with the basic linear independence models?
The R-squared reported as part of the model is the proportion of variation explained by the fixed effects. It is not predictive performance. Because the error structures are different between autocorrelation and independence models, there is no relationship between the R-squared of the two. If you want to compare the predictive ability of autocorrelation and independence models you can look at the correlation between observed values and predictions using cross-validation. That is a completely unrelated idea to the one above.
What is block kriging?
Block kriging is the prediction of an average value over an area, rather than the particular value at a single point in space.
What is the difference between prediction and estimation?
When you set up a statistical model, you generally put the observable quantity on the left of the equal sign, and the model on the right side of the equal sign. Prediction is used to refer to an inference on an unobserved, but potentially observable value to the left of the equal sign. Estimation is used to refer to an inference about a model parameter, which is not directly observable.
Why don’t I get an AIC value for logistic and Poisson regression models in the SSN package?
In the SSN package, the logistic and Poisson regression models use a model fitting method that has been called quasi-pseudo-likelihood (which is described in the SSN documentation). The real likelihood, including the spatial part of the model, is too difficult to compute. Because there is no true likelihood, AIC cannot be computed. Some have proposed a method called QAIC, but it has a questionable reputation and has not been tested for these types of models. Hence, we do not include AIC, except for models based on a normal distribution. You can use cross-validation, P-values, or some other method to compare, or select, among models. This approach, and the information that we give, is essentially equivalent to PROC GLIMMIX in SAS. You can read up on that to help you make modelling decisions and understand it better.
Find AWAE and follow us on your favorite social media site: