Latest Contributions by AdamMesser1

From ESRI support: A HTTP dataset or an application when accessed through gallery, it enforces to pass the request over HTTPS.  This behavior is found to be a case defect within the application and is logged as a bug. Following are the details of the bug: BUG ID: BUG-000109990 Synopsis: In Open data, the Gallery Guard enforces the applications or datasets to open over HTTPS even when the applications or datasets are over HTTP. Status: In Product Plan ... View more

Courtney, It was nice to meet you at the UC. As we discussed following up on any future issues I'm sending another orphan/duplicate record from OD. The Montana Lakes record is a document link so no specific url for the item on our OD site. It can be located via search on our current our legacy site:  Search | Montana Fish, Wildlife & Parks  Item id: 41ed181dc6124fa9a2955bcb127b4a9b; You will note the 'Lakes' search returns 7 records in the summary and the page json response, but there are only 6 listed.  Testing on our new test OD site, shows this duplicate record in the list. There is only one item on our agol content list. If I unshare this item from our OpenData group, it will remove the valid record from our OD site after a short time but leave the orphan. Let me know if you need any additional information. Thanks again, Adam ... View more

All of our Open Data orphans have been resolved by ESRI support. All of our data visible on our OD site is through a single Open Data group on our AGOL site. Apparently the following steps removed the orphan layers: From the OD administration pages the OD Group was removed from the site. From AGOL the OD group was changed from Public to Private. These steps were then reversed. From AGOL the OD group was changed from Private to Public, and the group was added back to the OD site. Then on the OD site indexes were updated and the download cache reset. ... View more

Courtney Claessens‌ , Just a heads up that our GIS manager has logged this issue as a ticket as of last week and we are communicating with ESRI support. The first group above "In Open Data group, but not on Open Data site" has been resolved. The second "On Open Data site, but not in Open Data group" has not and now includes an additional item. ... View more

Courtney, Our process is scripted so I can describe that it, but likely cannot point you to a specific point when this occurred. We (Bill DaigleLydiaBaileyBill Daigle) maintain feature classes in SDE. When edits occur the data manager will designate the layer be updated in all dependent locations, including AGOL as a hosted feature service. Very large items are loaded as document links that point back to our web server for download. The feature service upload process takes one of two paths, with all tasks being automated via api calls which mostly use github ArcREST api package functionality. The only exception is the full item upload via arcpy.UploadServiceDefinition. If the layer is new or has a schema change, the existing AGOL feature service is deleted and replaced. If the layer only has record level edits, the features on the existing AGOL hosted feature service are deleted and then new records inserted into that item. If errors occur in the second process, we revert back to the first full item replacement option. Items are shared with everyone and our OpenData group which contains all items to be displayed on our OpenData site. We are aware of issues with item replacement due to the object id being changed. However, this is lower priority since the feature service url does not change, and thus we haven't noted major negative impacts on map and apps pointing to those replaced feature service items. Following is a summary of our existing data issues related to inconsistencies between our OpenDataGroup and OpenDataSite. Count of items in each location; Items in our ODGroup that should be showing up in the ODSite; Items that are orphaned, not in our ODGroup nor on our AGOL site anymore, and should be removed from the ODSite. Our evaluations also picked up erroneous duplicate records over the last several days, but those appear to have been cleaned up or fixed as of this morning. In that case, a search for a specific record would show one result on screen, but list 2 results and show duplicates with the same item id when the returned json was evaluated. Thanks for your help, Adam ________________________ Open Data Site Items:133 Open Data Group Items:132 ________________________ In Open Data group, but not on Open Data site ____________     id:  991f5239cf814ec6b86628b9e490fddd   name:  AIS Watercraft Inspection Stations   type:  Feature Service    url:  https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/FISH_AIS_INSPECTION_STATIONS/FeatureServer ____________     id:  b938ee0d87a1480aa988109cb963e13b   name:  Montana Lakes   type:  Document Link    url:  http://gis.fwp.mt.gov/arcgis101/rest/directories/arcgisoutput/webResources/metadata/refrnc/lakes.htm ________________________ On Open Data site, but not in Open Data group ____________     ITEM ID NOT IN MTFWP ITEMS LIST       id:  2b095b1f50074ad3803c7535804f50f9     name:  Snowmobile Trails Program PDF Map Index     type:  ItemLayer      url:  https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/FWPLND_WINTER_PDF_MAP_INDEX/FeatureServer/0 ____________     ITEM ID NOT IN MTFWP ITEMS LIST       id:  3a7ccdc9db804845b126d5bcaaed32fe     name:  Winter Trails     type:  ItemLayer      url:  https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/FWPLND_TRAILS_WINTER/FeatureServer/0 ____________     ITEM ID NOT IN MTFWP ITEMS LIST       id:  bbec615bc12446539758cee15a6868fe     name:  Montana Fish, Wildlife & Parks Warden Districts     type:  ItemLayer      url:  https://services3.arcgis.com/Cdxz8r11hT0MGzg1/arcgis/rest/services/ADMBND_RESPAREA_WARDEN/FeatureServer/0 ________________________ ... View more

Courtney, I think we have the same problem on our site. We (bdaigle) are evaluating the discrepancy between the number of items in our agol open data group (n=130), the OD Site Manager summary (126) and data tab (136 datasets 132 items). It appears that this is a continuation of Kevin Dunlop‌ issue of Phantom items in Open Data Beta‌ . Is the current solution to still send you the list of these items for deletion? I assuming the bug is still being worked on by your engineering team? ... View more

Thanks for the information Kelly. We have been successful in updating content using the rest api without retaining an sd file... For now at least. ... View more

Kelly Gerrow‌ it appears that your original answer may no longer be valid. The documentation  About hosted layers—ArcGIS Online Help | ArcGIS  indicates that "You cannot delete the service definition file until you delete the hosted feature layer." Can you revisit your answer to determine why this is? What functionality has been implemented that requires the sd file be maintained for the hosted feature layer? As of last weeks update to AGOL we cannot delete either shapefile or service definitions while the hosted feature layer exists. However, we can still send an api delete command to remove the service definition content item without error. We are now concerned that there will be lost functionality or errors that result from this deletion. Thanks - adamm Bill Daigle‌ ... View more

A resolved ticket per this issue indicated that a webserver update last week fixed the problem with downloads hanging. We were unable to replicate the incomplete zip downloads, so assume those issues were also resolved. Thanks for the clarity on caching. ... View more

Python toolboxes should not be considered isolated from your data management and analysis workflow. Many of us have a desire to use the functionality in our python toolboxes in conjunction with our other arcpy code. You could build an easy to import companion .py file to hold your toolbox business logic next to your actual toolbox  (ie. myTbx.pyt and myTbxFunctions.py), however, pyt files can be accessed and used in your interpreter or IDE by using imp. The example below shows this with our metadataUpdateItems tool. There are a couple important things to note if using pyt outside of ArcCatalog: python toolbox parameters have a valueAsText attribute that is set when running via ArcCatalog and will not be created when building the arcpy.parameter object in this manner. The alternative to valueAsText is to interpret the .value attribute as a string where needed Additional arcpy.parameter attributes are updated in ArcCatalog including, but not limited to, param.altered or param.hasBeenValidated, in the case below we added a variable to bypass those checks when not using in arcCatalog import imp def getParamByName(params, name):     outParam = None     for param in params:         if param.name == name:             outParam = param #import toolbox myTbx = imp.load_source('t',r'C:\dsCode\toolboxes\myTbx.pyt') #build the toolbox parameter objects list params = myTbx.metadataUpdateItems().getParameterInfo() #retrieve the parameter to update and change its value inLyr = getParamByName(params, 'inLyr') inLyr.value = 'C:\\temp\mySDElyr' #update the parameters #Note: the second argument is a runAsFunction binary T/F # this is to bypass the parameter.altered or parameter.validated checks of the updateParameters code myTbx.metadataUpdateItems().updateParameters(params,True) #update a list parameter agolTags = getParamByName(params, 'agolTags') agolTags.values = [u'wildlife (open data)'] #execute the toolbox myTbx.metadataUpdateItems().execute(params, None) ... View more