- List of discussion threads, blog posts, idea suggestions regarding Survey123-Collector integration:
I, like many others documented in the list above, would like to leverage the smart form functionality of Survey123 with the map-centric user interface of Collector. The xlsform question types geotrace (lines) and geoshape (polygons) have not yet been implemented in Survey123 (although presumably planned and a very popular idea) and continues to be limited to geopoint (point features), so until then...
From what I gather, one recommended approach to enable the desired functionality is to work with existing feature services.
QUESTION: But before I go too far down a rabbit hole can folks comment or provide guidance on my planned approach and answer some questions?
Field app project description:
My survey is for an Infrastructure Inventory of Protected Areas to capture point features such as signage and more complex infrastructure features such as pathways, bridges (lines) and parking lots (polygons). I currently have a Survey123 template and feature layer for points and would like to extend the complex form-centric functionality (nested repeats) to the collection of lines and polygons.
- In Survey123, start the survey by capturing the survey attributes e.g. “protected_area_id”, “observerID”, etc. (Parent table to child-feature layers)
- Ask user to identify the feature they want to collect by geometry type: “point”, “line” or “polygon” (‘feature collection’ repeat under ‘Survey”)
- If “point”, the user collects attributes and attachments (through a series of cascading selects), before being finally presented with a geopoint field to record the point location.
Not yet implemented (but desired):
- If “line” (or “polygon”) is selected, the user captures tabular attributes just as they do with a point feature, but upon being asked to record the spatial information:
- Launch Collector to open and digitize the line (or polygon) feature layer passing a survey GlobalID so that the feature collection can be associated with the survey by a join
- After digitizing the feature, return to the Survey123 form to collect more features.
- Is my planned approach reasonable? The usual approach is to launch Survey123 from Collector but I need to capture survey attributes that would be common to each feature and not require the user to enter the same data repeatedly.
- Is the desired functionality as outlined in #2 possible?
- If yes, can someone provide references or guidance as to next steps?
- Will the functionality of #2 work offline?
Any comments and guidance will be hugely appreciated! Thank you in advance.
***UPDATE*** I've implemented the collection of multiple vertices for lines and polygons, and will be submitting an ESRI support request regarding the Collector integration with Survey123. If you're interested in the follow up and would like me to report back what I've learned, please let me know.