Skip navigation
All Places > Esri Technical Support > Blog > 2011 > May
2011
Imagine you're the GIS Data Manager for New York City and receive a request for data from a consultant for Central Park. The data request included roads, streams, soils, buildings and other feature classes that are stored in the master geodatabase for the city. Instead of providing the entire geodatabase, you clip the data down to just the park boundary.

In order to clip the data, you have the options to clip the features individually or set up a batch clip. However, there's a more efficient way. With the iterator functionality available in ArcGIS 10, a simple model using the Iterate Feature Class iterator and the Clip tool can provide an efficient way to extract the subset of data.

Within ModelBuilder add the Iterate Feature iterator (Insert Menu > Iterators > Feature Classes) and the Clip tool.  Connect the iterator output feature class as the input to the Clip tool.

Below are the parameters that can be specified for each of the components.
    • Iterate Feature Classes
      • Workspace or Feature Dataset
      • Wildcard
      • Feature Type
      • Recursive
    • Clip
      • Input Features
      • Clip Features
      • Output Feature Class
    • XY Tolerance

For the clip output feature class, you can use a variable based upon the name being generated from the iterator.   An example of this can be seen in the interface below with the percent symbols.Examples of inline model variable substitution

Based upon the variable for the output feature class name, the output of the model keeps the original name with ‘_clip' added on.

After setting up the model and defining the desired parameters, this process can be accessed from your toolbox to easily clip a workspace or feature dataset for any project requiring you to work with only a subset of you master data.

The above model example can be downloaded from the ArcGIS Geoprocessing Model and Script Tool Gallery: Clip Workspace.Timothy H., Support Analyst - Geodata Raster Group, Esri Support Services
The ArcGIS 10.0 Service Pack 2 (Desktop, Engine, Server) Page Layout Map Surround Patch is now live at the Resource Center.

The patch addresses a crash in ArcMap when opening or savings some map documents in ArcGIS 10.0 SP2. Any map including a map surround that's been saved to version 9.0/9.1 or 8.3 using "Save a Copy" can trigger the crash. Since there's no way to know if a document was saved to a previous version, we recommend that all users install this patch.

For more details and to download the patch, please visit:

http://resources.arcgis.com/content/patches-and-service-packs?fa=viewPatch&PID=17&MetaID=1767



"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.

You can check for mismatched IDs by reviewing the OID and FID fields in your feature classes. For example:

  • 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,

Or

  • 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



Last month, we announced the release of the English version of Service Pack 2 for ArcGIS 10.0. We are pleased to announce that Service Pack 2 for ArcGIS 10.0 is now available to download in French, German, Japanese, Simplified Chinese and Spanish.  

This release contains performance improvements, maintenance fixes and includes all updates delivered since ArcGIS 10.0. 

We recommend that customers using ArcGIS products at version 10.0 or 10.0 SP1 download and install this service pack at their earliest convenience to ensure the highest-quality experience when working with the software.                      

If you have any questions or run into issues with the installation, please contact Esri Technical Support at 1-888-377-4575, option 2, or visit the Support site. Users outside the United States should contact their local distributor for help.

ArcGIS 10 (Desktop, Engine, Server) Service Pack 2 Annoucement 


Have you ever added a raster image to your map document only to find that some of the georeferencing tools are not available? You know you've done this many times in the past, but what's different this time?

A quick test to identify any issues is to add the image to a new blank map document instead of an existing map document. If the tools are available in the new map document, then one of the reasons for the problem may be that your data frame in the existing map document is rotated. ArcMap can't apply a double-transformation to the raster.

Here are the only functions available when the data frame is rotated:

  • Update Georeferencing*
  • Rectify*
  • Reset Transformation*
  • Flip or Rotate functions
  • Rotate
  • Shift
  • Scale

*Available once image has been modified.

Simply clearing the data frame rotation will activate the following functions:

  • Fit to Display
  • Auto Adjust
  • Add Control Points
  • View Link Table

For more information on why your georeferencing toolbar may be grayed out, please reference the related links below.

-Timothy H., Support Analyst - Geodata Raster Group, Esri Support Services - Charlotte, NC

Related Links:

Problem:  The georeferencing toolbar is greyed out

The GIS Encyclopedia: Georeference

Working with Rasters: Georeferencing



geonetadmin

We're on Twitter!

Posted by geonetadmin May 9, 2011

Are you one of the more than 10 million people sharing thoughts on Twitter? If so, follow us @EsriSuptInfo. We're there to share news and exciting information, and to interact with the active GIS community. Tweet directly at us with feedback, questions or if you just have something interesting to share!

 


Have you ever added a raster to an MXD and noticed that it looked different? Or created a mosaic dataset or raster catalog and suddenly, the rasters are so bright, you think, "What did ArcMap do to my raster?!"

Well, I'll save you a Tech support call. There is a relatively simple reason why your raster is now so bright: there is a "stretch" being applied to the raster, making it brighter.  Applying a standard deviation to a raster with statistics is the default behavior in ArcMap because the stretch will improve the display of most rasters, but there are a few situations where the stretch is not appropriate.  

In order to turn off the stretch, open up the properties menu of the raster from the table of contents and click Symbology. The dialogue may differ depending on the type of data, but the components are the same. To see if your raster has a stretch, look below the "Display NoData as" button to the section indicated as - you guessed it - Stretch. Under that, you may notice the usual default setting as Standard Deviation. To turn off the stretch, simply switch that setting to "None" and click Apply or OK. Your raster should now look more like the original if you are using a mosaic dataset or raster catalog. 

So, why did this happen and where was the setting to control this effect?  Well, it depends on the version of ArcGIS Desktop you're using. In ArcMap 9.3.1., the control will be under Tools > Option > Raster > General, titled "Display raster datasets with contrast stretching." Uncheck the box.

In 9.3.1:

In ArcMap 10, the dialogue will be under Customize > Options > Raster > Raster Layer, titled "Stretch Type". Select None. 

Both of the settings will prevent ArcMap from displaying the rasters with a stretch initially. By default, the stretch is automatically applied to all rasters with statistics added to ArcMap. Deleting the statistics will also prevent the display from being stretched. Related ArticlesJeff S. - Geodata Raster Support Analyst 

Filter Blog

By date: By tag: