I have a case that I have spent over a year developing a Sign Inventory application. There has been several stumbling blocks along the way with ESRI limitations of functionality from no Android version of Collector, subtypes groups not working in services, could not use Feature to Feature relationship class relationships, etc.
I have another problem that I believe is not going to be an isolated function to me. This problem is taking related records from the relationship class and moving them to another parent feature. My example:
I have a pole Feature class (used as the spatial location) for the pole structure. The Pole has a 1:N relationship with table "Sign" records related to the Pole. If the Pole is run over or damaged by a storm, etc. the pole is retired and a new pole is put it in the ground and has an "active" status. There can be up to six signs on one pole (most I have seen). If the signs are still in great shape, then they are physically removed from the old pole and bolted or riveted to the new pole. I can not find any possible way to for them to keep these signs and just move the relationship to a new parent feature. Retiring and adding them all back in is not a logical methodology. Those poles are not retired, they are still in use, but on a different pole. I have created the relationship based on GlobalIDs based on ESRI's strongly suggested method. This goes beyond Collector, but it definitely should reside in remote field collection apps as the field is where everything happens.
I have spent well over a year of my life developing this solution (much of it was data quality, hence trying to simplify the field collection methodology and may be the first to include EVERY sign style in the MUTCD specifications (except for Interstate-related signs as our City does not maintain anything on those highways.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.