Tools that honor the Level of Comparison Between Projection Files environment only execute if the input projections match to the degree that is specified.
Usage notes
- Similar projections and parameters that are defined in different ways will not match. For example, UNITS METERS and UNITS 1 (which are equal) will not match. Defining UTM and State Plane projections by their central meridians or parallels will not match with the same projection defined using the ZONE option.
- For any operation that copies the PRJ file, the first one entered will be the projection of the output, as with the TIC and BND operations.
- Use this environment to validate the input projections before running coverage tools.
Dialog syntax
- NONE—Any combination of projection information will result in a match. Either all input projections can be UNKNOWN, or each input can have a different projection defined. This is the default.
- PARTIAL—At least one projection file must be defined; the others can be UNKNOWN and will result in a match.
- FULL—All projection information must be specified and identical in the projection file of each input dataset.
Scripting syntax
arcpy.env.projectCompare = projectcompare_option
| projectcompare_option | Explanation |
|---|---|
NONE | Any combination of projection information will result in a match. Either all input projections can be UNKNOWN, or each input can have a different projection defined. This is the default. |
PARTIAL | At least one projection file must be defined; the others can be UNKNOWN and will result in a match. |
FULL | All projection information must be specified and identical in the projection file of each input dataset. |
Script example
import arcpy
# Set the projectCompare environment to FULL
arcpy.env.projectCompare = "FULL"