Latest Contributions by KevinHibma

I'd give a quick read of this topic: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Accessing_licenses_and_extensions_in_Python/002z0000000z000000/ Basically it states that unless you explicitly set the license level in the script, it will try to obtain/use the highest license level available. ... View more

Tools follow the same license level regardless of where you execute them (ArcMap or Python). Within the help if you look just inside each toolbox, there is a breakdown of how the tools are licensed. For example, see the Data Management toolbox. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Data_management_toolbox_licensing/0017000000t3000000/ ... View more

There is no usable information in the scrolling bar or the results window. I have had a process running for hours and I have no idea if it is working or not, how far along, etc. I also do not have a way to cancel it without crashing it creating locks, etc. Almost 5 and out nightly updates will start, so I cannot have this processing still. Oh, wait... I found if I right click the tool in the results window I have a cancel option. It would be nice if that was explained in the Help information on the results window. Thank you for your feedback. If you attempt this workflow in the foreground do you experience a crash as well, or is it specific to the background? Additionally, the information you mention is listed on cancel is in the help, please see this link on the Results Window: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Using_the_Results_window/002100000013000000/ ... View more

Based on my reading of his description, it looks like he's trying to run this as a script tool, not from the Python window. Hence, he would need arcpy.GetMessages() to return the document title to the geoprocessing window. arcpy.GetMessages is specific to getting messages from a tool which has executed. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/GetMessages/000v0000000p000000/ ... View more

Code is absolutely fine. I suspect you dont have a title in your map document. If you dont have a title, mxd.title will equal ''. In this case the AddMessage doesn't return anything. The title it is returning is from: File > Map Document Properties > Title: ________ Can you be sure you got something in there? Also as a check, take your code into the Python window. mxd = arcpy.mapping.MapDocument("current") mxd.title (the arcpy.AddMessage isn't going to do what you want in the Py Window ... View more

ArcGIS 10 does indeed support raster into KML conversion. It can be tricky though. You're basically taking a snap shot of the raster as we use the GroundOverlay mechanism in KML to display these rasters. So you may need to try a few exports with the differing export options to fine tune your KML. As Melanie points out, you may want to chop up your raster. The best explanation of rasters inside KML can be found here: http://code.google.com/apis/kml/documentation/regions.html starting at the 'Super-Overlays' section. It explains how the pixels of the image(s) works within KML clients. ... View more

Ok, I am working with arcserver, and my only goal is to be able to do whatever I want with a table....preferably by using a search cursor to feed it into lists, modify the values, and then output a recordset which can be displayed in arcserver. I will play with what you've put up for a bit a post again. I really do appreciate the help. Right - I wouldn't worry about the conversion then...just use the cursor right off the input features. Do you thing, then write out the new table. Here's some untested code off the top of my head import arcpy inTable = arcpy.GetParameterAsText(0) SearchRows = arcpy.SearchCursor(inTable) outTable = r'in_memory/OuTable' outRows = arcpy.InsertCursor(outTable) for row in SearchRows:         value1 = row.NAME                value2 = row.TYPE         value3 = row.SUPERFIELD                 singleOutRow = outRows.newRow()         singleOutRow.outNAME = value1         singleOutRow.outTYPE = value2         singleOutRow.outSUPERFIELD = value3         outRows.insertRow(singleOutRow)                arcpy.SetParameter(1, outTable) ... View more

I'm not sure this is exactly what you want to do, but try this code: import arcpy inTable = arcpy.GetParameter(0) arcpy.SetParameter(1, inTable) Maybe I'm confused why you're casting something to something else? If you want to inspect the attributes of the featureclass you can do it the same if its features or a table (recordset). I assume you'll be using a search cursor to loop through the attributes? And can you post a link to the doc where this isn't working? If you're using: table = arcpy.GetParameter(0) result = table optable = result.getOutput(0) Result should be the result of a GP operation.... result = arcpy.TableToTable_conversion('inputTable','in_memory','outputTable) optable = result.getOutput(0) ... View more

It should be forward compatible. What do you mean by it doesnt work? If you're getting a red-x over the model, you may just need to edit it, save it and it should work. Short of that I'd need more information to help. ... View more

My comments are based entirely off the error message. It sounds like your JavaScript code is correct from everything you've done.... Start Time: Wed Apr 13 11:32:31 2011 ERROR 010160: Unable to open raster t_t966\t_t966. Zonal statistics program failed ERROR 010067: Error in executing grid expression. Failed to execute (Zonal Statistics as Table). It looks like you have the data inside your c:\arcgisserver\ directories? If so, you can probably rule out ArcGISSOC account permission problems. Next question is how are you referencing the data? It almost seems like you're referencing it as a raster layer - thus the tool is expecting an associated map service which holds the layer. Is this true? Or is the raster a "raster dataset", thus the raster parameter is pointing to something like c:\arcgisserver\rasterdata\t_t966 .... or something like that. ... View more

As for your original question about customizing the python window in ArcMap - yes. Right click in the window and select "format". You can change font style/size as well as color. I'd never recommend fooling around in the registry - but if you're savvy 🙂 you can export the registry for the PyWindow and make that a "script". I take my registry export and just double click it on whatever machine I'm on to get "my" Python Window. After modifying the Py Window in ArcMap, take a look around HKEY_USERS\< users >\Software\ESRI\Desktop10.0\ArcToolbox for the keys. (at your own risk of course) ... View more

Hello, Your concerns have been echoed in the following ideas thread: http://ideas.arcgis.com/ideaView?id=087300000008HslAAE I'll attempt to explain the goal with background processing. First and foremost it was designed as a productivity enhancement. By pushing GP processing into a separate process, you are free to continue interacting with ArcMap. Background processing wasn't designed to keep the percentage complete "in your face," in the same way as a tool does with foreground execution. The purpose of the bar at the bottom is to show: a) you do have something executing b) give you a general idea of how far from complete the process might be Second, while it wasn�??t designed to be a performance enhancement, I�??ve heard cases where a task has finished in less time when executed in the background vs. if it was done in the foreground. Most of these cases make use of newer operating systems (Windows 7) and machines with more RAM (4+ GIG). I don�??t have benchmarks, only the comments from employees and users who have passed on their experiences. If you want more detailed information from background processing, this is available within the Results window(Geoprocessing Menu > Results Window). Here you have access to the same messages you would if the tool executed in the foreground. There is also a little "clock" which again gives you an idea of how far along the process is. What I'm trying to figure out is the balance of staying productive (your tool is executing in the background) and understanding when it might finish (some sort of % complete). There are all sorts of cases that have different requirements: short execution, long execution, executing many tools in a row which depend on previous results. Each situation may require a different amount of feedback from the tool. A 30second buffer might have different expectations of messaging than a 14hour batch raster conversion job. This said, please don't feel I'm dismissing your concerns, because I definitely hear you. I'm simply explaining the concept and some of the rationale behind background processing. Since the release of 10, through comments on the forums, the Ideas site above, etc, it appears clear that a good number of people are interested in more comprehensive reporting while a tool is executing in the background. This is something we're investigating and will improve as we can. As I said above, the biggest part of this is finding the best single solution for all types of background jobs. Background processing will never have comprehensive reporting to the same degree as you get when a tool executes in the foreground, simply because that isn't the point of background. The point is you can continue doing other tasks in ArcMap and the how close your job is to done should just be a passing thought. If you need all the messages as the tool executes then perhaps the classic foreground style of processing is a better fit to your workflow. (Background processing is a choice) For the specific case you mention - I can't say I've seen that behavior (but that isnt to say it doesn't exist). It seems quite likely that this is specific to the tool/data/background processing. The first couple service packs and our development of 10.1 we've identified and fixed more of these one off tool specific cases. Hopefully you'll continue to see improvements with each release. Thanks for voicing your concerns. If you�??re seeing what you think might be a bug and can share your workflow or data, I�??d be interested in reproducing it. Feel free to email me, [email protected] and we can set something up. If anyone has suggestions, please feel free to add them here or email me. We are listening. ... View more

I don't think that is entirely true.  There have been lots of my models and scripts that seem to have trouble. Could you post something from a previous version which doesn't work in 10? ... View more

Using the instructions here: http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Adding_and_removing_tools_on_menus_and_toolbars/002400000005000000/ You can add and remove whatever tools you want to this drop down. ... View more

Well it all depends how you are publishing. If you're publishing a standalone tool you're working with featureclasses (something on disk). If you're publishing as a tool layer (with an MXD), you're working with layers. The Select Layer by Location tool only works with layers. So if you're publishing a toolbox, you need to convert your input points into a layer (Make FeatureLayer), then you can use a feature set to make a query against it. In setting up your script tool, create a new input parameter. Make it of type "Feature Set" and make sure to set the schema to the path of a polygon featureclass. You then take this input and use it as the selection with Select Layer by Attribute. There is absolutely no problem in scripting this - this however is one of those workflows which becomes real easy when done in ModelBuilder. Maybe you want 2 tools? The ModelBuilder portion to get the data you need, then a script which just takes those points as input and does the FTP (or whatever else you may need). Just a thought. ... View more