|
IDEA
|
@MizukiKayano2 Thanks for the detailed explanation. For the second example, you have a multipart parcel - but only 1 part (out of 3) gets updated. Wouldn't it be easier first to Explode it into 3 parcels, fix the defective part, and then use 'Merge into Existing' to recreate the multipart again? Other ideas that come to mind is to ignore the bad parcel, create a new one instead, and use the Transfer Attributes tool to transfer attributes between the bad to the good. Then delete the bad parcel and align the good one. If the surrounding parcels are very much off you can start by using the move/rotate/scale tool on points and edges to bring it closer. Moving points will also update any historic parcel that coincides. Is it needed to shrink the historic parcel to seed? If it shares the same points it will also move to the new point location. Also, keep in mind that Build does not build historic parcels.
... View more
12-21-2023
12:10 AM
|
0
|
0
|
3508
|
|
IDEA
|
@MizukiKayano2 For the first example, where you need to merge the error parcel (slivers) into the real parcels I would use the following workflow: Make sure you have an active record Select the parcel and the slivers Open the Merge tool on the 'Existing Feature' tab, select the parcel to preserve, Press Merge Would this work? Another option to consider: Delete all parcels Create one correct parcel Use Duplicate to duplicate it 4 more times FWIW- if the airspaces were to be 'floor aware', and each one has a different Floor Order value, each will be built/reconstructed independently. That means each will have it's own lines though.
... View more
12-20-2023
11:50 PM
|
0
|
0
|
3511
|
|
POST
|
@MarkByers Thank you for posting the question and the feedback. Questions challenge us - a daily riddle/problem to solve. It never ceases to amaze me that there are many different ways to perform a workflow. Even for a simple merge (combine) one can probably come up with 5 different methods, if not more.
... View more
12-19-2023
11:49 PM
|
1
|
0
|
2443
|
|
POST
|
@MarkByers I recommend that you: Use lines to enter the traverse and not a polygon. This will retain the COGO dimensions as attributes on the line features. After you enter the first easement, press Create Seeds and then press Build. Then, for any overlapping parcel, you can continue to enter lines and retain your COGO, but instead of using Create Seeds and Build, use the Construct Polygons tool. If selecting the lines consumes too much time, you can also consider creating seeds for each parcel part, then toggle off the Active Record, and use Merge into Existing Feature.
... View more
12-19-2023
12:01 AM
|
2
|
1
|
2487
|
|
IDEA
|
@MizukiKayano2 The workflow is not clear. It looks like you start by shrinking multiple coinciding parcels to their seed. Is that correct? Do they all share the same boundary lines or not? If not - which boundary lines belong to each parcel? A screenshot might be helpful here to understand why you shrink multiple parcels to start with. How common is this workflow?
... View more
12-18-2023
02:24 AM
|
0
|
0
|
3556
|
|
IDEA
|
@SeanLyons How would you know upfront which areas require manual links and which areas do not? And if you did know, wouldn't it be more efficient to align the 'manual' areas using the Align Features tool? Or maybe we should understand the use cases for 'manual link creation' and try to eliminate them (and/or convey there is an issue in those areas)?
... View more
12-15-2023
07:54 AM
|
0
|
0
|
1383
|
|
IDEA
|
@SeanLyons Any cadastral field survey attempts to locate, confirm, and collect the original demarcation in the field. I assume that if there is a conflict between the original survey to a later posting plan, the posting plan will win, after all, it was conducted to resolve uncertainties - is that correct? Sounds like you want to keep the original lines current - that is supported. You can create duplicate boundary lines stacked on top of each other, each associated with their plan. You can consider this workflow: Create a new record Select the posting boundary lines Copy Paste special to the appropriate target lines Create Seeds Shrink to Seed Build Active Use Align Parcels tool to align the new parcels From the record HUD - select all polygons Delete them You can also consider setting another category on boundary lines if you want to symbolize them differently. Even create a separate layer for them if needed.
... View more
12-15-2023
02:22 AM
|
0
|
0
|
2993
|
|
POST
|
@PrestonDallas1 Question: "Are multipart parcel polygons not recommended to be used within the parcel fabric? " Answer: the parcel fabric does support multipart parcels. You can create a multipart parcel by using the Merge tool with the option "into existing". With ArcGIS Pro 3.2 we also support using the Explode tool to convert it from multipart to single parts. If you have an active record and use Explode it will create parcel history. This feature was requested by your 'neighbors': HCAD. Question: Or is exploding the parcel, performing any edits, and merging the unchanged portions back into a multipart parcel the way to go? Answer: I didn't count the number of mouse clicks for each option. Keep in mind that you have to use 'Reconstruct from seeds' when the boundary lines around a seed are not associated with the same record as the seed (or not associated with any record).
... View more
12-14-2023
05:51 AM
|
0
|
0
|
2580
|
|
IDEA
|
@SeanLyons The attached plan does contain lot numbers - was this intentional? It also looks like: A posting plan is a form of a 'boundary resurvey' of parcel boundaries. The plan, like any other plan/record is registered/recorded. Should the old parcel boundaries get retired? If bullets 1 & 2 above are correct, a better workflow to reflect it would be: Create a new record Select the parcels to update Use Copy Lines To active record and create seeds (parcel attributes are not changed) Delete the copied lines Copy the new lines from the posting plan Build The above workflow will create parcel lineage to reflect the updated boundaries. If parcel lineage is not desired: Create a new record Select the parcels to update Shrink to Seed Delete parcel lines Copy the new lines from the posting plan Reconstruct from seeds Thoughts?
... View more
12-14-2023
04:29 AM
|
0
|
0
|
3023
|
|
DOC
|
@VogtBoat Did you try to uncheck the 'Use template' option? That will preserve the attribute of the selected parcel
... View more
12-11-2023
11:56 PM
|
0
|
0
|
1754
|
|
POST
|
@MervynLotter Reducing the number of vertices in your geometries will reduce their size with the default XY tolerance. We had a customer who reduced the XY resolution on their parcel data and it corrupted it. Like with image resolution, this process is not reversible. Even with vegetation unit boundaries, you might think it's OK to reduce it, to later find out there is a gap between the vegetation and a natural boundary that is also used as a parcel boundary. IMHO the XY Resolution is an 'implementation detail' that should have never been exposed. Please be careful - your data is your greatest asset.
... View more
12-11-2023
01:13 AM
|
0
|
0
|
2367
|
|
IDEA
|
@RobertChaney Do you maintain the 'Lot Number' and 'Parcel Number' on the same feature? What is the difference between the PID and the PIN? (assuming they stand for Parcel ID & Parcel Identification Number)
... View more
12-11-2023
12:51 AM
|
0
|
0
|
2489
|
|
POST
|
@T_R The parcel fabric team is working (R&D) on importing traverse courses from deeds.
... View more
12-08-2023
08:00 AM
|
0
|
0
|
1087
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 1 | 3 weeks ago | |
| 3 | 3 weeks ago | |
| 2 | 3 weeks ago | |
| 1 | 06-12-2023 01:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|