Latest Contributions by BarnabyRockwell

Hi Robert, Many thanks for the new widget version for WD 1.2.  If you Alt+click on widget header, you get this popup: Shouldn't it say that the widget is designed for WAB 1.2, not 1.3?  Also, there are some spelling errors..."This widget allows identifying features on the map." Cheers, Barnaby ... View more

That works perfectly.  Good job!  ... View more

Robert, It looks like 1.2 has lots of profound changes.... The LocalLayer widget, the most important widget of all, is particularly effected. Thanks, Barnaby ... View more

Robert, I get the same error with the widget when I invoke it from an app that was imported into 1.2 from 1.1.  It was working fine in 1.1. Cheers, Barnaby ... View more

I wiped WAB Dev 1.2 and installed it again from scratch, and imported one of my apps from 1.1. This time, the Layer List shows the layers which were added using LL widget (v1.6), but the layer names have all been replaced with the REST service directory name: All my services lie within the usminmap server directory.  I'm using ArcGIS Server 10.3.1.  Other than this layer name issue, everything else about the LL widget seems to work fine so far... Cheers, Barnaby ... View more

Hi Robert, The ID widget (v1.1.2) looks weird at the top using WAB Dev 1.2.  The example shown is where I have nested the ID widget and the Query widget into one compound widget: Cheers, Barnaby ... View more

Robert and Adam, Using v1.6 of this widget and WAB Dev 1.2, there seems to be an incompatibility with the WAB LayerList widget.  Using apps imported from WAB Dev 1.1, when I click on the Layer List widget, no layers load (it just hangs).  Layers themselves (added using LocalLayer widget) appear fine in viewer, but I cannot switch between them since nothing is visible in the Layer List widget.  Any ideas? An odd thing: Using an imported app that uses an AGOL Web Map for service layers instead of the LocalLayer widget, the Layer List still hangs.  What the....?  Perhaps the issue has nothing to do the the LL widget, but is a bug with WAB Dev 1.2 Layer List widget?  Best regards, Barnaby -- Edit:  The information in \client\stemapp\jimu.js\LayerInfos\LayerInfoForMapService.js has changed from WD1.1, so the instructions on how to modify this file to get the LL widget to work may have to be changed.  For example, there are no longer lines that read as below: var url = this.originOperLayer.url + '/' + subId; (now it is var url = this.layerObject.url + '/' + subId;) var url = this.originOperLayer.url + '/layers'; (now it is var url = this.layerObject.url + '/layers';) ... View more

Got it.  Thanks.  I haven't yet had the chance to test the functionality of the new widget version, but I did update all my WAB apps with it. ... View more

It could become confusing to set layer visibility using the widget, overriding visibility as set in the mxd before publishing.  There may be advantages to this new (currently non-functional) capability, but I am having difficulty imagining them now. ... View more

Great, thanks for the update, Robert! It looks like the various files haven't been updated with the 1.6 version number.  For example, the manifest.json shows version 1.4, and the README.md shows 1.5.1. Best regards, Barnaby ... View more

From ESRI Tech Support: After further testing, I have been able to reproduce your machines' behavior. I noticed that after installing the following Server 10.3 patches, and upgrading to Server 10.3.1, the old raster services would fail to restart, and new ones would not publish. As with your instances, repairing the installation fixed both of these problems: ArcGIS 10.3 for (Desktop / Server) NITF and NCDRD Quality Patch ArcGIS 10.3 for Server Map Cache Consumption Patch ArcGIS 10.3 for Server sync with related records Patch ArcGIS for (Desktop, Engine, Server) Migrate Storage for Oracle Patch ArcGIS 10.3 for (Desktop, Engine, Server) Spatial Statistics and Space Time Pattern Mining 2 Patch ArcGIS 10.3 for Server Site Creation Failure and Service Startup Performance Patch ArcGIS 10.3 (Desktop, Engine, Server) Geocoding General Maintenance Patch ArcGIS 10.3 (Desktop, Engine, Server) Geodesic Buffer Method Patch ArcGIS 10.3 (Desktop, Engine, Server) PDF Export for non-US decimal separators Patch This has been published as BUG-000088077. Regarding the ability to identify cells on a dynamic map service, I've submitted an enhancement request to allow this in Web AppBuilder (ENH-000088078). However, I can't do the same for the Flex Viewer, as it is being deprecated. I hope they do implement that enhancement request, as it will allow pop-up-like identification of pixel attributes from thematic rasters in dynamic map services, which is currently possible only using a custom ID widget.  ... View more

More to add.  The problem appears when one or more sublayers of a service are turned off by default in the mxd being published.  Here is an example: Note the "Alaska" dynamic service, which is turned off by default using the Local Layer widget.  In it, all three layers (Eastern Alaska Range, Pebble Cu-Au-Mo..., and Seward Peninsula) are on by default (as set in mxd).  But in the Seward layer, one of the sublayers (ASTER, shown in red above) is off by default.  This causes a slew of problems.  When the Alaska service is turned on in WAB app, the Seward Landsat 8 data (shown in blue above) are displayed as they should be, but its attributes will not show in the Legend widget, and the ID widget will not show any results for it when a pixel is clicked.  If the ASTER sublayer is turned on, then all behavior becomes normal (Legend is shown and ID widget works). It looks like an initialization problem that is removed once sublayers are toggled. Of course, the effect of the problem can be minimized by always making all sublayers turned on (or off) by default in the mxd, but this constraint is unfortunate as it limits the ability to customize how complex WAB apps appear when they are first opened. If the Landsat 8 sublayer is moved to above the ASTER sublayer before the service is published, the same problems occur. This is a major problem with the Local Layer widget that effects the behavior of default and custom WAB widgets.  Please let me know if you need more info. ---- Edit:  The problem can also be solved by moving the "Seward Peninsula" layer above the "Eastern Alaska" and "Pebble..." layers in the mxd before publishing. ... View more

Adam and Robert, I believe that I am still getting incorrect layer display in complex layering situations depending on whether layers are on or off in the published mxd and/or whether the (dynamic) layer is on or off by default in the WAB Dev 1.1 app. The issue can be seen in this app ArcGIS Web Application in the "ESRI 2013 Geographic Data" dynamic vector layer at the top of the layer list, added using the Local Layer widget (v1.5.1).  This layer is turned off by default in the WAB app.  Note that service is NOT tiled. This shot shows an area crossed by a state boundary (highlighted in red): This shot shows the TOC in the Layer List widget and the incomplete display of layers.  All I have done here is turn on the "ESRI 2013 Geographic Data" layer, turn off the Landsat 7 layer, and turn off the ESRI 2013 Geographic Data/World Map layer.  Note that none of the layers under ESRI 2013 Geographic Data/USA Thematic Maps/Basemap Layers are displaying even though they are turned on by default in the mxd (shown by checked layers in the TOC). Here is a shot showing correct layer display that occurs after I have toggled the "Basemap Layers" layer in the service off and then on. I think you should be able to duplicate this issue by trying out my WAB app.  The issue does not occur in a Flex viewer using the same services: National Map of Surficial Mineralogy Let me know if you need more info. Best regards, Barnaby ... View more

Robert, Bingo.   Problem solved.  When a service has multiple layers, one of which you want to exclude from ID results, just add the layer "name" from REST endpoint, and NOT the layer URL, into the "Add Exclude Identify Layer" GUI.  Case closed for WAB version of widget!!!!!!!!!!!!!!!!!!!!    Is there any chance that this method will work for the Flex widget? Many thanks, Barnaby Edit:  "Is there any chance that this method will work for the Flex widget?" -The answer is YES!!!!!!!!!!!!!!!!!!!!  I will add this answer to the Flex thread.  Good job, Robert! ... View more

Ha!  I was wondering the same thing myself, but kept my mouth shut...  ... View more