A Workforce for ArcGIS project is based on a predefined schema. This schema states that assignment types are populated into an associated coded value domain on the Assignments feature layer when created.
Sometimes assignment types need to be modified, perhaps because of a typo. On the Workforce front end, it is impossible to edit an assignment type. It can only be deleted (if the type is not being used by an assignment).
One can work around this by opening the Workforce project in ArcGIS Online, open the Assignment layer properties and directly edit the coded value domain.
I’ve recently implemented Workforce for ArcGIS on a big project. It’s great being able to automatically assign sites to fieldworkers, and update their to-do lists on the fly.
However, the lack of reference data for the fieldworkers was bothering me. In the Workforce mobile app, the map displays the default topographic basemap and the location and status of their assignments. We were sending fieldworkers into areas where they would have to be a bit more vigilant of their surroundings, as well as ensure that fieldworkers did not drive through areas which were deemed as “High risk” due to crime or environmental conditions.
I modified the worker basemap of the project to include a polygon layer containing these “High risk” areas, so workers could always be aware when they were near one of these areas. I also tried changing the basemap to OpenStreetMap, but the Workforce app did not like that at all. The app crashed multiple times before I figured out it only wanted to render the default map. The dispatcher map had no issue with changing the basemap.
I also managed to overlay our own reference road network over the basemap, so the fieldworkers were aware of which direction to face when capturing a survey. This was included so that required photos were captured consistently.
I’ve been quite busy over the last few months. I’ve fully switched over to ArcGIS Pro, and I’ve been spending most of my time developing a fieldwork workflow using Workforce, Survey123, Collector and ArcGIS Online. I also (finally) forced myself to dabble with the ArcGIS Python API, which has fallen neatly into place alongside my normal fiddling with ArcPy.
I thought I’d write this post quickly just to document something I’ve noticed when publishing a feature layer symbolised using unique values from a coded value domain to ArcGIS Online. Despite the descriptions displaying correctly in Pro, if one edits the symbols and then does not delete all the feature templates and recreate them, editing them in an online web map will result in the codes being shown on the edit dialog, and not the descriptions.
The way around this is to, well, delete the feature templates and recreate them before publishing. I’ve had this happen a few times, where everything looks great online, and then someone tries to edit it in Collector using the codes.
I’ve decided to post this here and not on my personal blog, even though this problem arose because of the awesome holiday I had planned. This has turned into a little personal project, so I tried to approach it from an end user point of view, instead of an enterprise GIS point of view. I scheduled several places to visit, and wanted to optimise the routes to these places based on my preferences, not time or traffic etc.
- I created a collection on here.com and diligently added each place, along with a note describing which date the place would be visited and in which order.
Naturally, I forgot that saving a custom route to a collection in Here maps is an absolute pain, and I can’t save it offline anyway.
- I then searched if Google Maps can do it. Moving on.
- Next, I tried Bing Maps. To my surprise, and similar to how here maps surprised me, Bing Maps allows you to add places, create polys and lines, set styles and export to KML or GPX! Colour me impressed.
With my Microsoft account signed in, I added two places and selected the route I wanted. I then launched Maps on my Windows Phone to see the fruit of my labours. Of course, nothing happened.
A quick Google search (sorry Bing, but it’s really never going to happen for me) confirmed that places would synchronise between Windows devices, which I can verify as places I added in the Windows 8 Maps app do appear on my phone. However, they do not synchronise with places added through the web interface, even though it’s the same Microsoft account. Sigh.
- This is how I ended up back in ArcMap, using the Find Route functionality, and converting the route graphic to a feature class so I can GIS it up nicely. However, generating each route and converting for each feature class did not appeal to me, even by writing a script to do it for me. Ultimately, it would still leave me with pretty jpegs, and I am not setting up an ArcGIS Online trial to load in my phone just for this.
The tasks are getting more advanced, and I’ve learned a lot about using ArcGIS Online. To be honest, I’m not even looking at the videos anymore, but that’s not to say that the videos are not good, it’s just that I don’t enjoy watching videos online, particularly lecture videos, unless I have searched for them for a specific reason. I prefer to read lecture slides and notes, where I can highlight, underline and reread as much as I like. It’s the same reason why I would routinely miss class while I was at university – I would rather self study the week’s lessons in my room than listen to a lecturer talk about it.
Overall, the MOOC does feel like it’s found a good pace, and I am looking forward to finishing it.
I should probably change the titles of these posts as I’m guessing ESRI will be offering more MOOCs in the future, so this could get confusing. Week 4 was much better content wise, and provided the opportunity to really use some nice tools available in ArcGIS Online. I like the fact that case studies from various disciplines are being used, to show everyone (especially the newbies) how GIS can be applied no matter what your field is.
I have found that sometimes when the analysis is complete, the newly created layer will disappear from the web map, which leads the user to believe that the analysis has failed because it appears that nothing has been created. When running the same operation again, a “layer name already exists” error proves that the layer was in fact created, but was not added to the map. This leads to the cumbersome process of having to add that layer again manually. I have also found that searching to add layers often returns no results when the whole layer name is used, but will return results for a partial match e.g. typing in “Intersect LA Crimes_cindywilliams” returned nothing but “Intersect LA Crimes_” brought up everyone’s layers and I had to scroll through it to get to mine.