POST
|
Hi Francis -- Yes, that feature is available at Enterprise 10.6 and also starting with the WAB Dev Edition version 2.5. Cheers, jess
... View more
06-01-2018
08:36 AM
|
0
|
0
|
1332
|
POST
|
Hi Francis -- Thanks for your question! First -- yes, by design when a Solution is deployed from the Solutions Deployment Tool in ArcGIS Pro, the layers will be empty. This is primarily for users who do not already have their data published and would like to use the schemas provided with the solution. So, you can either load your data into the services that are published with the deployment, or switch out the layers in the web map for your already published data. With the switch out option, you will likely have to reconfigure any widgets in Web AppBuilder so that everything is hooked up correctly. In Situation Awareness, I think the setting you are looking for is: Analysis > General Settings > Disable layer visibility management. To support our Portal for ArcGIS users across versions, this setting is not enabled in the deployed configuration because it's more modern Enabling this setting will make it so that the layers being analyzed are visible even if the tab isn't active. hope this helps! jess
... View more
05-30-2018
01:58 PM
|
0
|
2
|
1332
|
POST
|
Hi Scott, Your assessment is correct. The layer comes in without any data and needs to be populated with the USNG (or other if preferred) grid data. One way to populate the layer is with an existing dataset. You can find a collection of USNG 1000m grids for all the UTM Zones in online here (shout out to Jeff Baranyi for the assist). Once downloaded, open the layer package and select the area of interest that covers your jurisdiction. I recommend exporting this grid subset to a new dataset you can use whenever you may want to create a new USNG grid for a response effort. Using ArcGIS Pro, you can append the grid subset into your published USNG layer. Hope this helps! jess
... View more
04-25-2018
05:17 PM
|
2
|
0
|
681
|
POST
|
HI Mark -- Thanks for your question. We are planning to fix this issue in the April 2018 release of Online. jess
... View more
02-13-2018
03:41 PM
|
1
|
1
|
1033
|
POST
|
This could be related to the way in which the line features are identified. There are essentially two different workflows within the widget --- one that does a clip and one that does a select by location. If the Select by location workflow is followed (with the released version of the widget this would happen with Point or Line AOIs that do not have a buffer), then the length and area are not reported since the intention is to report the amount (length, area, count) or the features within the defined area.
... View more
01-02-2018
11:36 AM
|
0
|
0
|
637
|
POST
|
Hi cob -- The measurement units being tied together is tied to the original requirements for this project. This widget is an evolution of an on-premise JavaScript application that was used to deliver the capability pre-2017. I'll make note of your request to separate the units so it can be evaluated with other customer requests as we plan for future releases. The dev edition update is planned for mid-month. jess
... View more
01-02-2018
11:32 AM
|
1
|
0
|
654
|
POST
|
Hi Mark -- This is a great question that we received several times after the Screening widget was initially released, so with the ArcGIS Online update last week, we expanded the list of unit options available. Now, the following options are available: Feet / Square Feet Miles / Acres Meters / Square Meters Kilometers / Square Kilometers Kilometers / Hectares Here's what the configuration panel looks like where the default units are set: And here's where the user can change the analysis units at run time if needed: This update will be available in the next release of Web AppBuilder for ArcGIS Developer Edition. With the current version, it is possible to set the default units to Metric (km / sq km) in the configuration panel. Hope this helps, jess
... View more
12-11-2017
09:35 AM
|
1
|
2
|
654
|
POST
|
Hi Cob -- I'll see if I can find a developer to weigh on implementing Feature Actions, it's not my forte. Unless you've removed the logic that does the clip analysis when clicking the 'Report' button - then the layers that have been configured for reporting are being clipped by the area of interest -- which in your case is based on a selection -- and if only the selected layer is configured for analysis, then yes - I would expect you are getting the entire are of the features reported in the panel. Jess
... View more
11-26-2017
01:42 PM
|
0
|
0
|
637
|
POST
|
Hi Charles, I'm wondering if there's possibly an easier way to address the workflow need you have -- as i understand it, you want users to be able to select features from the map and then get a list of the features that includes the feature area or length? I've got two ideas for you: (1) If the area and length of the features is calculated in an attribute on the feature layer, you could do this with the Select widget... After making a feature selection, click the ellipses and available feature actions will be presented. One of them is View in Attribute Table. This would present a tabular view of the data, including the pre-calculated areas. (2) if it's not possible to modify the data to include the area and shape values, then I'd recommend extending the Select widget by adding a feature action that could show up in the list to perform the analysis required. The reason why this may be better given what I understand of your workflow is that the Screening widget is designed to actually clip the features based on the AOI defined (in your case a selection set) -- and that is the area or length that is reported; it may not be the full length or area of the intersecting features.
... View more
11-17-2017
05:08 PM
|
1
|
2
|
637
|
POST
|
Hi Eric -- Thank you very much for the further detail regarding your use case -- you're right, as it stands right now, within the Situation Awareness widget, there isn't a way to simply select a collection of features as input. We can put an enhancement request into the system to support this workflow. I was able to work out an approach that would enable you to accomplish this within WAB using the Select and Analysis (Dissolve Boundaries) widgets, though admittedly it's not an intuitive workflow. jess
... View more
09-18-2017
12:31 PM
|
0
|
4
|
1332
|
POST
|
Hi Eric -- As I understand the challenge, you'd like to summarize the total count of farms in a particular area and that area is defined based on pre-existing locations? I have a couple ideas for you -- With the Situation Awareness widget, you can add existing locations to the current area being analyzed through the feature's pop up -- the Add/Remove Location feature action. In the following screen grab, I can add a second flood polygon to the first through a feature action on the pop up: Alternatively, depending on what exactly you're summarizing, you could explore looking at the Screening widget, In this case, the widget is reporting feature counts, area of overlap for polygons, and length of overlap for lines. With this widget, users could simply select the areas they are interested in with a selection workflow, and then see the report of which farms fall in that area on the report results panel. There are similar print and CSV download functions in that widget as well. Looking forward to hearing about what you come up with, jess
... View more
09-08-2017
05:38 PM
|
1
|
0
|
1332
|
BLOG
|
After a disaster event, one of the longest running operations is removal and disposal of debris. Between damaged and destroyed structures and built up vegetation and dirt, the work to clean up an area affected turns into a community effort. Citizens affected will have observations that may help recovery teams target efforts and the recovery teams need to track the location, status, and disposition of debris throughout the process. We previously posted about a community engagement solution you can use to solicit input from affected citizens about remaining debris, damage, and other information happening in their neighborhood. You can find that here: How To: Engage citizens to report community observations To support recovery team efforts, ArcGIS for Emergency Management includes a solution for Debris Reporting and monitoring. This solution includes: an information model for identifying the location of debris in the field using Collector for ArcGIS and monitoring it as it moves through the disposal process an Operations Dashboard configuration that enables response and recovery stakeholders to monitor the total volume of debris being processed and the overall progress of the clean up Debris Reports Monitoring View an example operational view for monitoring debris identification and removal operations. Get Started To set up the Debris Reporting solution, you'll need three ingredients: a Hosted Feature Layer based on the Debris Reports template service (or ArcGIS Server Feature Service), a Web Map containing your Debris Reports layer, and an Operations Dashboard view configured to monitor debris removal Sample data, an ArcMap document you can use to publish the Debris Reports layer to your ArcGIS Server, an step by step instructions for configuring these elements for your organization have been documented on the ArcGIS for Emergency Management Debris Reporting solution site. Quick Start Option The Debris Reporting solution (and many more) can be quickly deployed to your ArcGIS Online Organization or Portal for ArcGIS using the ArcGIS Solutions Deployment Tool. Here is a short, two minute video on using the Deployment Tool to create the hosted feature layer, a web map for use in Collector for ArcGIS, and the Operations Dashboard view with nearly one click. Bonus Content We have shared a service template for Disposal Locations and Emergency Facilities. You can use these templates to create new hosted feature layers in your organization, then populate the layers with the locations to be used for staging, transfer, and disposal of debris. Attached to this post is a template Survey 123 for ArcGIS form which can be used in your field operations. You may receive validation warnings with the choices in this form, you can safely click OK on these. Update the submission_url setting to point this form to your existing Debris Reports hosted feature layer.
... View more
09-01-2017
09:10 PM
|
2
|
0
|
1514
|
POST
|
Hi Todd -- That's correct. If you add multiple locations into your incident, the widget does not differentiate the analysis results between the incidents. Depending on what your needs are, you could run the widget multiple times and then download lists or reports from the widget summarizing the information for each location.
... View more
08-30-2017
10:29 AM
|
1
|
0
|
537
|
POST
|
Hi Michael -- I wanted to check in with you to see if you were still having issues with the workflow you described with the June release of ArcGIS Online. We addressed an issue with filtering and the Info Summary widget at the June release. Please let us know! jess
... View more
07-17-2017
05:13 PM
|
0
|
2
|
404
|
POST
|
Hi Fernando -- Were you able to find a resolution to your question? Info Summary could be a good option for you -- you will need either a rendering pattern or field to do the grouping within the widget. Let me know! jess
... View more
07-17-2017
04:53 PM
|
0
|
0
|
165
|
Title | Kudos | Posted |
---|---|---|
1 | 11-17-2017 05:08 PM | |
1 | 12-11-2017 09:35 AM | |
1 | 01-02-2018 11:32 AM | |
1 | 07-17-2017 04:46 PM | |
1 | 08-30-2017 10:29 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:22 AM
|