Add the ability to use different layers in a map for viewing and submitting reports about crowdsource-reporter

[aparveen]

@CTLocalGovTeam could you please assess this for 9.4 release? Thanks

[sumitzarkar]

@aparveen @skrishn @chris-fox

As indicated in the shared webmap, we understand that there will be 2 different layers representing the same features one for submitting the report (with add capability) and the second to view the reported features (with query capability).

The reporter application is designed to show features on the map, a list of features, a button to submit reports, and my submission list in a new panel. For all this to act in unison all 4 items are related to a feature layer with both query and add capability.

In the current implementation application is failing/breaking when we are configuring such webmaps , to overcome this issue we are proposing the following approach:

• We will handle different cases in the application which are breaking when the layer is not having query capability
• As the layer which can add the features is not queryable we will show a message in the feature list panel indicating this behavior
• We have a different layer in the map that is queryable user need to click on the features in this layerto see the detials of the features.
• With this kind of configuration and the proposed approach we can see the following limitations /changes in app:
  • Map will show only features from the query capability layer only
  • On selecting an add capability layer, the feature list will not show any feature, and submit button will be displayed
    • We need to show a message to inform users about the list of features
  • Query capability layer will not be displayed in the layer list
  • My submissions will show no features for the logged-in user
  • To view the feature details, the user has to select the feature from the map only

Please let us know your thoughts on this.

[sumitzarkar]

@aparveen @skrishn @chris-fox

As discussed on the call we checked the feasibility to use the different layers for query and applyEdits, here are details regarding its impact:

• To enhance the reporter app to achieve this functionality will need high LOE and high risk.
• Due to the initial core design of the app to run based on only one feature layer the code is dependent on the selected single operational layer and it has many interlinked dependencies on this layer. All the different widgets created in the app are referring to the selected layer which is creating more complexity in changing the code.
• The code change may impact all the functionalities of the application
  Here are some features which may have major impacts:
  • Issue Wall (Feature list)
  • Issue Details (Feature details)
  • Highlighting the selected feature on map
  • Adding and showing Comments (Complexity with maintaing the related table)
  • Like
  • Attachments
  • My Issues(My Submmisions)
  • GeoLocation filtering

Please let us know your thoughts on how to proceed with this ticket