Latest Contributions by ChristineLeslie

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? ... View more

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 ... View more

 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.      ... View more

  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   ... View more

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   ... View more

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. ... View more

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 ... View more

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   ... View more

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 ... View more

Hi Drew Rather than set the accuracies to NULL, I would decrease their values - ie make the accuracies higher. See this excerpt from the doc below, which gives an example: If the Rigorous Sigma Zero value is significantly less than 1, the estimated a priori accuracies (or weights) may be too low, meaning that the numeric accuracy values may be too large. This also means that some or all the measurements can be given higher weights based on the statistics. For parcel data, this can often indicate that the COGO dimensions were calculated from the line shape geometry rather than entered from the original parcel record. The tool displays a warning message to indicate that the direction and distance values are unusually good for the given distance and direction accuracy values. To achieve a Rigorous Sigma Zero value closer to 1, increase the estimated accuracies (give them a higher weight) by decreasing the numeric values. For example, decrease a 30 seconds accuracy estimate for directions to 5 seconds to give it higher weight, and run the adjustment again. If the Rigorous Sigma Zero value is larger than 1, the estimated a priori accuracies (or weights) may be too high, meaning that the numeric accuracy values may be too small. To improve the result, first use the adjustment feature classes to identify and correct any measurements that are flagged as outliers. Then run the adjustment again. If there are no measurements flagged as outliers, decrease the estimated accuracies (increase the numeric values). For example, increase a 0.59-foot estimate for distances to 0.8 feet. Christine   ... View more