Tag Archives: ArcCatalog
It is always challenging when your coordinates are in Decimal Degrees (DD) format and you need them in Degrees, Minutes, Seconds (DMS). Amidst this challenge is determining how to do the conversion. Is it best to open the table in Microsoft … Continue reading
When using ArcSDE geodatabases, you may have noticed a change within the 10.0 release in how the upgrade process is now handled. Instead of using the Post Installation Wizard and selecting Repository Setup, as in previous releases, there is a new upgrade process. Upgrading your geodatabase is now performed within ArcCatalog using the new Upgrade Geodatabase (Data Management) tool.
The Upgrade Geodatabase (Data Management) Tool can be accessed in ArcCatalog via the Database Properties of a database connection under the General tab > Upgrade Status or within the Upgrade Geodatabase geoprocessing tool referencing an existing connection. For ArcSDE geodatabases, a direct connection to the geodatabase is necessary to run the upgrade.
Post Installation Wizard at 10.0:
The Post Installation Wizard in 10.0 can be used for the following:
- Defining Database and SDE DBA User – Creating new ArcSDE enterprise geodatabases
- Repository Setup – Populate system repository tables (for new geodatabases only)
- Authorize ArcSDE – Perform Software Authorization of the geodatabase
- Create ArcSDE Service – If using application server service (when not using direct connections)
More changes are on the horizon to incorporate Post Installation functionality into the client tools for the 10.1 release, so stay tuned!
“Can I fix feature linked annotation if it’s no longer working as expected?” is a question I’m frequently asked. Good news, the answer is “yes, annotation can typically be fixed.”
What do I mean when I say “fix your annotation?” How did it break? Why isn’t it working as expected?
These are good questions. What I mean is: Your annotation is no longer working as expected. For example, you add a new feature into the feature class and populate the fields, but annotation is not automatically created, or perhaps you make some changes to a field in the feature class, but the annotation is not automatically updated.
There are a few key things to look at when trying to determine how to fix annotation problems:
1. Is your annotation based off of a SQL query?
To check this, work in either ArcCatalog or the Catalog Window
- Right-click on the Annotation Feature Class and choose Properties. Click on the Annotation Classes tab.
- Highlight one annotation class at a time and choose “SQL Query.” If no SQL query is listed, then as long as the attribute information is populated in the feature class attribute table, annotation should appear.
If a SQL query is present, but your annotation is not getting written, review this article: HowTo: Automatically generate new feature-linked annotation for a feature class originally created using a SQL query.
2. Do your ID’s match?
When a new feature is created in the feature class, that feature is assigned an ObjectID (OID) automatically. That OID is used by the relationship class to populate the FeatureID (FID) field in the annotation feature class. If for some reason the OID and FID are no longer in sync, the annotation is no longer feature-linked because the relationship class does not know which two features belong together.
Signs that your ID’s are not matching would include:
- Your existing feature-linked annotation is no longer updating when you make changes to the feature attributes;
- You can no longer move a feature and have the annotation follow;
- Although you checked the SQL Query as described above, the annotation isn’t working correctly when you add a new feature to the feature class and populate the attributes.
- Select a feature from your feature class using the Select tool so that the feature is highlighted. The feature should appear light blue on the screen.
- Open the feature class attribute table and find the selected feature. Note the OID.
- Open the annotation feature class attribute table and do a search on the FID field for the OID of the feature you wrote down above.
If your OID and FID fields match, your SQL query is correct and all of your required attributes are populated in the feature class attribute table, then the problem could either be in your annotation configuration or your relationship class may need to be recreated.
First, check your configuration. In ArcCatalog or the Catalog window, right-click on your annotation feature class and choose Properties. Select the Annotation tab and ensure the following check boxes are selected:
If they are, follow this Step 24 to recreate your relationship class.
If your OID and FID fields do not match, you’ll need to manually go through your annotation attribute table and update the FID to match the correct OID.
You could do this in one of two ways:
- You could join the feature class attribute table to the annotation attribute table using the OID and FID fields. Any FID field without a match would need to be reviewed and changed to match the correct OID field. This approach is better for a 1:1 ratio of features and annotation,
- For a 1:M or M:N ratio, do a spatial join and add the attributes from the feature class to the annotation feature class. This way, you can manually examine all of the connections and make adjustments as necessary.
After updating the FID to match the correct OID, follow the steps in this Knowledge Base article to relink previously feature linked annotation.
If you’re in need of additional assistance don’t, hesitate to contact Support and log an incident.
Allison Rost, Technical Account Lead in Charlotte, NC
If you’re creating a custom Web mapping application that has a Map control in Visual Studio 2010 and the map doesn’t show when you’re running the application, first ensure that the map service displays fine in ArcCatalog, Server Manager and an out-of-the-box (OOTB) application created manager.
If the map displays as expected in those applications, the next step is to navigate to the Solution Explorer for the Web mapping application (WMA) in Visual Studio, right click on the Web application project and select “Property Pages”.
Then go to Build and select the correct “Target Framework”. If it is set to .NET Framework 4, change it to .NET Framework 3.5.
You will see a warning message regarding the change, but click on “Yes”.
Now rebuild the project (if required) and run the application again. You should be able to see the map now.
Just remember that .NET Framework 4.0 is not currently supported with ArcGIS Server .NET Web ADF at version 10.0 and that .NET Framework 3.5 SP1 is required.
Kripa J., ESRI Support Analyst – SDK Group, ESRI Support Services
In ArcGIS Desktop 10, Item Description launched from the ArcMap Table of Contents > Data > Item Description does not work
In ArcGIS Desktop 10, launching the Item Description for a layer by right-clicking on it from the ArcMap Table of Contents > Data > Item Description does not work.
Note: Launching the Item Description from the Catalog Window or ArcCatalog does work.
This is a known issue. For updates on the status, you can use bug number NIM057099. Esri is working on a permanent solution to this issue. In the meantime, please use the following workaround:
- Shut down ArcMap and ArcCatalog.
- Download the following ZIP file: Data Source Item Description window.zip.
- Extract the .reg file located in the ZIP file to your hard drive or desktop.
- Double-click the Data Source Item Description window.reg file. This adds a registry setting that enables the functionality.
- Open ArcMap.
- The Item Description launched from the ArcMap Table of Contents > Data > Item Description will now work.
Sorry for any inconvenience this may have caused. Please leave any comments in the comment section below this blog post. NOTE: You must be logged in to your Esri Global Account to leave comments.
- Jeff M., Desktop Development Lead – User Advocacy Group, Esri Support Services
Hello, this is Cassandra again, bringing you a blog post about my favorite thing about ArcGIS Desktop 10 – the Catalog window. In a nutshell, the Catalog window provides a tree view of file folders and geodatabases, just like in ArcCatalog, but directly within ArcMap. Need to add to add a feature class, but can’t quite remember where it is? Browse for it with ease in the Catalog window. Need to perform some geoprocessing and geodatabase organization but don’t want to shut down out of ArcMap? Do it in the Catalog window. Getting frustrated with schema locks on your geodatabases? Just stay in ArcMap and do your processes in the Catalog window.
The most common question concerning the Catalog window I’ve seen is ‘Where’s the preview tab?’. This question is easily understandable, especially since the Catalog button on the ArcMap Standard toolbar now opens the Catalog window, not ArcCatalog.
There is neither a Preview nor metadata tab directly available in the Catalog window. However, you can preview the data, view the metadata and more by right-clicking on the item and then select Item Description. The Item Description dialog box gives you access to view, print, edit, validate, export and import the metadata on the Description tab, as well as previewing the geography and table of the item on the Preview tab.
The Catalog Window includes a choice of three views as well. You can cycle through them by clicking the ‘Show Next View’ button.
For more information on the Catalog window, see the following help topic: What is the Catalog window?
Please leave any comments or questions that you may have under the Comments section below. NOTE: You must be logged in to your Esri Global Account to leave comments.
- Cassandra L., Desktop Support Analyst, Esri Support Services
I know how frustrating it can be when ArcMap or ArcCatalog crashes. A few years ago, I wrote a Knowledge Base article with different methods to resolve these crashes, as well as known issues that may cause a crash. In an effort to resolve these crash issues, ESRI Software Development implemented the crash reporting system. You might have seen this little window pop up the last time the application crashed:
You may ask yourself, where exactly do these reports go? Why don’t they write me back using the e-mail address I provided?
The error reports you submit are very useful for improving the product’s stability. When an error report is submitted, a server reviews the report to determine what component of the software caused the program to crash. If the behavior has been encountered before, the report is added to the defect report for that issue. But if the behavior is not recognized by the system, then a new defect report is generated to examine that issue. When a defect report is associated with multiple error reports, our product engineers make every effort to resolve the issue for the next service pack.
If you can identify a reproducible set of steps or a particular action that causes ArcMap or ArcCatalog to crash, please check my Knowledge Base article for a known issue in the Related Articles section. If you don’t see your scenario here, please submit your steps to reproduce to ESRI Support Services, and we would be happy to review your issue.
- Emeline R., Support Analyst, ArcGIS Server group, ESRI Support Services