Latest Contributions by AdamDrackley

If you want to give it a try, I'd be interested to know how it operates 'out of the box' in your particular case with a pre-existing configuration file.  In the 1.6 version of the application, the config file kept track of which layers to 'hide' (IE; which were left unchecked in your Dynamic Layer Settings Window).  The 1.7 version of the app takes the approach of remembering which layers to show by default instead.  I found this made the process much easier to keep track of from a code perspective. If you have an especially complex configuration file, let me know.  There may be ways to rethink this approach prior to the release. ... View more

Just a quick note that I have a 1.7 release branched in github with the following enhancements.  We're still doing some testing on our end, but if you feel adventurous and would find some of the improvements beneficial in your workflows, feel free to explore the candidate. cmndrbensisko/LocalLayer at LocalLayerv1.2.1 · GitHub Enhancements: Experimental geoJSON Support (Currently only supports point geometries which contain a single standard schema, as well as Non-standard JSON Arrays which include Lat/Long keys) WebMapTile support, including the ability to add these as either Tile Layers or Basemaps (If you haven't played with Stamen's watercolour map yet, it's gorgeous,  maps.stamen.com) Sublayer Visibility in Dynamic MapServices re-introduced, and should(!) now work properly.  Grouplayer visibility toggling allowed.  (Re-configuration of your layer will likely be required) The ability to set MinScale and MaxScale for added layers. The highest kudos to Robert for pushing this project forward. I'm actually just beginning to use this widget for a few projects professionally, so this should hopefully result in more time dedicated to the widget's ongoing improvement and enhancement. ... View more

Works great, thanks for the simple solution Lalaine. ... View more

Hey Tope, thanks for your code snippet.  I'm a developer working with Alison on implementing the WMX Javascript app, and I used your code as a base to perform the Job Update, but I'm feeling that there might be a simpler way. Around line 1770 of WorkflowManager.js, in the createJob success callback, I have to perform a self.wmJobTask.queryJobsAdHoc function to grab the new Job's details before I can make the updateJob call, because otherwise I don't have access to the job's name as you do in your snippet. Does this seem like the right area to implement your code above, or is there a better location to be making the updateJob call? ... View more

Version 1.5 is available, containing a Layer Visibility fix for Dynamic Services, and the ability to display labels on Feature Layers if desired. ... View more

Just a thought, but maybe this is something you can keep on your geonet blog as a "Live" document, updating/replacing it as it grows.  That way, we can just link to your blog post in our Readme.md file, and take the best bits of your experience as a guinea pig new adopter for the widget's 'official' documentation.  How would this sound? ... View more

Hey Barnaby, I've added better control over layer order as an enhancement to the widget: I agree that it's very important, and that Feature Layers shouldn't necessarily float to the top if we can prevent it. I'm a little curious about the issue you're describing here, regarding your use of a Tiled Service as a Feature Layer: "Edit 3:  Note that a tiled service (a geodatabase of nationwide vectors in this case) added as a Feature layer using the widget draws very slowly.  The same tiled service draws instantly when it is part of an AGOL Web Map added to a WAB Dev app" I haven't tested myself, but it seems like in this particular situation, the slowness you're experiencing could be because a Feature Layer will by default query all the visible features from a data source and send them to the client to render, in this case the Web App.  Instead of quickly sending the pre-rendered tiles your way, which is what I imagine you're expecting to see, it's slowly rendering all the features in the browser. If my guess is on the mark, I'd imagine this is the cause of the slowness you're seeing.  I'm curious then about the AGOL Web Map you're mentioning; Would you be able to pass along a public AGOL Web Map containing this Tiled Feature Layer?  My guess is that the AGOL Web Map has the Tiled Layer added in such a way that the tiles are being correctly streamed, and that's why you're seeing the tiles rapidly drawing, instead of the slow process of client-side vector rendering. Does this sound like it could be on the right track?  Do you have any public URLs you can share so that I can try to troubleshoot your issue on my end? ... View more

Got it.  It doesn't look like there's any way to keep Github from appending the "-master" branch name to the zipped repo, but hopefully the rename will make things easier for users. ... View more

The login prompt appearing each time is likely a security feature built into the WAB.  I don't believe the proxy is actually used at all in the authentication process, unless your proxy has been specifically programmed to take care of this, but I'll take a closer look this evening. If it's desired functionality, we might be able to get the Widget to store an authentication token in a cookie, and not prompt the user again until the cookie expires, but we might need to make this something you clearly opt-into in the setup: Some users might not want authentication tokens stored, and might enjoy the added security that comes with needing to authenticate each time the app is viewed. Alternately this kind of thing might be able to be handled entirely in the Proxy, though it would require storing user credentials directly in your Proxy Config, and potentially any users could spoof their way into seeing your secured services by going through an auto-authentication proxy.  It depends entirely on your specific workflow which you'd be more comfortable with. ... View more

Sorry to leave you two hanging on this.  I hadn't tested the widget against secured services until now, but you guys seem to be running into another face of the same bug that necessitates the edit to your LayerInfoForMapService.js file. On line 406 of jimu.js\LayerInfos\LayerInfoForMapService.js file, find the line that says:       var url = this.originOperLayer.url + '/layers'; And change it to:       var url = this.originOperLayer.layerObject.url + '/layers'; And let us know how far this gets you.  Hope this helps. ... View more

Hey Rebecca, a quick question regarding your proxy issue: The proxy address should point to a .ashx proxy page, not a file ending in .config.  Do you have a file like this hosted by your local webserver, and reachable at something like http://<yourDomain>/proxy/proxy.ashx? ... View more

I have a feeling this was due to a change I made.  I'm going to copy/paste this into our issue tracker and assign it to myself; Your service will be very helpful in finding the best way to implement this.  Thanks Barnaby. ... View more

Hey Rebecca, great idea regarding the Readme.md file, we'd love to better document some of the stickier parts of the widget.  I'll point you towards the project Issue Tracker as a great starting point; Robert and I will be referring to this when it comes to organizing and prioritizing improvements to the tool and its documentation. https://github.com/cmndrbensisko/LocalLayerWidget/issues ... View more

Just an APB to anyone interested; As mentioned in the original post, the widget has been merged with Robert's awesome GUI work, and LocalLayerWidget v.1.2 is now live!  Head over to Github to grab a copy and check it out! https://github.com/cmndrbensisko/LocalLayerWidget ... View more

Hey Barnaby, I thought I should weigh in here.  Robert's widget is a very big upgrade from the one I initially posted, but "officially" (at least in terms of how we're managing the code currently), it's a beta version of the next version of the same widget. I'm currently in the process of vetting it to make sure everything works well before upgrading the core code repository to include Robert's work, at which point both codebases will be unified.  When we get to that step, which should hopefully be soon, we'll get to work on updating the documentation to reflect the new capabilities of the enhanced application. You're running into some interesting edge cases with your environment, and as you keep documenting them, we can try to tackle them in future enhancements.  If you have a Github account, you should be able to add Issues to the repository's bug tracker at https://github.com/cmndrbensisko/LocalLayerWidget/issues .  This thread is getting a big cramped, so we may try to encourage bugs/issue reporting and enhancement requests to Github to keep everything centralized.  I'll be sure to edit the original post to reflect this. Regarding the issues you raised in your post: From what I've tested using the new version of the widget, I am able to turn sublayers on and off in the LayerList widget for Dynamic MapServices, even with MapServices with all layers turned off by default.  Would you be able to create a bug report for this in the repository, potentially with the /MapServer?f=json rundown of your service's setup and capabilities? Regarding your State issue, I am able to duplicate something similar on my end with Aliased fields.  We can try to fix this before the official rollout of Robert's upgrade. The Feature Layer issue seems to be driven by ArcGIS Online; We can start to investigate how we might be able to deliver finer-grained control of layer order in later versions. ... View more