Hi folks.
I am a GIS Analyst working for an AEC consulting company, and I'm currently working with our surveying department to develop a web experience for managing existing and inputting new survey data into a central database. The department manager currently uses Google Earth for his most common workflow, which involves creating a new folder, delineating a survey area, defining some point/line/polygon areas within, then having the functionality to export to KMZ to share with the client and/or subcontractors.
I currently have it set up so that the first step is to draw a broad polygon to encompass the work area as a feature layer, then adding the features as either point/polyline/polygon layers spatially within. The hosted feature layer is configured with 4 layers, "Project Area", "Polygon", "Point", "Polyline". There's a arcade script that runs to sequentially generate a numerical ID in the "Project Area" attribute table, and a script that grabs the underlying "Project Area ID" and inserts that into each of the other feature classes attribute tables. Relationship classes are defined for each other layer that associates the points/polygons/polylines with their respective "Project Areas", essentially creating a dynamic spatial join.
My rationale is to enable the manager to enter a variety of attributes specific to the project in the "Project Area" feature class and have each other feature created within be associated with that project. Also allows for one click deletion of all a project's content and hopefully can figure a way to filter/export the child records (point/polygon/polyline features) for reporting purposes.
This seems like a very clunky way to replicate Google Earth's folder structure, and while it mostly works now, I'm worried that minor issues will continue to pop up (e.g. creating a feature outside a "Project Area" currently causes an error message). I'm hoping someone here has experience or insight to figure out a better architecture for achieving this setup.
Thanks in advance!
