Latest Contributions by SebastianRoberts

I just found that you can use the dojo attachpoint for the button.  This is the html of the close button in the infowindow: [HTML]<a class="hide" dojoattachpoint="_hide" dojoattachevent="onclick:hide" style="margin-left: 303px; "><div class="sprite"></div></a>[/HTML] Here is how you can listen for the click event of the close button. dojo.connect(map.infoWindow._hide, "onclick", function(){       //your code here for handling the close button click. }); ... View more

I am part way there, but still having difficulty opening a separate attribute inspector for the related table.  I'd like to use the attribute inspector because it can handle the valiation for me.  From the documentation, it looks like you should be able to open the attribute inspector in a div outside the map.  As I understand it, the attribute inspector requires a feature layer and selected features in that feature layer.  Therefore,  I query the related records using queryRelatedRecords, and then select them using the selectFeatures method on the featureLayer for the related records. When I create the attribute inspector for the related records I assign it to a new div, but still the related records show up in the attribute inspector associated with editor widget and the primary point feature layer.  The div that it is supposed to show up in says "No features selected" (screen shots of app and debugger values attached).  This doesn't work, because I need to add a save button to the attribute inspector for the related records.  Is it possible to have two separate attribute inspectors open at the same time?  Is there some other better way to do this? //global variable for the related record feature layer relatedRecordMaintLayer = new esri.layers.FeatureLayer("https://myserver.net/ArcGIS/rest/services/internal/Sanitation_Inpsection/FeatureServer/1", {     mode: esri.layers.FeatureLayer.MODE_SELECTION, //QUERY_SELECTION is working as well     outFields: ['OBJECTID','PointID','Date','MaintType']    }); ....... //I am able to display the key field for the related record in a table, and this is the function to show the attribute inspector for the related record that is clicked on in the table.                    function showRelated(objID){     var flQuery = new esri.tasks.Query();     flQuery.where = "OBJECTID = " + objID + "";     flQuery.returnGeometry = "false";     propMaintLayer.selectFeatures(flQuery,esri.layers.FeatureLayer.SELECTION_NEW,function (selection)      {       var layerInf = [{'featureLayer':propMaintLayer,          'showAttachments':false,          'isEditable': true,          'fieldInfos': [          {'fieldName': 'OBJECTID', 'isEditable':false, 'tooltip': 'Object ID', 'label':'Object ID:'},          {'fieldName': 'Date', 'isEditable':true,'tooltip': 'Inspection Date MM/DD/YYYY','label':'Date:'},          {'fieldName': 'MaintType', 'isEditable':true, 'label':'Maintenance Type:'},          {'fieldName': 'PointID', 'isEditable':false, 'tooltip': 'Foreign key', 'label':'Foreign Key:'},          ]}];       attInspector = new esri.dijit.AttributeInspector({         layerInfos:layerInf         },         dojo.create("div",{id:"relateDiv"},"liRelate" + objID,"last")       );      }     );                         }                  } ... View more

Well I am part way there.  I am able to query the related records and show them in a list.  Clicking on one of the items in the list should launch the attribute inspector such that I can edit the corresponding row in the related table.  I'd like to use the attribute inspector because I believe it will take care of validation and allow me to track and save edits.  As I understand it, the attribute inspector operates on selected features for a feature layer.  Therefore I added the related table as a feature layer and perform a selectFeatures on it.  When the selectFeatures callback is called, I can see in the debugger that my featureLayer has the correct feature (table row) selected.  However, the attribute inspector (which references the same featureLayer) has an empty array for its _selection attribute, and displays "no features selected".  The API reference says that you can use a table to create a featurelayer, but could there be an issue with using a feature layer for a standalone table and doing a selection on it?  Or perhaps can the attribute inspector not operate on a featureLayer that is a standalone table?  Below is my code, and attached are the debugger screen shots. //the feature layer created in the init function propMaintLayer = new esri.layers.FeatureLayer("https://myserver.com/ArcGIS/rest/services/internal/Sanitation_Inpsection/FeatureServer/1", { mode: esri.layers.FeatureLayer.MODE_SELECTION, outFields: ['OBJECTID','PointID','Date','MaintType']}); //and the function called when a related record is clicked function selectRelated(objID){    var flQuery = new esri.tasks.Query();    flQuery.where = "OBJECTID = " + objID + "";    flQuery.returnGeometry = "false";    propMaintLayer.selectFeatures(flQuery,esri.layers.FeatureLayer.SELECTION_NEW,function (selection)     {      var layerInfos = [{'featureLayer':propMaintLayer,         'showAttachments':false,         'isEditable': true,         'fieldInfos': [         {'fieldName': 'OBJECTID', 'isEditable':false, 'tooltip': 'Object ID', 'label':'Object ID:'},         {'fieldName': 'Date', 'isEditable':true,'tooltip': 'Inspection Date MM/DD/YYYY','label':'Date:'},         {'fieldName': 'MaintType', 'isEditable':true, 'label':'Maintenance Type:'},         {'fieldName': 'PointID', 'isEditable':false, 'tooltip': 'Foreign key', 'label':'Foreign Key:'},         ]}];      attInspector = new esri.dijit.AttributeInspector({        layerInfos:layerInfos},        dojo.create("div",{id:"relateDiv"},"liRelate" + objID,"last")      );     }    );   } ... View more

Hi Curtis,   Thanks for your reply.  That improved performance greatly.  I just moved my temp directory creation inside the loop so that a new directory is created for every loop iteration (every 30 feature clasess), and now it is on target to finish in about 3 hours rather than 30.  Sebastian for x in groups:     #create the tempworkspace     tempWS = tempWorkspacePrefix + str(tempWorkspaceSuffix)     if not arcpy.Exists(tempDIR + os.sep + tempWS):         arcpy.CreateFolder_management(tempDIR, tempWS)     arcpy.env.workspace = tempDIR + os.sep + tempWS     while......................(rest of the loop as in my previous post) tempWorkspaceSuffix = tempWorkspaceSuffix + 1; ... View more

Jill,   Did you find any solution?  As we have added more overlapping parcels to our feature class (we now have 860), I too seem to be running into memory issues.  My script was crashing, so I added another loop that uses a smaller cursor and repeatedly deletes the searchCursor.  It no longer crashes, but interestingly enough, a "zone" is processed in about 20 seconds at the outset, and then towards the end of the 800 features, it slows down to about 5 minutes to process one zone.  Below is the python code that I am using. #create overlapping polygons with intersect tool (intersect with self, only creates partial parcels where overlapping) arcpy.Intersect_analysis([inputParcelLayer],FeatureIntersect,"NO_FID","","") #make feature layer, join with self intersected parcels, use result as overlapping parcels for zonal stats arcpy.MakeFeatureLayer_management(inputParcelLayer,"parcelsoverlap") arcpy.AddJoin_management("parcelsoverlap","APN",FeatureIntersect,"APN","KEEP_COMMON") arcpy.CopyFeatures_management("parcelsoverlap", FeatureZone) tempDIR = arcpy.GetSystemEnvironment("TEMP") #create scratch workspace name tempWorkspace = "tempWorkspaceForZonalStats" if not arcpy.Exists(tempDIR + os.sep + tempWorkspace):     arcpy.CreateFolder_management(tempDIR, tempWorkspace) arcpy.env.workspace = tempDIR + os.sep + tempWorkspace #input variables strFIDname = arcpy.Describe(FeatureZone).OIDFieldName zone = "zone" arcpy.env.cellSize = 2 #needed to reduce cell size because zonal stats crashes if the polygon is smaller than raster resolution gc.enable()  #enable garbage collection arcpy.CheckOutExtension("Spatial") cellAssign = "CELL_CENTER" priority = "NONE" newSelection = "NEW_SELECTION" # Make a layer from the feature class arcpy.MakeFeatureLayer_management(FeatureZone, zone) #Loop through features numFeats = int(arcpy.GetCount_management(FeatureZone).getOutput(0)) groups = [] bracket = 30 while(bracket < numFeats): groups.append(bracket) bracket = bracket + 30 groups.append(numFeats+1) for x in groups:     whileClause = '"OBJECTID" >= ' + str(x-30) + ' and "OBJECTID" < ' + str(x)     print whileClause     inRows = arcpy.SearchCursor(FeatureZone,whileClause)     #inRows = arcpy.SearchCursor(FeatureZone)     inRow = inRows.next()     while inRow:         #selct the fid to process         strID = inRow.getValue(strFIDname)         print ' processing objID: ' + str(strID) + 'of ' + str(numFeats) + ' total features.'         strQry = '"%s" = %s' % (strFIDname, strID)         arcpy.SelectLayerByAttribute_management(zone, newSelection, strQry)         #create a unique name for the zone         uniqueZone = arcpy.CreateUniqueName("zone.shp", arcpy.env.workspace)         uniqueTable = arcpy.CreateUniqueName("ZSasT", arcpy.env.workspace)         #create a temporary feature to use for zonal stats as table         arcpy.CopyFeatures_management(zone, uniqueZone)         outZSaT = ZonalStatisticsAsTable(uniqueZone, joinField, valueRaster, uniqueTable, "NODATA", "ALL")         #move to next record.         inRow = inRows.next()     del inRow     del inRows ... View more

Thanks cminde7 and Sashom,   I was having the same problem, and your solution fixed it.  I had to make a change because I symbolize my layer with only one marker symbol (instead of categories or class breaks), so I don't have an array of infos.  So the code below might be more robust and be able to deal with both situations. function fixIELayers(evt) {   // IE FIX FOR IMAGES NOT SHOWING IN FEATURE LAYER!!!   if (dojo.isIE)   {     var currentLayer = Hydrants; //map.getLayer(map.layerIds );     if(currentLayer && currentLayer.renderer && currentLayer.renderer.infos)     {         for (var i=0; i<currentLayer.renderer.infos.length; i++)      {       var url1=currentLayer.renderer.infos.symbol.url;       var url2=esri.config.defaults.io.proxyUrl+'?';       if (url1.indexOf(url2) != -1)        continue;       var url3=url2+url1;       currentLayer.renderer.infos.symbol.url = url3;      }     }else if(currentLayer && currentLayer.renderer && currentLayer.renderer.symbol)     {      var url1=currentLayer.renderer.symbol.url;       var url2=esri.config.defaults.io.proxyUrl+'?';       if (url1.indexOf(url2) == -1)       {        var url3=url2+url1;        currentLayer.renderer.symbol.url = url3;       }     }   } } ... View more

Just found this post.  Jamie's script worked great.  I am using this for zonal stats in a parcel model so only have a small subset of overlapping tax parcels (condos only).  In my case, I do an intersect with just one input (the parcel layer) to extract only the overlapping condo tax parcels. I added this to the beginning of Jamie's script,  then process only these parcels with the script.  In a second model, I do a selection to subtract these condo tax parcels form the county wide parcel feature layer.  I can then do a regular zonal statistics on the feature layer for all the remaining non overlapping polygons.  Just thought I would share this as a way to speed up the process if your dataset has a small subset of overlapping polygons. #create overlapping polygons with intersect tool (intersect with self to get overlapping) arcpy.Intersect_analysis([inputParcelLayer],FeatureZone,"NO_FID","","") ... View more

Richard, I did finally resolve this with the help of an Esri support request.  Just as you said, I needed to change the environment settings for the M values to "enabled", and set an M resolution of .0001 and M tolernace of .001.     Thanks for your response.  I appologize for not remembering to update my post after resolving it with the help of Esri. Regards, Sebastian Roberts ... View more

Sarah,   I haven't used the TOC, so I am not sure how it manages the layers, but in my widget that uses radio buttons, I just put the layers in an array, and then in the radio click handler I turn all layers off that don't correspond to the click event. Putting all the operational layers that exist in the main config.xml file into an array:    private function getLayers():void    {     if (configData && configData.opLayers){      for (var i:int=0; i< configData.opLayers.length; i++)      {      layerArray.addItem(configData.opLayers.label);      }     }    excluding any layers listed as exclude in the widget's config file private function excludeLayers(): void    {     if (configXML){      // exclude these layers      var layers:XMLList = configXML..excludelayer as XMLList;      for (var j:Number = 0; j < layers.length(); j++){       for(var i:int=0; i< layerArray.length; i++){        if(layerArray == layers ){         layerArray.removeItemAt(i);        }       }      }     }    } create radio buttons: for(var i:uint = 0; i < layerArray.length; i++)     {      radioBtn = new RadioButton;      radioBtn.groupName = "radioBtnGroup";      radioBtn.label = layerArray;      radioBtn.styleName = "WidgetText";      radioBtn.value = i;      radioBtn.height = 18      radioBtn.setStyle("textRollOverColor","#D0D0D0 ")      vBoxRadio.addChild(radioBtn);          } radio click handler:    private function radioClickHandler(event:ItemClickEvent):void    {     // update the visible layers to only show the layer selected     for(var i:uint = 0; i < layerArray.length; i++)     {      if (layerArray == event.label){       map.getLayer(layerArray).visible = true;      }else{       map.getLayer(layerArray).visible = false;      }      }    } ... View more

Andrew,   Did you ever find out if this tool is or will be avalaible, perhaps as an add-in?  I am specifically looking for the fishbone tool or and creating address ranges for road centerlines from points. ... View more