Latest Contributions by DamienRobinson

‎06-21-2015

Hi Braulio, In one of my previous responses on this thread I detailed that I could easily have released wms for an arcgis server service and claimed to have support for wms. You may have noticed that I already had the code included in the widget for an esri wmsserver service, but have commented it out. This was because I was not happy with the workflow for non-esri WMS services and I intended not to release either wms functionality until I was able to resolve this. I won't be officially adding any WMS functionality to the widget until I can support non-ESRI wms. Thanks, Damien

‎06-19-2015

The WMS is something i've been looking at and haven't quite got a workflow in javascript that I like. I could easily put the code in to allow an ESRI WMSServer service, and claim the widget to be WMS compatible, but i'm thinking of other platforms. At a higher design level i'm thinking of INSPIRE services compatibility. Thanks, Damien

‎06-19-2015

Hi Daniel, If you have tried it in a new web app builder application and it hasn't worked, I would try adding it to a new build of web app builder developer edition, i.e. extracting the web app builder source code to a new folder, paste in the 1.1.1 version of the widget to the widgets folder and invoke web app builder as normal. This should resolve any "caching" type issues (using the term "caching" loosely of course). Thanks, Damien

‎06-19-2015

Hi Julian, The layers are not meant to be saved. This widget permits you to add a service from a REST directory (secured and unsecured), at run time and in memory. Saving back to the webmap id that the web app builder utilises, isn't something I have considered. Often i find that the only reason i'm adding a webmap in web app builder is to provide basemapping (and because I have to!), hence I wouldn't want to be corrupting my master basemap webmap by saving additional layers to it. From an administrator perspective (of a public site), trying to manage the creation and addition of layers to new and existing webmaps would quickly become a nightmare, never mind considering permissions etc.. It would vastly over complicate the scope of this widget, which is designed to be simple and relatively uncomplicated. In my opinion you should be setting up your webmap with whatever layers you need in the first instance through ArcGIS Online, like you would for any other javascript application/template that requires a webmap. I hope this explains the scope of the widget with greater clarity than i've stated previously. My future plans would be to get it working with non-ESRI OGC services, to allow for open source server service integration within scope. Thanks, Damien

‎06-17-2015

Hi Humza, Currently it doesn't support feature layers. It only supports the following Javascript classes currently: ArcGISDynamicMapServiceLayer, ArcGISTiledMapServiceLayer and ArcGISImageServiceLayer. I will consider adding the FeatureLayer class to the next update. Thanks, Damien

‎06-16-2015

Thanks Stan!

‎06-16-2015

Hi Braulio, It currently doesn't support WMS. It only supports ArcGIS Server Map (Dynamic and Tiled) and Image services. I hope to add the WMS functionality at some stage in the future. Thanks, Damien

‎06-15-2015

Hi Stan, I had tinkered with too many files in the stemapp, so something went awry somewhere. I just downloaded a fresh web app builder install and the issue is gone. I've updated the code to include your settings code and referenced your contributions. Thanks for contributing! It would probably be as well to host it all in the same location on this thread, so would appreciate if the github could be taken down. Thanks, Damien

‎06-15-2015

Hi Stan, Thanks for this, I've got it working (sort of)! So to clarify, this functionality doesn't require any manual config? Just drop the unzipped AddService folder into stemapp widgets folder and it's automatically detected? I've ran it through stemapp and the widget appears twice in the header controller => add widget setting. I assumed it was because I hadn't removed the AddService label and uri from the master config.json, but even after removing it two of the same widget appear side by side. Any suggestions as to the cause?

‎06-14-2015

Precisely Robert! I find it easier and quicker to provide a customer with a URL that they can add themselves to a pre-built application, rather than having to configure a completely new application for their purposes. We used the flex equivalent for a long time, so it was natural to replicate this functionality in Javascript.

‎06-14-2015

Hi Daniel, I'll look into the "layer1" issue. My idea was to utilise the layer list widget and its listeners, rather than re-inventing the wheel for map service control. I might look at extending the layer list widget to permit the removal of a service, rather than building it into my own. You can toggle visibility, re-order and change transparency etc. using the layer list widget, the only thing it seems to be missing is the ability to remove a service. I hope to add WMS and potentially WFS handling to the widget when i get a chance.

‎06-12-2015

Thanks Rebecca.

‎06-12-2015

UPDATE - 17th November 2015 Add Service Widget - 1.2 Widget updated with WMS functionality. Apologies for how long this took, but it was quite a complex task. I finally found a workflow I was happy with, that would also support non-ESRI WMS. This widget cannot handle secured WMS. The widget requires some configuration in the config.json file. It is an array of the GIS servers that you will be adding web services from. The code handles this and pushes them as corsEnabledServers. If the server isn't CORS enabled, I believe it won't permit adding of the service in your application. A change was added to the image service workflow, whereby if the image service is cached it will bring it in as a tiled map service rather than an image service, as the image service capability limits the amount of tiles viewable (defined in the service). ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- UPDATE - 19th June 2015 Add Service Widget - 1.1.3 Fixed image service bug. Added additional code for error handling. Add Service Widget - 1.1.2 Fixed image service bug. Now checks for the allowRasterFunction in JSON object to infer image service type, and attributes a new variable called imageServiceBool depending on outcome. If the allowRasterFunction object exists in the JSON then imageServiceBool = true, else imageServiceBool = false. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- UPDATE - 16th June 2015 Add Service Widget - 1.1.1 Fixed Layer List bug (where layer list showed map services as layer1, layer2 etc.). Layer list widget will now read in the json.mapName object for dynamic and tiled map services. Add Service Widget - 1.1 Stan McShinsky has added code to the settings folder to enable automatic integration with web app builder. Just unzip the widget and drop it into your web app builder stemapp "Widgets" folder. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This widget will add an ArcGIS Server service at run time to web app builder. It currently accepts Dynamic and Tiled Map Services, and Image Services. The widget has been designed to handle secured services. Added services can be controlled in the layer list widget (thanks to its listeners!). Instructions To add to your Web App Builder application, extract the zipped AddService folder and paste it into your application's "widgets" folder.

‎01-16-2015

Thanks Josh! This is great!

‎01-15-2015

Hi, I'm working on a custom javascript based viewer. This viewer will allow a user to perform a query, then it zooms to the relevant extent. This aspect is working great. However i'd like to add a jquery spinner when the query is performed and stop it once the extent has been zoomed to. For whatever reason, I can't get this spinner to work within the script tags of the arcgis javascript viewer. I have tried various methods using javascript and other libraries. The basic methodology i'm pursuing is to create two functions, one to stop the spinner, the other to hide the spinner. I downloaded the javascript and css files from the following github: jQuery Spin‌ . I have referenced these in the head of the html page. I have placed the following functions in the map viewer script tags. function stopSpinner(){ $('.spin').spin('hide'); }; function startSpinner(){ $('.spin').spin('show'); }; The startSpinner() function will be called on the same button click as the query operation, the stopSpinner() would be called immediately after a getExtent call. Are there any issues with using jquery and the arcgis javascript api ? Any advice would be greatly appreciated. Thanks, Damien

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by DamienRobinson

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

Add Service Widget 1.2

Re: Javascript Spinner with ArcGIS Javascript API

Javascript Spinner with ArcGIS Javascript API

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2

OCHA icons in Draw tools

Re: Add Service Widget 1.2

Re: Add Service Widget 1.2