2 Replies Latest reply on Feb 1, 2013 6:19 AM by huttarl

    getting the specified geographic transformation, or at least the GCS, of a data frame

      Hi all,

      I have a script that opens a user-specified MXD and processes user-specified layers in it. Part of the processing involves projecting the data from whatever GCS it's in, to whatever PCS the data frame has in its spatial reference.

      Sometimes, the input GCS and the output PCS are in the same datum (e.g. WGS_1984), and so I don't need to supply a geographic transformation to Project_management().
      Other times, they are not in the same datum; e.g. the data frame coordinate system might be Europe_Lambert_Conformal_Conic, which uses the datum ED_1950.
      If I don't supply the right geographic transformation (or lack thereof), the Project tool fails.

      How do I know what transformation to use?
      In the case where the datums are different, I can require that the data frame in the MXD file have a transformation method specified in its properties, e.g. ED_1950_To_WGS_1984_10.

      If that was the end of the story, my job would be simple: if the data frame has a transformation method in its properties, pass that to Project_management(), otherwise omit that parameter. The script would just look at the value of dataFrame.geographicTransformations.

      The problem is that on some machines, when I ask for mydataframe.geographicTransformations, I get a spurious value of "NAD_1927_To_NAD_1983_NADCON". So if the data frame has no transformation methods specified in its properties dialog, dataFrame.geographicTransformations returns ["NAD_1927_To_NAD_1983_NADCON"]. Which causes Project_management() to fail, if that transformation doesn't apply to the GCS and PCS actually being used. For example, when the data's GCS is GCS_WGS_1984, and the data frame's PCS is Asia_Lambert_Conformal_Conic, no geo transformation is needed (both have datum D_WGS_1984), and none is specified. So if I pass dataFrame.geographicTransformations[0] to Project_management() as the geographic transformation parameter, I will cause it to fail.

      If the data frame does have a transformation method specified in its properties dialog, then (on these same machines) dataFrame.geographicTransformations returns a list with "NAD_1927_To_NAD_1983_NADCON" as the first element, followed by the one specified in the properties dialogue.

      Again, this is on some machines. On others, the spurious "NAD_1927_To_NAD_1983_NADCON" doesn't appear, so I can rely on dataFrame.geographicTransformations to be set, or not, as appropriate.

      So my question is, where is this spurious transformation coming from, and how do I get rid of it, so that if I don't need a transformation, I can avoid passing a bad one to Project_management()? There's nothing in the Environment Settings under Output Coordinates / Geographic Transformations.

      Or, if I can't get rid of it ... maybe I can detect when the data's GCS and the data frame's PCS have the same datum, so I don't need a geographic transformation. In that case I would just not pass any such parameter to Project_management().
      The trouble with that approach is, I don't know how to get the datum, or the GCS, of a PCS spatial reference. I can look at dataframe.spatialReference.PCSCode, but spatialReference.GCSCode, GCSname, datumCode and datumName are blank (see http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/SpatialReference/000v000000p6000000/ - these properties are only available with a GCS). I know that ArcGIS desktop knows the GCS being used by the data frame, because when I open data frame properties, the Coordinate System tab tells me not only the PCS but also the GCS (including datum). But it's not available thru dataframe.spatialReference, that I can tell.

      So, if someone could tell me

      1. how to get rid of the uninvited NAD geographic transformation (preferred); and/or

      2. how to determine the GCS or datum of a PCS (can I look it up in some standard place?)

      I would be very appreciative.

      I'm using ArcGIS Desktop 10.0 by the way.