Compute Dirty Area (Data Management)

Summary

Identifies an area within a mosaic dataset that has changed since a specified point in time.

Usage

Syntax

ComputeDirtyArea_management (in_mosaic_dataset, {where_clause}, timestamp, out_feature_class)
ParameterExplanationData Type
in_mosaic_dataset

The input mosaic dataset.

Mosaic Layer
where_clause
(Optional)

An optional SQL query that can be specified to only process a specific subset of data.

SQL Expression
timestamp

Specify a date and time. All mosaic items modified after this date will be used to compute the dirty area.

Currently, there are two types of date formats supported:

  • XML time syntax: YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss.ssssZ, 2002-10-10T12:00:00.ssss-00:00, 2002-10-10T12:00:00+00:00
  • Non-XML time syntax: 2002/12/25 23:59:58.123

For more information about the formatting of the time string, refer to the Usage Tips.

String
out_feature_class

The output feature class where the dirty area polygons will be created.

Feature Class

Code Sample

ComputeDirtyArea example 1 (Python window)

A Python sample for ComputeDirtyArea.

import arcpy
arcpy.ComputeDirtyArea_management("c:/workspace/fgdb.gdb/md", "#", 
                                  "2010-01-12T18:00:00.00-08:00", "dirtyarea.shp")
ComputeDirtyArea example 2 (stand-alone script)

A Python script sample for ComputeDirtyArea.

##===========================
##Compute Dirty Area
##Usage: ComputeDirtyArea_management in_mosaic_dataset {where_clause} timestamp
##                                   out_feature_class

try:
    import arcpy
    arcpy.env.workspace = "c:/workspace"
    
    # Find the area changed after 6:00pm Jan 12th 2010
    arcpy.ComputeDirtyArea_management("fgdb.gdb/md", "#", "2010-01-12T18:00:00.00-08:00", "dirtyarea.shp")                                              
    
except:
    print "Compute Dirty Area example failed."
    print arcpy.GetMessages()

Environments

This tool does not use any geoprocessing environments

Licensing Information

ArcView: No
ArcEditor: Yes
ArcInfo: Yes

10/27/2014