Just wondering how many of you were incorporating the PLSS data (Sections, Quarter Sections, etc.) in the babric? We were thinking about putting it into ours, and were wondering if that is best practice. Thanks in advance!
I am in the process of conversion and I am choosing to start with PLSS sections and then "Construct from parent." When I finish building the parcels in the section, I build and keep all current. The new parcels are "Parcel type" 7 and the sections are "Parcel type" 2. Townships are "Parcel Type" 1. I use the Land Records Template, as described in the white paper.
I am in the process of conversion and I am choosing to start with PLSS sections and then "Construct from parent." When I finish building the parcels in the section, I build and keep all current. The new parcels are "Parcel type" 7 and the sections are "Parcel type" 2. Townships are "Parcel Type" 1. I use the Land Records Template, as described in the white paper.
We have chosen not incorporate PLSS into fabric because we view it as purely representational. We seperate PLSS as its own FC that is not in Fabric. Can you please tell me why you have decided to include PLSS. I am not questioning your process but just want to understand why you would build PLSS into the fabric. I am aware that the type exists for PLSS (T&R and Section, etc) but we have found that the only data we need to record in Fabric are Assessor specific (Tax Parcels, Lots, ROW, etc).
We have chosen not incorporate PLSS into fabric because we view it as purely representational. We seperate PLSS as its own FC that is not in Fabric. Can you please tell me why you have decided to include PLSS. I am not questioning your process but just want to understand why you would build PLSS into the fabric. I am aware that the type exists for PLSS (T&R and Section, etc) but we have found that the only data we need to record in Fabric are Assessor specific (Tax Parcels, Lots, ROW, etc).
Hey Carlos,
We are carrying the PLSS info. in our fabric for two reasons. The first being that we incorporate land records information beyond our corporate limits (city limits) which often result in larger tracts which just refer to Quarter Section and Section lines in deeds that provide no legal. Secondly, we feel as though carrying the PLSS data in the fabric will provide an extra layer or two of redundency for least-squares adjustments, particularyly around the edges of our mapping extent.
We are carrying the PLSS info. in our fabric for two reasons. The first being that we incorporate land records information beyond our corporate limits (city limits) which often result in larger tracts which just refer to Quarter Section and Section lines in deeds that provide no legal. Secondly, we feel as though carrying the PLSS data in the fabric will provide an extra layer or two of redundency for least-squares adjustments, particularyly around the edges of our mapping extent.
Ok, but if you do have new development outside your normal boundary then you should be able to get the survey data for it. Our though is that with old Assessor maps that have no real data and are raster we would just wait until something changed and then use the CAD data to easily import the parcels, lots, control points etc to Fabric.
Here is a question Mike (Member of our GIS Team) and I came up with about this. This is more for ESRI dev. staff monitoring this thread, but maybe one of you can answer it.
Say PLSS is stored as parcels (as we are discussing) with the correct type.
We perform a least squares adjustment
Will the PLSS parcels warp / adjust wtih the rest of the fabric? -if this is true then you've just messed up your PLSS -can you exclude certain parcel types from the least squares adj.
Another thought -Do we first have to convert all PLSS intersections to points and imported them as control points with a certain accuracy to even be able to use PLSS to perform a least squares adj where PLSS is taken into account?
