Latest Contributions by JoshSaad1

I recommend managing your local data in a geodatabase, and that it uses the OneSoltuion CAD data schema.  You can automate importing and transforming the shapefiles from your other agencies into the geodatabase using a geoprocessing model.  And, if it's already in the OneSoltuion schema, you can just export to shapefiles to convert to CAD without additional transformation. Geodatabases offer functionality that makes managing the data much easier, like versioning and archiving.  You can use either an Enterprise geodatabase in SQL, or store one (or more) locally as a file geodatabase, depending on whether you'll have multiple people editing the data simultaneously. It still sounds tricky determining which features to use for CAD if you'll be editing the data outside of the authoritative sources.  You could add a 'source' field to the data that identifies which is which, and use some logic in the data export to determine which features to use. ... View more

I just figured this out the other day.  You can use the Offset function in Arcade.  Here's the code that I use to calculate the neighborhood on the left-side of a road segment. //Set the neighborhood dataset, selecting only the neighborhood name field. var fsNbrhd = FeatureSetByName($datastore, "GIS.DBO.Neighborhood", ["nbrhdname"]) //Specifies the left-side of the road. If the offset is greater than 0, it will be the right-side. var RoadLeft = offset($feature, -1, 'feet', 'square') //Selects the neighborhood polygon on the left-side of the road. var fsNbrhdLeft = Intersects(fsNbrhd, RoadLeft) //Returns only the first intersecting polygon, in case there are overlaps. var NbrhdLeft = First(fsNbrhdLeft) if(NbrhdLeft == null) return null //Returns the name of the first intersecting neighborhood polygon on the left-side of the road segment. return NbrhdLeft.nbrhdname    ... View more