Can I import ArcView project (APR) files into ArcMap for use in EMDS 3?
Can I view the spatial results of two or more EMDS analyses simultaneously?
How does the datalink and field name matching algorithm in the Data Requirements table work?
The data for my analysis are in multiple layers. Do I need to overlay the layers to get all the data into a single attribute table for an EMDS analysis?
How can I identify features in a truth-value layer with user-friendly ID fields?
I want to perform a tabulation of results in a truth-value layer (for example, the length-weighted average of reach condition for each subwatershed in a watershed assessment), but the truth-value layer (for example, reach condition) does not contain fields with the reach length or IDs that I can use to tabulate on. How can I do the tabulation?
The NetWeaver output table, out.dbf, contains more records than the attribute table of the shape file used as input to an analysis. What's going on?
Why do I get an error message when I try to edit a knowledge base?
I want to share an EMDS project that I have created with a colleague. Can they use my project?
The EMDS
Table of Contents (TOC) panel in ArcMap only allows the
user to work with one EMDS project at a time. The user
will have to load the ArcMap map (MXD) file that is
associated with the other EMDS project the user is also
interested in working with.
You can
run EMDS 2 and EMDS 3 on the same computer. Be advised
that EMDS 2 will not function properly on a Windows 2000
operating system.
You can
import ArcView project (APR) files into ArcMap by using
the File | Import from ArcView project function in
ArcMap. The imported data layers can then be saved as
ArcMap (MXD) files and used in an EMDS project.
To view and compare the spatial results of two or more
EMDS analyses or scenarios, create a new Data Frame by
using the Insert | Data Frame function in ArcMap. Then
right-click on the new Data Frame and select Activate
from the context-menu. Once the Data Frame is activated,
you can add data to it.
Can I run an EMDS 2 project
in EMDS 3?
You cannot run an EMDS 2
project in EMDS 3.
The algorithm is as follows:
For each knowledgebase datalink and for each input layer field:
Is the field name equal to the knowledgebase datalink name? If yes use it.
Is the field alias equal to the knowledgebase datalink name? If yes use it.
Is the field name equal to the knowledgebase datalink alias? If yes use it.
Is the field alias equal to the knowledgebase datalink alias? If yes use it.
Unable to determine a match programmatically. Do not use.
With this algorithm, precedence is given first to the knowledgebase datalink name then, if a match has not been found, try the knowledge base datalink alias. This way the knowledge base can be setup so that its datalink aliases are the same as the 10 digit field names in the input data. Thus, the you do not have to enter all the field aliases correctly every time you add a shapefile to ArcMap in order to use them in EMDS. This algorithm also allows matching knowledgebase datalinks to input data fields by entering the 10 digit field name in the alias table instead of having to dig around in the ArcMap interface to enter the 32 digit knowledge base datalink name into the field's alias.
How do I use my own data in
EMDS?
External data tables
(that is, data not already associated with map
features in a shape file attribute table) may need
to be imported into ArcMap to be joined with one or
more shape file attribute tables in an EMDS project.
If the original table contained missing values,
be sure to import
the data as tab delimited text so that ArcMap
and the NetWeaver engine correctly handle the
missing values.
Can analyses be performed
with missing data?
Yes. In fact, this is one
of the real strengths of EMDS in landscape analysis.
For additional background on performing analyses
with missing data, see the topic,
influence of missing information, in the
Glossary..
EMDS 3.0 only handles feature-based spatial data sets (coverages, shapefiles, and DXF CAD). Raster data must be converted to one of the feature-based types to be used in EMDS. Refer to ArcToolbox Conversion Tools for more information.
No. When an analysis is
run, EMDS checks the associated layers in the Data
Requirements table and overlays layers as needed.
The attribute table of a truth-value layer only contains a shape field and a truth-value field. No other fields associated with the original input layer are retained. To visually identify features in a truth-value layer displayed in the map view, add labels to features in the original input layer, and make sure the input layer is included in the same data frame as the truth value layer.
To perform the tabulations in an external application such as Excel, open the out.dbf file in Excel. In order to easily be able to perform a tabulation of, for example, the length-weighted of reach condition by subwatershed, you need to be sure that out.dbf contains user-friendly ID fields with reach and subwatershed names. These fields would not typically be present in out.dbf because they typically are not data the knowledge base would be requesting. However, these ID fields can, in effect, be forced into out.dbf by creating "dummy" networks in the knowledge base that ask for the name of the reach and the subwatershed.
This typically happens when the features in the input shape file are themselves composites of simpler features. For example, I might have created reach features by dynamic segmentation of a stream layer. During analysis, the composite features get decomposed back into their original, simpler topology. You can eliminate the decomposition problem by running CleanShapefile.exe on your shapefile. The program is located in the folder, C:\argis\arcexe82\ArcObjects Developer Kit\Samples\Utilities \CleanShapefile\. CleanShapefile produces a new simpler topology that will not be decomposed. It is still possible, however, to wind up with more records in out.dbf. Two other conditions can cause this: 1) features may naturally be split during layer overlays, and 2) particularly in the case of line features, internal gaps in the line segments will generate extra features during an overlay operation. The first of these conditions is unavoidable. The second can be corrected by careful feature editing.
Why are all the items on the
EMDS tool bar disabled?
When you first start ArcMap after installing EMDS, you must first enable the EMDS extension:
1. Click the Tools menu on the ArcMap menu bar.
2. Click the Extensions item on the Tools menu.
3. In the dialog, check the box in front of EMDS in the list of extensions.
Can I share an EMDS project
that I have created with a colleague?
Yes, but there are a few things to consider. The base layers that you used in the project may not reside in the EMDS project path structure. You will need to zip these up and send to your colleague also. EMDS can only find the base layers automatically if they are in exactly the same path on your colleague's PC as yours. If the path structures differ on the two machines, then the base layers will be displayed in the ArcMap Display pane as disconnected (grayed out). To reestablish the data source for each disconnected layer:
Right click on the layer in the ArcMap Display pane.
Click on Properties in the context menu.
In the Layer properties dialog, click on the Source tab.
Click on the Set data source button.
Navigate as needed in the Data source dialog to locate the base layer.
Select the base layer name, and click the Add button.
Back in the Layer properties dialog, click the OK button to complete the process.
Save the emds project.
Things are a little more complicated when the install path for EMDS differs between two PCs. In this case, before you send the project to your colleague:
Open your EMDS project in ArcMap.
Click on File - Map properties to open the dialog.
In the Map properties dialog, click on the Data source options button.
In the Data source options popup, set the option to store relative path names.
Save the project and send it to your colleague.
After your colleague adds the project into their \emds\projects folder, they will need to do the following:
Open the EMDS project in ArcMap.
Go to the EMDS tree view.
For each assessment in the tree view, right click on the assessment, in the context menu popup click on Associate layers, in the Associate layers popup click the OK button (this refreshes the layer association for the assessment.
Click on File - Map properties to open the dialog.
In the Map properties dialog, click on the Data source options button.
In the Data source options popup, set the option to store full path names.
Save the project.
Close ArcMap.
Open the EMDS project again.
Take a look at the contents of the ArcMap Display pane, and note the truth value maps that are listed there.
For each truth value layer listed in the Display pane, refresh the map by redisplaying it. That is, for each analysis or scenario in the emds tree view, go to Results - Truth values, select the truth value map, and press the Display button.
After refreshing all truth value maps at step 11, save the project.
Steps 8 through 12 are required in order to reestablish path information for the emds hotlink tool.
A knowledge base is a
formal logical specification for interpreting data.
For additional background on knowledge bases as
implemented in EMDS, see the topic,
knowledge bases, in the glossary.
How do I get existing
knowledge bases?
Two sample knowledge
bases (for watershed- and reach-scale evaluation of
watershed condition) are included with the sample
data provided with EMDS 3. These knowledge bases are
specific to the Chewaucan region of south-central
Oregon and should not be used for other regions
without at least minor modification. However, these
sample knowledge bases are easily customized with
NetWeaver Developer. Check the
NRIS
Tools web site (http://www.fs.fed.us/emc/nris/tools)
for additional knowledge base resources coming in
the near future.
How do I create my own
knowledge bases for use in EMDS?
Knowledge bases for use with EMDS are created using NetWeaver Developer.
What is the Data Acquisition
Manager (DAM)?
The DAM is designed to
develop priorities for missing data based on how
influential the missing data are to the analysis (in
a logical sense) and based on logistical issues of
obtaining the missing data.
Why would I want to use the
DAM?
Although the basic influence of missing information is obviously a very important consideration in deciding how much priority to give to missing data, you may wish to temper that evaluation by practical logistical considerations. The DAM balances the two criteria, influence and ease of acquiring of data, to produce an overall priority score for missing data.
The
Hotlink Browser is used to view the evaluated
state of the knowledge base for landscape features
selected with the Hotlink tool.
Why would I want to use the
Hotlink Browser?
The Hotlink Browser is a graphical model exploration tool that provides intuitive explanations of the derivation of analysis results. The Browser is also one of the primary tools through which alternative scenarios can be explored by modifying data inputs and logic model structure.
What is the Priority Analyst
(PA)?
The
PA evaluates the priority of landscape features
for possible management actions, given results of an
analysis generated by the NetWeaver logic engine,
and given a
Criterium DecisionPlus decision model for
establishing management priorities.
Why would I want to use the
PA?
Landscape features in the
worst condition are not necessarily the highest
priority for management actions. Additional
considerations, that can be evaluated with
PA and that may lead to improved decisions for
management action, include things such as the
feasibility and efficacy of management actions.
How do I get existing
Criterium DecisionPlus (CDP) models?
Two sample models for
setting priorities on stream reaches and watersheds
are included with the sample data provided with EMDS
3. These models are designed for use with their
corresponding knowledge bases and may require at
least minor modifications, depending on how the
knowledge bases are modified for adaptation to new
areas. However, these sample CDP models are easily
customized with
Criterium DecisionPlus. Check the
NRIS
Tools web site for additional CDP models coming
in the near future.
How do I create my own
planning models?
Multi-Criteria Decision Models for use with EMDS are created using Criterium DecisionPlus. To read more about Criterium DecisionPlus and Multi-Criteria Decision Models, see the Priority Analyst section.