Nested collection

[EricCollinsOVV]

It would help to be able to collect nested features, particularly points while collecting a line or polygon. For example, while collecting a pipeline linear feature, one should be able to jump out and collect a valve point location while collecting the pipeline linearly and then continue collecting the pipeline as a line.

Bonus - add these points in as a related table item or connect them with a globalid to relate the valve to the pipeline.

[EricCollinsOVV]

How is Survey123, a form based collection tool, a good tool for doing map-centric work? 

[JeffShaner]

Thanks for the post @EricCollinsOVV, and for the pipeline example as well. We are looking at how we can satisfy this requirement within the existing workflow for collect. 

Though not a solution, have you considered submitting the pipeline feature, adding the valve and then tapping on the pipeline feature again to extend it? It is a lot of taps but may be a short term solution - until we address the requirement. This won't work for polygon features unfortunately.

Also, if you do establish a feature-to-feature relationship class where the pipeline feature is the origin and the valves are the destination class with a 1:M using GlobalID -> GUID, this should enforce the relationship and work. You can just treat the valves like you would a related table.

We are also considering a rapid collection tool as well - where you you can tap the tool and it would automatically place the location with default attributes. Is this something that you all would be interested in?

@AdamStewart - would be interested in hearing your workflow as well. Sounds like you've had to link between Collector and Survey123. We'd like to solve this within 1, map-centric app, if we can. That way you don't have to manage and deploy 2 apps.

[EricCollinsOVV]

I didn't think about extending the pipeline by tapping it in edit - would that work with streaming? 

We try to set collector projects up with as many defaults defined as possible in advance for the task at hand so the rapid collection tool might not be a lot of value unless you were to offer quick collects for multiple default choices perhaps when the field collection might have 3 or 4 standard collection types.

Thanks for the advice on the relationship classes! Sounds like one would have to define/select the relevant pipeline while collecting the valve in order to establish the specific point-line relationship in the project.

[JeffShaner]

>I didn't think about extending the pipeline by tapping it in edit - would that work with streaming?

Tapping edit on a feature puts you right back into the collect mode again so you can start streaming if you like. 

> ...quick collects for multiple default choices perhaps when the field collection might have 3 or 4 standard collection types.

That's the most probable path forward - configure a set of feature templates that could be used for rapid collection - it would just apply default values for you.

> Sounds like one would have to define/select the relevant pipeline while collecting the valve in order to establish the specific point-line relationship in the project.
Yes, exactly. Just like you work with relationship classes today in Collector (or Field Maps). If you stream capture of the pipeline feature, then tap Submit, the feature is selected and the pop-up is shown. From the pop-up, you can access the related table and tap add to add a new one. When you do so, it will require a point geometry for the valve. I think it would be worth exploring to see if the workflow meets your needs until we can properly address the nested features requirement

[BrandonWotachek]

I agree with Eric, ArcGIS Field Maps needs to have nested feature collection.  We have a routine sampling workflow where we need to stream a line feature and while streaming a line, need to collect multiple point locations at certain times during our recording of a line feature and do not want users to have to stop and start streaming a line.  Currently we will have to use another app to do perform a screen grab of our X,Y to get those coordinates.  The ability to drop pins while streaming a line feature would also be nice, as would the option to have a coordinate readout somewhere in the map view that a user can turn on our off, such as in ArcMap.  I hope that ESRI puts more functionality into Field Maps soon.

[AlfredBaldenweck]

Bumping this thread.

This is badly needed functionality. 

Being able to collect a point for an artifact while walking a long site perimeter,  or, as is more often the case, walking a mile straight of trail, would save a bunch of time and be far easier than having to submit your current feature, take the new feature, and open the first one to continue editing it, especially if in areas of poor connection or if submitting attachments. (Even if working offline, this is important functionality.)

[MickeyGuziak]

Bumping this thread again - has there been any movement on developing this functionality?

[tiztrain]

this is a requirement brought up from our field teams when doing in ecological surveys

[RichardHowe]

To add to @tiztrain I have also had a similar request from our ecologists. Scenario was bird observation polygons containing multiple singular bird species points

[ThijsBriggeman_Tensing]

This would be an excellent idea and something customers would really like to see in my experience. 

Ideally I would like to see an option to register a point in fc 'A' when registering a line in fc 'B', at the location of vertices of the line in 'B'