Closed jdokemaps closed 2 years ago
@afackler let's check all the feature layers to make sure squad id aliases match (don't worry about field names for now, we don't want to introduce any breaking changes).
Should we use Squad ID or Team Squad? Looks like Team Squad is used in the tracklog and segments, then Squad ID in the waypoints.
Let's go with Squad ID since that is more intuitive.
On Mon, Dec 6, 2021 at 7:35 AM Adam Fackler @.***> wrote:
Should we use Squad ID or Team Squad? Looks like Team Squad is used in the tracklog and segments, then Squad ID in the waypoints.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pjdohertygis/WideAreaSearchTemplates/issues/162#issuecomment-986889898, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAPJU3I7RCR7H7YZROSBP3UPTJ4RANCNFSM5EMU7LNQ .
--
Paul J. Doherty, PhD
How many digits will the squad ID field allow?
Right now it looks like the input mask is limited to two digits. @grover556 do you think this should be bumped up three?
I'd like to see three digits if we can
@afackler Can you please update the input mask for Survey123 and QuickCapture to allow for 3 digit squad id?
Implemented in Sandbox and Deployment, including 3 Digits for Squad Number (1-999).
From Peter (Lee NJ-TF1): I was wondering, with the QC tracks vs waypoints, the "team squad" vs the waypoint "squad id" vs "creator" fields, is the desire to not have these congruent? I realize they write to different feature layers, and my idea was to just have the quickcapture tracks "team squad" for the waypoint "squad id", so it's the same per the creator/squad. That seems to make sense to me.
We should align the field names and descriptions across feature layers.