Even if I'm right, no doubt it's too little too late. You've given up or you already figured this out. However, casting your resolution as integer vs text is probably not the issue. Numeric values are passed in as strings all the time (i.e. arcpy.Buffer_analysis("roads", "C:/output/majorrdsBuffered", "100 Feet"...)). If units are left out (i.e. arcpy.Buffer_analysis("roads", "C:/output/majorrdsBuffered", "100")) the linear units of the input features' spatial reference are passed in. What seems to be the issue is the declaration (or definition? I forget which...) of ' df_export_width="", df_export_height="" '. Why exactly, I'm not sure. However, if you're using "Page_Layout" as the declaration for the data_frame variable, you don't need to pass in df_export_width or height. For example, this worked for me: arcpy.mapping.ExportToPDF(map,"P:\\Proj6\\USNVC\\Range\\geoPdf\\" + field + "d.pdf","PAGE_LAYOUT",resolution = "75") while this did not: arcpy.mapping.ExportToPDF(map,"P:\\Proj6\\USNVC\\Range\\geoPdf\\" + field + "d.pdf","PAGE_LAYOUT",df_export_width="", df_export_height="",resolution = "75") Notice that the resolution is passed in as a string in both.
... View more