Segmented Collection (Line Features)

07-01-2022 12:05 PM
Status: Open
Labels (2)
Regular Contributor

My team is largely focused on trails, not only the route of the trail, but the characteristics of it as it moves through the landscape.

For a visual aid, I'm stealing the example used in Esri's documentation for linear referencing, found here.


When we are documenting trails, many of which have not previously been documented, we run into instances where various characteristics of the trail change over its length. 

I would like to be able to collect these changes as one feature (on the user's end), to prevent having to stop, submit, begin a new feature, stop, submit, begin a new feature...

The process as I envision it is:

  1. Begin collection of a linear feature with one set of attributes.
  2. Each time an attribute changes, begin a new segment. Repeat as necessary
  3. Submit the feature
  4. Once the feature is submitted, it gets output into multiple little segments.

I know that Trimble's TerraSync has/had this functionality, but I have yet to see it replicated in any other software.

Segmentation during data collection would not only make collection more efficient, but also ensure better data (each new segment is guaranteed to pick up where the last segment ended).


Check out QuickCapture! That's almost exactly like one of the examples they demo'd for it!

You'd have to configure the different buttons, but when using QuickCapture to collect lines, it will keep the endpoints snapped together, so you could, for instance, have different buttons for trail surface types and access presets. You can make a QuickCapture project as simple or complex as you need to.




I'll give this a closer look again, but at first glance that doesn't sound like it would meet our needs.

Namely, it sounds like I would need a button for each possible combination of attributes, which would get messy fast.

For example, we look at surface, incline, whether or not it has curbing and on which sides, our confidence in how "real" it is, which land division it's in (admittedly, this could be done out of the field), etc.

If each one of those five parameters has three options, that's 243 buttons to choose from. Being able to just choose changes as they happen is far easier to conceptualize and requires less planning to prepare for every possible outcome. 

It's a shame; it looks like QC has simultaneous collection, which is is another feature I'd like to see in FieldMaps. 

I gave QC a brief shot before posting this, and it appears my button assumption is correct. I also had trouble getting the vertices to join together, but I assume that's user-error.