|
|
 |
FAQ's Pre Current Version
Tools
Stick
Loader
Builder
General Questions
- What is the best way to determine the changes in the SDSFIE content from version to version?
The best way to determine the changes to to review the release notes for each new version.
Release Notes 2.600
Release Notes 2.500
Release Notes 2.400 - What are the arrows for in the SDSFIE? What geometry type can I use for them?
The direction arrows (there are about 15-20 of them) are included in the SDSFIE but are "cartographic" ONLY. This means that there are no defined attributes and the specific structures are left up to the users. They are essentially "drawn" on the map to show flow, direction, slope, etc. They can be drawn as line strings, or captured as points (as in ArcGIS) where an attribute indicates the angle of the symbol shown at the point.
Tools
- Once SDSFIE v2.6 is installed on the computer does the user need administrator rights to run any of the tools?
Yes, you will need to have admin rights. The other option is to use SDSFIE on a stick, which keeps everything on a flash drive, and does not install anything to your computer. - Will the SDSFIE tools from the Toolbox work in Vista?
As you may be aware, Vista represents a significant change in the architecture of Windows and would likely represent a considerable investment in modifying the applications of the SDSFIE Toolbox.
In that a major initiative is underway to expand the functionality of the SDSFIE and remodel the content for SDSFIE 3.0, there is reluctance to commit to a sizable expenditure to upgrade the existing toolbox. At the same time, the Services have indicated that Vista is not expected to be a major player in the DoD Operating System environment for some time. All of this indicates that complete migration of the earlier SDSFIE Toolbox is not warranted, and should not be expected.
Based on the experience of the Help Desk, the two areas where an interest exists are 1 – Browsing (either Full or Lite) and 2 – Geodatabase Builder. We are currently in the midst of an initiative to attempt modification of the “SDSFIE on a Stick” for ESRI users with some success. A recommendation is expected around June 1, but it is unlikely that a complete rewrite of the Toolbox is in the works.
It would be wise for users to consider dedication of an XP machine for use with the current Toolbox, at least through the spring of 2009. If it is possible to modify the functionality of critical tools for Windows Vista without significant funding, an announcement will be made on the Web Site.
Stick
- Are there any conflicts when using the SDSFIE on a stick? I get an exception error whenever I try to use it to create a personal geodatabase.
The definitive test is whether the Browser or Browser Lite work. If they do, then the extraction for the stick is appropriate. If they do not, then the problem is in the configuration of the stick. If you get the Browser, and also get the Geodatabase Builder on the Menu Bar, then the application can see the ESRI License. This is important for the Geodatabase Builder. If all that is Ok, then the problem is elsewhere.
The stick still requires the workaround, depending on the release of ArcGIS you are using. If it is 9.1, you will need to rename the fme file. If it is 9.2, then you need the Environment Variable. The details are on the Web Site. If you perform the workaround and still are having trouble, then it is likely something with permissions on your computer. Start with the other applications, then check the workaround on the Web Site.
Loader
- How to generate the metadata Table in the SDSFIE GDB-Loader 2.6?
In the Loader, if you wish to use the Metadata tab, you must first have a FEATURE_METADATA table built within your geodatabase. This can be added using the ESRI Geodatabase Builder, even after the geodatabase has been built. During the Load, it is important to use unique META_ID values. Each layer has to use a unique value or it will overwrite the previous metadata entry. Finally, it is important to note that Feature Level metadata maintains data for each feature. The metadata that is viewed in ESRI ArcCatalog is Layer level metadata, and correlates with the entire feature class.
Builder
- I am building geodatabases with the same feature classes over and over again. Multiple feature classes in multiple entity sets can take a lot of time to select and add. Is there a way I can create a personalized filter which will automatically make this selection for me?
The SDSFIE Filter Maker is intended to provide exactly that support. You can save up to 10 Custom Filters per Library. Open the Filter Maker, connect to your Library, name your Filter, and select your Features. You will then see it in the Geodatabase Builder. There are Help Files that describe the process. - When creating a new personal geodatabase using v. 2.6, I'm been trying to import the spatial reference from an existing layer which lives on SDE. The existing SDE dataset is selected, and when Build/Generate is clicked, I get the following error: Error getting Feature Dataset.
This particular error is a result of the conversion from low precision to high precision. The existing toolset was written before ArcGIS 9.2. The error was first reported following installation of ArcGIS 9.2 Service Pack 5. This error is generated when the tool attempts to create a Spatial Reference for high precision datasets from low precision datasets. In the high precision dataset, the concept of the Spatial Domain (the box where the data resides) is much less critical than in earlier structures. Here, at the Help Desk, we create new Spatial References by selection rather than import. We determine the Spatial Reference by querying the Feature Class we want, using the Select and finding the Spatial Reference; e.g. WGS 1984 UTM ZONE 16, and then adjusting the precision (although in most cases it is fine). We have not had any difficultly using this technique, and it does not require export.
Unfortunately, this also continues to be a problem even if the datasets in SDE are high precision. The problem is in the Builder Software. The government has taken a position that they do not want to update the old software, particularly since there is a workaround. If you want to add to an existing Feature Dataset, it should work with no problem. That way, you might be able to create the Feature Dataset in ArcCatalog, and then use the Builder to create the classes. Just make sure you have the proper Feature Dataset name. - What is the process of migrating from 2.400 to 2.500 withing the SDSFIE environmnet?
It is possible to create an extract within the Geodatabase Builder (or from a standalone dowloadable executable) that can be submitted to the Checker. Once you are an authorized user of this web site, you will see it under Web Tools. I would run an extract of your 2.4 Geodatabase, and run it through the Checker using Release 2.500 as a baseline.
The resulting report should give you some specifics as to what is going on. In some cases, you can "declare yourself a winner" since the SDSFIE did not change. In other cases, you may be able to make the change yourself manually. - The SDSFIE ESRI Geodatabase Builder crashes with ArcGIS 9.2. What is causing this problem?
The problem is caused by a continuing disconnect between the ESRI Data Interoperability Extension and internal ArcObject Calls made by the SDSFIE software. The workaround for this error is:
What programs generate the error?
If you are running any of the SDSFIE Geodatabase programs, they may generate an error. This includes Geodatabase Builder 2.501 and earlier, Geodatabase Loader 2.502 and earlier, Geodatabase XML Constructor 2.501 and earlier, and/or the Geodatabase Domain Fixer (for d_uom) 2.500 and earlier.
What is the error?
The error is generated whenever the "IGxDialog" appears. This is an ESRI Dialog that is used to create or open a Geodatabase, Feature Dataset, Feature Class, or Object Class. It has the look and feel of a mini-ArcCatalog and navigates through ESRI Objects. Depending on the individual machine, operating system, and/or patches, the Dialog may briefly appear, or it may not appear. The error creates a Windows exception and the application terminates. The exception is normally associated with the Kernel32.dll. ArcCatalog is unaffected by the error.
Why am I getting this error?
The error is related to the Data Interoperability Extension within ArcGIS 9.2. The error is similar to the ArcGIS 9.1 error except that the workaround for ArcGIS 9.1 does not correct the problem, since the offending file is no longer in the Data Interoperability Extension directory. A new workaround is required.
How do I fix the error?
ESRI has no patch for this but the fix is a simple one. It involves changes to the machine configuration and the applications. Upper 90 Systems, Inc is aggressively working the problem and is modifying the SDSFIE Geodatabase Tools to function in the revised environment. The new Geodatabase Builder (2.502) is available at: http://www.sdsfie.org/Downloads/Release_250/9_2Fix.zip
The executable in this zip should be placed in the SDSFIE Directory; e.g. normally C:\Program Files\TSSDS The Release 2.600 version of the SDSFIE Tools has this modification already incorporated, so no further download is required
Note: This executable will ONLY replace the Geodatabase Builder. Do not remove any of the previously installed SDSFIE tools.
In addition, the path to the ESRI Data Interoperability Directory must be added to the PATH environment variable. This is accomplished by:
- Right Click on "My Computer", and select Properties at the bottom of the pop-up menu.
- Select the "Advanced" tab and click on "Environment Variables" at the bottom of the Dialog.
- In the "System Variables" section at the bottom of the Dialog, find the PATH environment variable, select, and click "Edit".
- APPEND the path to the ESRI Data Interoperability Extension (normally C:\Program Files\ArcGIS\Data Interoperability Extension) to the path value. Make sure you place a semi-colon (;) between the current value and the new directory. After appending the path, the variable should look something like:
%SystemRoot%\system32;%SystemRoot%;C:\Program Files\ArcGIS\Data Interoperability Extension”
*Note: If ArcGIS is not installed to the default directory, the above path should be changed to accomodate this location.*
**If ArcInfo WorkStation is still installed on the machine, it should be removed, as this will also generate an error.**
- In some configurations, the application may still fail the first time. However, testing both here and in the field have indicated that the fix is reliable in subsequent tries.
- To avoid possible error, restart the machine. Because an environment variable has been altered, many machines may not recognize the change immediately. In that the complete analysis of ArcGIS 9.2 is still being determined, please report problems and/or issues to the Upper 90 Systems, Inc Web site or e-mail to helpme@sdsfie.org.
Other help:
For more help, or for answers to questions about this error, contact:
SDSFIE Help Desk
1-866-9SDSFIE
HelpMe@sdsfie.org
- The SDSFIE Geodatabase Builder crashes with my ArcGIS 9.1. What is causing this problem?
The problem is the result of a license conflict with the ESRI Data Interoperability Extenxion. The Workaround for GIS 9.1 is:
What programs generate the error?
If you are running any of the SDSFIE Geodatabase programs, they may generate an error. This includes Geodatabase Builder, Geodatabase Loader, Geodatabase Checker, and/or the Geodatabase Domain Fixer (for d_uom).
What is the error?
In the SDSFIE Geodatabase Builder When a dialog box is opened to open or create a geodatabase, the entire program shuts down. This error does not occur for 9.1 users with ArcInfo developer licenses.
Why am I getting this error?
There is an IgxDialog file created by ESRI, which is prompted every time these dialog boxes open. It is looking for a license code for ArcGIS 9.1. If a user has a standard version of ArcGIS 9.1 with no license code, the program will terminate.
How do I fix the error?
ESRI has no patch for this but there is a simple workaround. You need to rename the fmearcgisext.dll file, which the software is trying to call This will NOT harm the performance of the ESRI software in any way, provided you do not have an Interoperability Extension License.
- Find the fmearcgisext.dll file. The default location of the file is: C:\Program Files\ArcGIS\Data Interoperability Extension If the file is not located there, you will have to find it.
- Rename the file fmearcgisext.dll to OLDfmearcgisext.dll. Do Not Delete It!
- Rerun the SDSFIE Geodatabase tool and the error will not occur.
Other help:
For more help, or for answers to questions about this error, contact:
SDSFIE Help Desk
1-866-9SDSFIE
helpme@sdsfie.org
- How do I populate the Relationship Class Forward and Backward Label values in the SDS Builder for use with ArcGES 9.0 SP2?
The Release 2.6 Builder has this capability. It builds both a forward and a backward label.
Here is a query submitted by another user if you want to try it. The user states this query will work on any GDB you may have because it uses tables common to all SDSFIE compliant GDB.
UPDATE (GDB_RelClasses INNER JOIN GDB_ObjectClasses ON GDB_RelClasses.OriginClassID = GDB_ObjectClasses.ID)
INNER JOIN GDB_ObjectClasses AS GDB_ObjectClasses_1 ON GDB_RelClasses.DestClassID = GDB_ObjectClasses_1.ID
SET GDB_RelClasses.ForwardLabel = GDB_ObjectClasses_1.Name, GDB_RelClasses.BackwardLabel = [GDB_ObjectClasses].Name;
|
|
|
|
|
|
|
|
|
|