Latest Contributions by OwenEarley

You could either place the command arguments in your script as constants or pass them in via tool parameters. # Option 1 - Get feature class from tool parameter arg1 = arcpy.GetParameterAsText(0)  # Define static parameters ARG2 = "ABC" ARG3 = "123" ARG4 = "456" ARG5 = "#" ARG6 = "XYZ" ARG7 = "#"  # Process parameters into command line if ARG2 != "#":     command.append("-o")     command.append('"'+ARG2+'"') Note - there is no particular language construct to declare a constant in python, it is just a variable. They are typically declared as variables with uppercase names. # Option 2 - Get all variables from tool parameters arg1 = arcpy.GetParameterAsText(0) arg2 = arcpy.GetParameterAsText(1) arg3 = arcpy.GetParameterAsText(2) arg4 = arcpy.GetParameterAsText(3) arg5 = arcpy.GetParameterAsText(4) arg6 = arcpy.GetParameterAsText(5) arg7 = arcpy.GetParameterAsText(6)  # Process parameters into command line if arg2 != "#":     command.append("-o")     command.append('"'+arg2+'"') The second option allows you to change the parameters without editing the script. However, you will need to create all of the parameters in the tool properties and give them default values. If they are constant values then I would probably go with option 1. Owen www.spatialxp.com.au ... View more

This issue appears to be related to your loading images. <script type="text/javascript">  ...  // Keep a reference to the loading icon DOM node.  var loading = dom.byId("loading");  var loading1 = dom.byId("loading1");  var loading2 = dom.byId("loading2"); In your HTML there is an image element with id="loading2": <img id="loading2" src="images/loading2.gif"></img> However, there are no elements with ids of "loading" or "loading1" in the page. Your extractByCounty function attempts to show the element with id "loading": domStyle.set(loading, "display", "inline-block"); Your extractByUnit function attempts to show the element with id "loading1": domStyle.set(loading1, "display", "inline-block"); In both cases these elements do not exist in the HTML so you are getting the 'e is null' error when the Javascript code attempts to set the style of the element. You could either change the Javascript to use the same loading image element ("loading2") or create the other two HTML image elements to fix the issue. Owen www.spatialxp.com.au ... View more

I created a cut-down version of your code here: http://jsbin.com/dimifaju Try running this in Chrome with the developer tools open - showing the console output. From what I can see the toolbar events are all working and your extractMethod variable is being updated. Also, clicking on the Extract Data button calls myFunction and the extractMethod variable is available. In switch statements I put the default as the last option. For these type of switching functions I also normally place the actual code for a task in their own functions. This makes it easier to read and simplifies testing as you can pass test values directly into the functions. function myFunction() {  console.log("Extract using method:", extractMethod);  switch (extractMethod) {     case "extractByCounty":    console.log("Switch result is: extractByCounty");    var county = document.getElementById("sel_county").value;    extractByCounty(county);    break;   case "extractByUnit":    console.log("Switch result is: extractByUnit");    var unit = document.getElementById("sel_unit").value;    extractByUnit(unit);    break;   default:    console.log("Switch result (default) is: ", extractMethod);         extractByPolygon();    break;  } }  function extractByPolygon(){  console.log("Run extractByPolygon code");   // code to extract by polygon }  function extractByUnit(unit){  console.log("Run extractByUnit code:", unit);  // code to extract by unit }  function extractByCounty(county){  console.log("Run extractByCounty code:", county);  // code to extract by county }    Now It still does not transmit the value to the query in the switch statement.    Not sure why this is - try a console.log (see code above) as the first line to see if it is being called. The jsbin version (http://jsbin.com/dimifaju) is working as expected in this regard.    Owen www.spatialxp.com.au ... View more

This really depends on your accuracy requirements and the intended purpose of the georeferenced map. You can georeference any map image to a basemap. The result will end up with the spatial reference of the World Street Map basemap. Which may or may not be appropriate for your intended purpose. If you are after accuracy then you will get better results using other basemap data such as a road centers or a land parcels. It depends on what features are in your overlay map that you can use as georeferencing control points. Ideally, your overlay map and the basemap have shared features that can be used for control points. Owen www.spatialxp.com.au ... View more

I don't think the issue is with the locator, it looks like the schema lock is happening when the second process attempts to copy rows to the DBF file: CRWInspectionLogCopyRows = os.path.join(scratch,CRWInspectionLogCopyRows.dbf) ... if result == 0:    arcpy.AddWarning("Process terminated."); sys.exit() else:    # The next line is probably the cause of the schema lock:    arcpy.CopyRows_management(CRWInspectionLog, CRWInspectionLogCopyRows, "") The DBF file will be locked by the first process and the second process will not be able to write to the same file while it is open. In your script this file would be the same for all users: E:\geoprocessing\Building\Outputworkspace\CRWInspectionLogCopyRows.dbf To avoid this on the server you should remove the line that specifically sets the scratchWorkspace: # 2. Set geoprocessing environment scratch = arcpy.env.scratchWorkspace arcpy.env.scratchWorkspace = r"E:\geoprocessing\Building\Outputworkspace" # - REMOVE this line arcpy.env.overwriteOutput = True Change to: # 2. Set geoprocessing environment scratch = arcpy.env.scratchFolder arcpy.env.overwriteOutput = True Then when simultaneous users run the script they each get a system generated job/scratch directory and the DBF files can be created without any locking issues. Alternatively, you could use some random temp file name for each DBF if you want to keep your specific scratchWorkspace. This way each process is writing to a different DBF file. Hope this helps. Owen www.spatialxp.com.au ... View more