Tag: ArcGIS 10
Image services are a great way to allow others to use your service layers within their GIS projects. Did you know you can actually allow users to download your source files? By default, this option already enabled when you publish a mosaic dataset. Continue reading
Search and Rescue (SAR) and GIS is an award-winning combination!
On November 3, 2011 a group of forward-thinking SAR volunteers and US National Park Rangers received
the prestigious Foundation Award for Excellence in Public Safety GIS from the National Alliance for Public Safety GIS Foundation.
This informal group was formed in Joshua Tree National Park in 2009 and has made incredible progress towards integrating GIS into missing person search operations (SAR-GIS). SAR-GIS has been used successfully on search operations in National Parks and Counties across the U.S. and Canada. You can join the SAR-GIS discussion group to find out more about the topic. Continue reading
- Only updates your files- no redundancy created
- Update are almost immediate
- A new raster dataset is created and the original file is left unaltered
- Choose many options: such as file format, cell size, resampling technique, and NoData value.
- This is the only option for some files: such as GRID and other files that cannot be updated (e.g. read-only files)
Depending on your workflow, both Update Georeferencing and Rectify have their advantages.
In ArcGIS 10, feature templates define all the information required to create a feature, such as the target layer and the attributes the new feature will receive. Most of the time, you interact with feature templates on the Create Features window. However, some editing operations present a dialog box containing templates that you can choose for the output for that particular feature creation workflow. For example, the Select Feature Template dialog box used with the Editor menu > Buffer command allows you to set the feature template that will be used to create the new buffer feature. The list of templates is filtered to show only editable and visible polygon or line layers in the map; feature templates for other templates are hidden and cannot be used for the buffer output.
If you are developing a custom command or tool that requires the user to specify a feature template for the output of your workflow, you have two options for working with or presenting feature templates in the map. You can require the user to select a template from the Create Features window or you can implement a feature template dialog box that works similar to the Buffer command. Often, implementing your own feature template dialog box is the better option, as you can ensure the user has specified a template that meets the criteria of your customization. For example, you may only want the user to choose from templates from certain layers or those that are of a particular geometry type.
If you decide to create your own template dialog box for a customization, you can start by downloading a sample that Esri has created and shared in the Editing Labs group on ArcGIS.com. This sample is a Visual Studio 2010 project written in C# that creates an add-in containing simple dialog boxes to display templates. The sample was modeled after the template dialog box from the Buffer command and contains the same controls and considerations for displaying feature templates. You can use some or all of the functionality from this sample for your own customization. It is important to note that the dialog box can only display existing templates; you must create, delete, and manage templates for layers as usual through the Organize Feature Templates window.
Using the Template Dialog Sample command
The sample creates an add-in command that provides a similar chain of dialog boxes as Buffer: clicking the command opens a dialog box containing a button that opens another dialog box with a list of feature templates. The command is called Template Dialog Sample, which is TemplateAppButtton.cs in the Visual Studio project. To explore the sample’s functionality in ArcMap, compile the project or install the add-in that accompanies the download. Then, drag the Template Dialog Sample command from the Customize dialog box > Commands tab > Editing Labs category and place the button onto any toolbar. The command is only enabled when you are in an edit session.
Click the Template Dialog Sample button on the toolbar to which you added it to display the template application form (TemplateAppForm.cs). Click the Template button on the Template App Form dialog box to open the Template Picker Form (TemplatePickerForm.cs). Similar to the Select Feature Template dialog box opened from the Buffer command’s dialog box, the Template Picker Form allows you to choose a template and search for templates by name, tag, and layer.
In this sample, the Template Picker Form displays feature templates from all visible point, line, and polygon layers in the current editing workspace. If you want to enable filtering by geometry type, for example, you can modify the sample code through an enumeration in TemplateAppForm.cs when calling the TemplatePickerForm.
Most of the internal work in the sample occurs in the TemplatePickerForm class. This class contains a Visual Studio ListView control to display the templates as ListViewItems arranged into ListViewGroups that represent the layers. Selecting a template sets the _currentTemplate variable back on the add-in button, which can be used to set the current Editor template target on IEditor3.CurrentTemplate. The template can then be used to help you create new features as described in the Working with templates section in the Using feature templates help topic.
Content provided by Sean (Editing Team)
Last week we made the ‘CityEngine: Philadelphia example’ available for download on the CityEngine resource center. The main comments we’ve received so far are:
- how do I get my GIS data into CityEngine, and
- how do I bring it back into ArcGIS?
So let’s do a roundtrip! Continue reading
VMware has published a technical paper describing the best practices for running ArcGIS Server deployed on VMware Infrastructure.
Geoprocessing can be used to automate many aspects of data compilation, including implementing a geodatabase topology. In my previous post, I created a model that imports data into a file geodatabase and performs initial data cleanup processing. Now, I will use geoprocessing with Python scripting to build a topology on the imported data. Although many spatial integrity issues were resolved by running the model, a geodatabase topology can help check for and repair any remaining errors.
The dataset I am using is a feature class of parcel lot line boundaries that began as a CAD file full of topological inconsistencies, such as lines that overlapped or did not connect to other lines. Once I create the topology and am sure the lines are correct, I will build parcel polygons from the lines and introduce all the features into my production enterprise geodatabase.
Creating a topology in a script
To build topology in an automated manner, I am going to write a simple Python script, add it to a toolbox, and run it as a regular geoprocessing tool. Essentially, the script just performs the functions of the New Topology wizard, but without requiring my intervention. In fact, this script could be developed without any programming by creating a model to perform these tasks and exporting it from ModelBuilder as a Python script.
When scripting, the ArcPy site package allows Python to access and run any of the geoprocessing tools in the ArcGIS system toolboxes, including the topology tools. The Topology toolset in the Data Management toolbox contains all the tools I need to add a geodatabase topology to the line feature class. The import arcpy statement adds ArcPy to a script and is at the top of every ArcGIS Python script.
Before I start adding the tools to the script, I define variables for the paths to the feature dataset, feature class, and topology. Because I created folders to store my tools and data following the recommendations in A structure for sharing tools, I can make the script more portable by setting these paths in relation to the folder containing the script. Since the folder locations are not hard-coded to match the C: absolute path of my hard drive, the script should run on someone else’s machine regardless of the machine’s directory structure.
With the paths defined, I first use the Create Topology tool to add a topology to the feature dataset. The syntax for the tool in my script is arcpy.CreateTopology_management(featureDataset, topologyName, “”), where CreateTopology is the name of the Create Topology tool, _management is the toolbox in which it resides, featureDataset is a variable I defined earlier representing the path to the feature dataset, and topologyName is a variable for the name of the topology. When working with topology, it is recommended to use the default cluster tolerance, which is the distance in which vertices are determined to be coincident. Since I want ArcGIS to calculate the cluster tolerance, I left the value blank as “”instead of supplying one.
Although that function creates a topology, it is currently empty and has no classes or rules in it. I can use the Add Feature Class To Topology tool to add my line feature class with the statement: arcpy.AddFeatureClassToTopology_management(topology, featureClass, “1″, “1″). If the topology contained multiple feature classes, I can set ranks so the feature class with the highest accuracy is not adjusted to match vertices in a feature class which is known to be less accurate. However, since I am using only one feature class, I leave the rank parameters as “1″.
Next, I set which topology rules to include by calling the Add Rule To Topology tool. When choosing which rules to add to a topology, there are a few rules that many editors commonly add to every topology, such as the line rule for Must Not Have Dangles. In the script, this rule is coded as arcpy.AddRuleToTopology_management(topology, “Must Not Have Dangles (Line)”, featureClass, “”, “”, “”). Because the rule only applies to one feature class that does not have subtypes and is not a rule between two feature classes or subtypes, the other parameters are left blank. I also want to make sure that the lines do not overlap or intersect themselves, so I include the Must Not Overlap and Must Not Self-Intersect rules as well. If I need to add more rules later, I can run the Add Rule to Topology tool or use the topology’s Properties dialog box in the Catalog window.
Once all the feature classes and rules have been added, my script validates the topology. The Validate Topology tool identifies features that share geometry, inserts common vertices into features that share geometry, then performs integrity checks to identify any violations of the rules that I defined for the topology. Since the topology has never been validated before, I am going to validate the entire extent of the data with the syntax, arcpy.ValidateTopology_management(topology, “Full_Extent”). However, when working in ArcMap, validating the visible extent of the map instead of the full extent limits the area to be validated and can be useful for very large datasets that take a long time to validate.
Finding and fixing topology errors
After the script runs, I add to ArcMap the resulting topology so I can inspect the results and fix any errors using the ArcMap editing tools. However, with all the previous automated QA work from my Import and Clean Lines model, the remaining manual edits are minimal in comparison to what they could have been without running it first.
The errors identified with topology are indicated by the orange-colored squares. Almost all of these are dangle errors that could not be fixed by the original model since they exceeded the tolerance value for the Extend, Trim, or Snap tools. The topology found only two Must Not Overlap errors, which I can fix by deleting one of the overlapping features. There are no violations of the Must Not Self-Intersect rule, indicating that the lines were split properly in the model. Using the editing tools on the Topology toolbar, such as the Error Inspector and Fix Topology Error tool, I can review each error to determine if the built-in topology fixes can be used or if the lines should be edited manually to resolve the topology error.
In some cases, the topology error may need to be marked as an exception, which is a valid violation of a topology rule. One of the most common examples of exceptions to the Must Not Have Dangles rule is a cul-de-sac road, which are dead ends that do not connect to other roads. However, when working with parcel lot lines, there are fewer scenarios that are valid exceptions. I do have some lines at the edges of the dataset that do not connect to other lines. I can either mark these as exceptions or choose to delete the features, depending on whether these features are supposed to connect to existing features in my enterprise database.
If an edit is made to correct a topology error, I have to validate the topology again to make sure the error no longer exists. After I perform a visual inspection and fix all the remaining topology errors, I can create new polygons representing landownership parcels using the geometry of the lines. If I attempted to create polygons from lines that do not connect to each other properly, either no polygons would be created or one large polygon would result where there should actually be two polygons. After creating the new polygons, I add the polygon feature class to the topology and check for any gaps or overlaps and make sure the parcel polygon boundaries are always coincident with the lot lines.
After implementing the topology and making edits in ArcMap, the lines and the polygons created from them meet standards for our spatial data. I can now introduce the features into the production enterprise geodatabase.
While a script tool or model may take time to set up initially, in the long run, it is quicker to automate data compilation tasks through geoprocessing whenever possible. I can run a tool as needed and re-run it later with different parameters and tolerances or apply it to other datasets. Scripts are particularly useful because they can be run at specified times as a scheduled task in Windows. For example, I could combine the tools presented in these blog entries into a Python script that imports a dataset into a geodatabase, processes it, and implements topology. If I set the script to run automatically in the evening after working hours, I am ready to start editing on clean data when I come into the office the next morning.
For more information:
The sample tools and data can be downloaded from the Editing Labs group on ArcGIS.com. An ArcInfo license in required to run the tools.
Content provided by Rhonda (Editing Team)
A few weeks ago we posted a blog regarding how to fix your mosaic dataset when the paths to the source data are broken. Like many other tasks in ArcGIS, there is a geoprocessing method of performing this task.
Find the broken paths
The first step is to find the broken paths.
1) Open up the Export Raster Catalog Paths geoprocessing tool
2) Input Data = your mosaic dataset
3) Export Mode = BROKEN
4) Output Table = a new table (either to a geodatabase or to a .DBF file)
5) Click OK to run the tool
Review the broken paths
1) Add the table into ArcMap
2) In the Table of Contents, right-click on the table and choose Open
3) Review the table to see how many different paths need to be fixed.
Remember, only the parent folder holding the images need to be fixed, not each image.
4) Right-click the first broken path, and choose Copy
This will actually copy the entire path to the image, but we can delete the file name in the next section.
5) You can either Hide or Close the table so you can see the rest of your ArcMap window.
Fix the paths
Now that we know the paths that are broken, we need to fix the paths.
1) Open up the Repair Raster Catalog Paths geoprocessing tool
2) Input Data: choose your mosaic dataset
3) Repair Mode = FIX
4) Original Path = paste your path, but remove the file name and last
You will get a warning that the path does not exist – this is normal
5) New Path = browse or type in the new path
6) Click OK to run the tool
You have now repaired the first broken path. If all your images are in the same folder, then you will have hopefully fixed all your paths. You may need to run through all the steps again until all your paths are fixed. All your paths are fixed when the output table from the Export Raster Catalog Paths tool no longer has any records.
CityEngine allows you to model and design your city in 3D based on GIS geometry, attributes and procedural rules.
It has been awhile since we released Esri CityEngine 2011 at the EUC in Madrid. In the last month we have been working hard on an ArcGIS – CityEngine urban planning example and we are happy to let you know it is available for download now in the gallery section on the CityEngine resource center.
This example highlights how CityEngine can be used to create and design 3D urban content based on GIS data input such as building footprints and street lines with attributes.
Starting point is a 3D geodatabase with:
building footprints with attributes such as ridge height, eave height and roof form
street center lines with attributes such as street width
vegetation locations with attributes such as vegetation type, rotation and size
street furniture locations with attributes such as furniture type, rotation and size
The example comes with a set of rules that allow you:
turn your building footprints into 3D textured buildings
turn your street center lines into 3D streets.
turn your vegetation and streetfurniture points into 3D models
Import existing 3D content such as 3D buildings, trees, cars and street furniture
do a redesign on any part of the city
You can download this CityEngine: Philadephia example in the gallery section on the CityEngine resource center.
For more information on how to:
bring your CityEngine models back into ArcGIS
turn your 2D features into 3D
go to the gallery section on the CityEngine resource center and have a look for the CityEngine to ArcGIS and 2Dto3D templates.
Esri R&D Center Zürich