Latest Contributions by ChristineLeslie

‎06-23-2025

Hi - I would look into attribute rules to catch this - perhaps a constraint type attribute rule?

‎03-28-2024

Hi You can use the Update COGO tool to do this. The lines are already COGO enabled in the parcel fabric by default. https://pro.arcgis.com/en/pro-app/latest/help/editing/update-cogo-attributes.htm Christine

‎03-28-2024

Yes you can restart/resume a traverse by tracing in the lines into the traverse grid. Trace in the lines, make your edits and the lines will reflect the edits. https://pro.arcgis.com/en/pro-app/latest/help/editing/create-a-traverse.htm#ESRI_SECTION1_08880D70C629456C8085E727047700B1 However if you have built a parcel, you will need to do Reconstruct From Seeds first... https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/reconstructfromseeds.htm Christine

‎02-29-2024

Hi Seneca Could you try using the Circular Arc tool to calculate curve parameters? - use your existing, known parameters to create the circular arc and then once the arc is created, change the Delta parameter to Radius to obtain the radius of the arc. https://pro.arcgis.com/en/pro-app/3.1/help/editing/calculate-circular-arcs.htm

‎02-16-2024

Correct - to follow on from Kevins comment- do the red and yellow parcel lines belong to the same record or to different records? I am presuming they are associated to the same record seeing that seeds have already been created?

‎02-16-2024

Hi - there is no reason why you cant let current parcels overlap within the same parcel type. There is nothing that will make the parcel fabric not perform properly if current parcels overlap. There is also no default topology rule that prevents overlapping polygons either - andusers are free to add that rule if they need it for their organization - but it is not added by default. Also, we model floor-level parcels as overlapping parcels in a parcel type that supports strata parcels. Hope this helps Christine

‎01-23-2024

Hi Jamal The data attached did not contain parcel 129. So I just created an approximation. Here Parcel129 is assocaited to RecordFor129. To associate a parcel to a reacord, create the record, set it as active in the map and then select the parcel and assign it to the record you created: Now to split this parcel, create a new record for the split and set it as active. With the record as active, split the parcel Now to merge one of the split parcels with another parcel - make sure that other parcel is already associated to its original record. Then create a NEW RECORD for the merge and set it as active. Perform the merge. Now a lineage for the original record of parcel 129 shows this RecordFor129 created Parcel129, which was retired by record Split. Record Split created two new parcels Split1 and Split2. Split2 was retired by record Merge, which created MergedParcel. Please see the help docs and videos for more information on how to create and manage records.

‎01-19-2024

It seems you are doing a 1 to 1 relationship between parcels and records. If thats the case, your lineage will only ever show 1 parcel in a record - since that is what you are explicitly doing. 1 parcel for 1 record. This is how I see the correct workflow: Parcel 129 is assigned to an existing record A. You now want to split parcel 129 (this comes from a new record B that shows the split) So assuming parcel 129 is assigned to its original record A, you go and create a new record B to represent the split and put it active in the map. Perform the split Do a parcel lineage for Record B and you will see an appropriate lineage diagram. Simirlarly if you do a parcel lineage for Record A, you will also see the appropriate lineage diagram. So, in summary, parcel 129 must be assigned to its original record. Then the new record that represents the split is created and put as active in the map. The split is performed. Parcel lineage is tracked for both the records. I hope this helps

‎01-11-2024

Hi Deigo I can see from your screenshots that Version Management is missing under Capabilities and Include topology layer is missing under Feature Properties. All I can think of is - did you set the versioning type to Branch before you added the parcel fabric to the map? Christine

‎12-15-2023

There is the data model/schema documentation that shows which fields are used by the Pro parcel fabric. https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/aboutparcelfabricschema.htm However we dont explicitly tell users to remove upgraded ArcMap fields, since there may be data in those fields that are being used by that organizations parcel fabrc, and those fields should be migrated accross and kept. Its up to the user to decide which fields from ArcMap they no longer want to use.

‎12-11-2023

You can populate the COGO attributes of a line into COGO fields. First you have to enable Cogo on your line feature class to generate the COGO fields and then you can use the Update COGO tool to populate the line's COGO attributes into the Cogo fields.

‎08-29-2023

Hi Jamal In Pro 3.2 you will be able to view a Parcel Lineage tree for parcels in the parcel fabric using the Link Chart functionlity. Christine

‎08-18-2023

Hi Jamal When parcels are edited, the record they are associated with does not get edited in the same way. . Record updates happen in the following ways: The record retires the original parcels (that were split) as historic. New parcels that are created by the split are associated with the record. The record polgyon does not update since boundary of all the parcels associated with it does not change in a split. If new parcels are created in the record then the record polygon will update to reflect the cummulative boundary of the polgyons associated with it. The Created Parcel Count and Retired Parcel Count fields of the Record layer are updated when parcels are created or retired. Also, the parcel name should have nothing to do with the record name... The record reflects the document that created the parcels. https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/createparcelfabricrecords.htm#ESRI_SECTION1_C2F7A1F83DBE42309F659E39CDC1C4DB

‎07-25-2023

Hi I would definately use the geoprocessing tool. If you are processing large numbers of parcels that have many points, you may need to leave it run for a while. If you are still seeing issues with the Build tool, please contact tech support. - If it fails, it will need to be submitted as a bug. Christine

‎05-22-2023

Hi The consistency check is run on the entered COGO dimensions. So if a particular COGO dimension is not consistent with other COGO dimensions, it will be flagged as an outlier. So consistency check is is checking COGO dimensios against other COGO dimensions and not against the shape_length. I think it will only look at shapelength if the COGO values on the line are null. Because of that I wouldnt be using shape_length to get accuracy values. I would increase the accuracy values until you get Rigorous Sigma Zero value closer to 1. So you may have to run the check a few times, trying different accuracies - but it sounds like they do need to be high because the data is survey correct. If an entered dimension is wrong by 10 feet (either a typo from data entry or an actual typo on the document) - the consistency check should pick this up. To detect COGO mismatches with shape length - you can use the configured data quality layer -COGO mismatch. https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/parcelfabricdataqualitylayers.htm#ESRI_SECTION1_4F7D82CED82E4DE9B0CF34FC83082378 Christine

Online Status	Online
Date Last Visited	9 hours ago

My Ideas

Latest Contributions by ChristineLeslie

Re: Can Allow Null for Record Name be turned off?

Re: Displaying COGO Labels for Parcel Lines

Re: When creating a parcel via the traverse tool, how do I restart the traverse tool to make adjustments?

Re: Traverse curve with only angle and arc

Re: Overlapping Features: Platted Lands

Re: Overlapping Features: Platted Lands

Re: ArcGIS Pro 3.1.0: What is the best practice to display the tree of a parcel lineage history particularly in case of parcels merge?

Re: ArcGIS Pro 3.1.0: What is the best practice to display the tree of a parcel lineage history particularly in case of parcels merge?

Re: Publish the parcel fabric as a feature service missing properties

Re: ArcMap Parcel Fabric Fields that can be removed in Pro Fabric

Re: Find COGO of existing feature

Re: ArcGIS Pro 3.1.0: What is the best practice to display the tree of a parcel lineage history particularly in case of parcels merge?

Re: ArcGIS Pro 3.1.0: How to update the records layer after editing the parcel layer while working with the fabric?

Re: Build Parcel using Build Extent

Re: What does "Rigorous sigma zero value is low" warning mean?

Re: When creating a parcel via the traverse tool, ...

Re: Overlapping Features: Platted Lands

Re: ArcGIS Pro 3.1.0: What is the best practice to...

Re: Publish the parcel fabric as a feature service...

Re: ArcMap Parcel Fabric Fields that can be remove...

PLSS Editing