doug-m / field-maps-testing

0 stars 0 forks source link

When collecting related records in app, honor location of parent rather than current location. #18

Open AbbyEJ opened 4 years ago

AbbyEJ commented 4 years ago

This is an issue I noticed in Collector as well, but I wanted to address it here since I am experiencing the same thing while testing. I work for an electric cooperative. We use Collector to keep track of equipment that cable companies attach to our poles. I configured this workflow in Collector by adding our Structure (pole) layer in the map, then adding a related point feature class to represent the cable companies attachments on the pole. Structure and Pole Attachments are related by GlobalID and GUID. In Collector, our guys add attachments by clicking on a pole, selecting the related feature class from the pop up, then click the blue "Add" button. Once they click that button, Collector (and now Field Maps) will try to put the point on their current location, rather than on the pole itself. Our guys have to navigate back to the pole and make sure the pole attachment point snaps to the pole. I understand field maps/collector is meant for gathering data while in the field, so ideally they would be under each pole during the inspection. However, that is not always the case. I figured since pole attachments are being added by clicking on the pole through a relationship, I would rather the point stay on top of the selected pole rather than moving to the current location.