AnsweredAssumed Answered

Handling CadNSDI's PLSSConflictedAreas in a fabric

Question asked by dbollinger on Aug 19, 2019
Latest reply on Sep 3, 2019 by lbeauchamp@blm.gov_BLM_EGIS

The default tools that ship with the Land Survey Editing don't deal with the conflicted areas polygons, so I'm wondering if and how to represent them in the fabric.  We'll be doing county-wide adjustments against local control, so I'd want them to be adjusted along with the rest of the survey data.


Truthfully, they don't get used much, and are really just "metadata" functionally, but for consistency it would seem I'd want them in the fabric just so that they can be properly published back out in post-adjusted form (so as to still match everything else post-adjustment).


If kept inside the fabric..  my initial thought was to add another type to the lrSpecialSurveyType domain, similar to how meandered water is handled, and just load them there.  Then modify the publishing script so that 1) conflicted areas, 2) meandered water, and 3) everything else are all properly sorted out during publishing from the type=4 special surveys in the fabric.


Anything wrong with that approach?  The lack of a pre-existing domain value (and absence from the publishing script) makes me wonder if conflicted areas were either 1) not yet accounted for in the model, or 2) considered, but not expected to be inside the fabric.


If kept outside the fabric, and just "brought along" with adjustments... my concern would be that I don't know the CadNSDI data model well enough to know if conflicted area boundaries are allowed to be "unique" (ie, not represented by any other feature) in which case you'd definitely need them in the fabric to get a full/proper export of all PLSSPoints and PLSSIntersectedAreas.


Perhaps a simpler way to word that secondary question might be:  could conflicted areas be ignored ENTIRELY without affecting the validity of publishing?