Latest Contributions by AmirBar-Maor

If a vertex is introduced in one feature class, validating topology would crack any other feature/feature class and create it (if within tolerance). Advice: NEVER change the geodatabase topology cluster tolerance or XY tolerance. If you are looking into automating alignment between features, there is a set of conflation tools. I would use the 2 highlighted. You will need additional processing to first create lines from the polygons though. Automating alignment can also corrupt your data, so be careful and review results before reconciling and posting them + automated tests. ... View more

115 layers is a map sounds way too many. Regardless of the data source, a map with so many layers is hard to manage and might be slow to draw and refresh. As for the number of parcel types in a parcel fabric: I would try to limit them to around 10  - the reason is that for many operations a database cursor is used to open the table and if you have 10 parcel types it translates to 20 cursors. On top of that many operations are impacted by topology (dirty areas, error features). For example: if you delete a feature we also check that there is no error associated with that feature + create a dirty area. So if you have so many 'types' of entities the recommendation is to try to consolidate them into a reasonable number of parcel types. For example: if you have 20 easement types they can all be in a single parcel type called 'Easements' and use a field called 'EasementType' to symbolize the different easement types.   Can you include feature classes that are not controlled by the parcel fabric in the parcel fabric topology? YES. Just make sure to create them in the same feature dataset. ... View more

As for differences in behavior between file GDB and using feature services - there should be no difference. Please contact technical support and submit a case. They could determine if this is an actual bug or a user error. ... View more

The parcel fabric supports the 'System of Record' concept. We want the parcels in our system to represent the legal recorded information. So if your legal description specifies the dimensions on the side lines to be split in certain dimensions or proportions, you should start the workflow by splitting the lines (Create record, Copy lines To active record, split lines, add a splitting line,  create seeds, build) But if your legal description is an 'area description' that states how the area needs to be divided - then there is no reason to split the lines as it was never mentioned in the legal description. Some parcel representations (e.g. Tax parcels for fiscal cadastre) require a dimension on every parcel edge. To meet this requirement you can easily use the Reconstruct Boundaries tool - it will add and remove boundary lines and make sure every parcel edge has a line with a dimension. As for differences in behavior between file GDB and using feature services - there should be no difference. Please contact technical support and submit a case. They could determine if this is an actual bug or a user error. Amir ... View more

@AlisonKelsey  The Divide tool will not divide the lines. In this example you can see that the lines are not divided:     If you want the lines to be divided you can use the Line Intersection tool after you perform the divide. Make sure to check the box to recalculate COGO values, then click on the 2 intersecting lines and lastly on the intersecting point. You can see the northern line has been already divided. ... View more