Latest Contributions by DavidMartin

Thanks RJ, I'll take a look at the Javascript pre-processing option. Cheers David ... View more

Does this "auto-picking" of transformations continue to be the case in 10.2? If so, is there any way of discovering what transformation is being auto-picked? For example, what would be the auto-picking logic in use behind a request to transform between WGS84 and OSGB36? ... View more

I'm guessing you're saying that this error only occurs when you deploy your application? And that it doesn't occur in your development environment? If that's the case, then the fact that it's being thrown by a local service is probably indicative of your having opted for a basic license (which won't support local services) instead of a standard license. I'd check the choices you made in the License Viewer, and hence the license code snippet that you've compiled into your application. ... View more

Also relevant here is that you can use tools like Add Field to add attributes to the Footprint layer. The Add Field tool, and others like it (e.g. Calculate Field) will take a Mosaic Dataset as an input (as-is) and will apply their actions directly to the Footprint layer. ... View more

This appears to be a tool validation issue. If I create this same model in Model Builder, and run the "Make Mosaic Layer" portion of it, I can then validate the entire model and it will run OK - whether within Model Builder or subsequently via the tool's UI (provided default parameters exist and I don't change them). Whenever I do change the parameters, however, it errors with the message that %MosaicLayer%\Footprint does not exist. I'd say that the tool is treating %MosaicLayer%\Footprint as a necessary prerequisite to running the model. If it's there (in memory?) due to previous runs of the model in Model Builder, then all's well. Otherwise it won't validate. Looks like a bug? I am also running 10.1 (SP1). However there is a workaround - using the Calculate Value tool in Model Builder. The model shown in the attached screenshot will run OK. ... View more

I believe it is, yes, unless someone else is about to educate us otherwise. Note too that the Calculate Geometry Tool will give you the lat/lon using the datum of the selected coordinate system. You have the choice of using the coordinate system of the layer or of the data frame. In the case of your screenshot, these are one-and-the-same and so you will get your lat/lon based on the GCS_IRENET95 datum. Assuming you want your lat/lon in WGS84 (perhaps you don't though?) then even the Caculate Geometry Tool will fail to give you the answer you're seeking here. Although admittedly you could coerce it by setting the data frame to use WGS84 and supplying ArcMap with the appropriate transformation as you do so. If you did that, you could then use the coordinate system of the data frame in the Calculate Geometry Tool and get the right answer that way. But in Model Builder I believe you'll need to follow the approach I've described above. A quick search has brought up a similar question from 2011, and the response then was effectively the same as the one I've given here, so unless there's been any new tools brought out since that could address your problem, then it looks like that's the approach you'll need to take: http://forums.arcgis.com/threads/37718-Calculate-Geometry-in-Model-Builder ... View more

I believe you should be able to project from one projected coordinate system to another, provided any necessary geographic transformation has been supplied (although I'll admit I haven't tested this). To do so would effectively involve the following sequence of events: 1/ un-project to local datum 2/ possible geo-transformation between datums 3/ project to new projection If you're having problems, you could always separate step 3 into a separate use of the Project tool. ... View more

I should perhaps have added that once you've projected your data, you can add the lat/lon as fields using the Add XY Coordinates tool (http://resources.arcgis.com/en/help/main/10.1/index.html#//001700000032000000). If you want to keep your data in its original projection, but have these lat/lon fields on that original dataset, then I guess you'd need to join the original feature class to the projected one (using Add Join tool) and then pull the fields across (using Add Field / Calculate Field tools). ... View more

Interesting. I wonder if this is version-specific? If I run your script (with or without the SetParameter line commented out), I don't get an xml file created - just a text file. I'm on 10.1 SP1. Even if I change the type of the output parameter in the script tool to "Dataset" or "Table", I still don't get an xml file generated. Glad you're sorted though! ... View more

What tool are you using? Normally, the sum of a number of rasters results in a new raster, with each cell value being the sum of the values for that cell within the input rasters. You appear to be looking at a summary statistic for the whole output raster. Is this the mean? Or the median? Differing cell sizes in the input rasters could perhaps contribute to your issue?? ... View more

I would look more closely at what you are doing with arcpy, in that case. I have just created the script below, and from it built a script tool with a single output parameter (a file). When I run it, I don't find an xml file is created, only my text file. import arcpy with open("e:\\filename.txt", "w") as f:      f.write("my_list_of_files_as_a_string")      arcpy.SetParameter(0, f) ... View more

The Buffer tool creates a new feature class to which to output its features, so that might be the reason you're getting the message about Feature Class B already existing? Instead, output the results of your Buffer operation to an intermediate feature class, then use the Append tool (http://resources.arcgis.com/en/help/main/10.1/index.html#//001700000050000000) to append these results to Feature Class B. Check then whether you're still getting messages about locks, and address that separately if you are. ... View more