POST
|
Esri provides a mechanism to submit updates to basemaps here: http://communitymaps.arcgis.com/. There are several tools depending on what you want to provide and the basemap that you want to see updated.
... View more
06-19-2019
12:20 PM
|
1
|
0
|
63
|
BLOG
|
I like this approach. What a great way to take advantage of all this data with such a small infrastructure investment. You could also change some of the formatting of the text in the alerts before pushing it into the feature service. For example changing "WEATHERHAZARD" to just "Hazard". I did this with GeoEvent Server but this this would be pretty simple to do in the python script. Here is an example we put together with GeoEvent Server for Indiana: Indiana Waze Operations Dashboard. Great thanks for sharing this. Great job!
... View more
10-31-2018
08:34 AM
|
3
|
0
|
1349
|
POST
|
I can answer that one. The assignments in Workforce are managed through a feature service that gets automatically created with the Workforce project. You can add a work assignments by simply adding a feature to that feature service. To do that you call the applyEdits operation on the feature service. Below is a screen shot of how we setup Integromat to update the feature service: And below is the json that we put into the adds key: [{"geometry":{"x":{{1.feature.geometry.x}},"y":{{1.feature.geometry.y}},"spatialReference":{"wkid":{{1.feature.geometry.spatialReference.wkid}}}},"attributes":{"status":0,"description":"{{1.feature.attributes.damageFeature}} {{1.feature.attributes.assetID}} has the condition of {{1.feature.attributes.bridgeStatus}}. {{1.feature.attributes.featureComments}} Bridge located on Route {{1.feature.attributes.routeID}} at measure {{1.feature.attributes.begin_Log}}. Inspected by {{1.feature.attributes.fieldInspector}} {{1.feature.attributes.fieldPhone}}.","notes":"","priority":null,"assignmentType":1,"workOrderId":null,"dueDate":null,"workerId":null,"location":"{{1.feature.attributes.assetID}} @ {{1.feature.attributes.routeID}} and {{1.feature.attributes.begin_Log}}","declinedComment":null,"assignedDate":null,"assignmentRead":null,"inProgressDate":null,"completedDate":null,"declinedDate":null,"pausedDate":null,"dispatcherId":1}}]
... View more
10-11-2018
02:30 PM
|
0
|
0
|
147
|
DOC
|
In working with Ohio DOT we have identified the cause of this issue and a viable resolution. The Issue: Ohio DOT uses shared iPads for their data collection. Their workflow is for field workers to start by taking an iPad from a shared docking station. They then use that iPad to take a map offline in Collector for ArcGIS. After data is collected in the field they sync their edits and remove the offline map. The iPad is then placed back in the shared docking station. The next day another field worker starts the process from the beginning. The issue arises when the second field worker takes the exact same map with the exact same extent offline for the second day. In this situation iOS returns a file reference to the geodatabase associated with the replica from the previous day instead of the geodatabase associated with the newly downloaded offline map. Since the replica from the previous day has already been removed from the server; when the user attempts to synchronize they get the error “Replica with this GUID does not exist on the server”. After this error the edits on the device cannot be synchronized with the server. The Resolution: Using the current version of Collector for ArcGIS there are two workarounds for this issue. Close (swipe up) the Collector app before downloading the new offline map. Set the default extent for the webmap of the offline map so something that would have to be changed prior to download. Imagine a very small extent that the user would zoom out to the appropriate location. Ohio DOT chose to use workaround #1 because it was a minimal change to their existing workflow. They also instituted a policy to have each field worker sync once prior to going out in the field. This verifies that they will be able to synchronize their edits at the end of the day. The new version of Collector for ArcGIS (Aurora) coming out later in 2018 will not have this issue. Therefore, no additional workflow will be needed after moving to this new version of Collector for ArcGIS.
... View more
09-11-2018
12:37 PM
|
2
|
0
|
246
|
POST
|
Sam, With regard to this: " We use no fill in ArcMap, but if you set a point to no fill color in Pro it won't let you select the point anymore which has caused us problems. " One trick to create a label for a feature in pro without seeing the feature is to set it's transparency to 99%. This will make the feature invisible but the label will show and you will be able to select or identify the point to get at it's attributes. Hope this helps.
... View more
05-25-2018
03:38 AM
|
2
|
0
|
79
|
BLOG
|
Yep you got it. You will need to turn your events into features and use those as the parent feature in the relationship. If your events change than you will need to republish or update the data with the new features.
... View more
04-09-2018
11:37 AM
|
0
|
0
|
389
|
BLOG
|
Joe, I think you can do this workflow with related features. Simply create a related feature to your event. Then the field person would be able to click the linear event and add whatever data they want at that location. I don’t think you need linear referencing to support this.
... View more
04-09-2018
07:15 AM
|
0
|
0
|
389
|
BLOG
|
Joe, unfortunately, no. The ArcGIS Online team is evaluating this but has not made any progress to date. But we have done a lot of work with back end process that tie Survey 123 and Collector data collection to an LRS network. Could you describe in more detail what you are trying to accomplish?
... View more
04-06-2018
09:38 AM
|
0
|
0
|
389
|
Online Status |
Offline
|
Date Last Visited |
12-15-2020
04:27 PM
|