IDEA
|
@DucksInaRiver Migrating to the parcel fabric is easy, but to make it even easier you I have zipped the map package with the georeferenced plat. I'll find how to upload it later today
... View more
Tuesday
|
0
|
0
|
19
|
IDEA
|
One idea that comes to mind is: Adding a field, for example, called 'DeleteOK' Adding an Attribute Rule constraint rule that is triggered 'on delete' operations and only allows features to be deleted if they have $feature.DeleteOK ==1 This will prevent any feature from being deleted accidentally as you have to set DeleteOK to '1' in order to be able to delete it. Would this work?
... View more
Tuesday
|
0
|
0
|
109
|
IDEA
|
@DucksInaRiver I had time yesterday to look into it. Apologies for the wait time. This is a challenging plat: No coordinates or control point to tie to making it hard to georeference No surrounding parcels to tie to Poor spatial accuracy Natural boundaries without COGO dimensions --> no misclose information to detect blunders Missing COGO information For example: There is a missing course in this location But I assume you are used to that reality in VA. When you use parcel fabric lines to enter the data, you can switch to digitizing mode which allows you to enter natural boundaries by digitizing them. You can even prepare different boundary line types to distinguish between natural boundaries, road frontage, side lots lines etc. I decided to start with Parcel A with the point marked as '1', encountered a missing course marked as point '2', and never reached the water with the course of 470' (+/-) marked as '3'. Maybe the course going to the river should have been 870' instead of 470'? You can see in the screenshot about that when you use lines to enter the traverse: Your edits are saved as individual features - making it easy to stop, save edits and return to it at a later time. Labels show you the COGO attributes you have entered - making it easy to compare to the georeferenced dimensions on the plat. You can switch to digitising mode for natural boundaries. You can maintain different boundary line types, which have an impact on zoning. When you use the parcel fabric you have additional benefits in the context of entering this plat: All the features you create (boundary lines and parcels) are associated to the 'Point Of Rocks Park' record. You can filter the data to only see the features associated with the 'Active Record' = 'Point Of Rocks Park' record. You can use the Align Parcels tool to align the newly entered parcels with the surrounding parcels / subdivisions. You can maintain historic parcels. You can run a LSA to detect blunders in your COGO. I hope this helps Amir
... View more
Tuesday
|
0
|
0
|
41
|
IDEA
|
Hi Jeff, This is an interesting idea. We usually try not to alter the recorded COGO dimensions and instead update the 'Rotation' and 'Scale' fields on the lines. The Ground to Grid correction can yield similar results but it would not change the COGO fields, and you might already be using it for the real ground to grid corrections. Is there a case where you would want to use the Rotate tool and NOT update the COGO dimensions? To be consistent, should the Resize tool update the linear dimensions?
... View more
Monday
|
0
|
0
|
81
|
IDEA
|
@SamMontoia1 Thanks for the quick response. When developing and testing COGO Reader we tested with deeds from many states, but not all them, and surely not with enough deeds from Colorado. I've created a bug for missing out on those directions. The words 'bears' and 'running' are throwing it off. If you remove those words it will pick it up correctly, including the connection line:
... View more
Friday
|
0
|
0
|
72
|
IDEA
|
@SamMontoia1 The first release of COGO Reader does not support PLSS. Thank you for attaching the deed - it let's us see that it failed to read cardinal directions ('running north', 'running south'). We consider COGO reader missing reading the directions as a BUG and recommend opening a technical support case for those. Is your idea about pointing out to where COGO Reader has failed? Like selecting the text, right clicking and choosing 'Add as direction' or 'add as distance'? Or is the idea about teaching COGO Reader that 'running south' means 180 degrees (north azimuth format)?
... View more
Thursday
|
0
|
0
|
108
|
IDEA
|
@DucksInaRiver If you can share your plat we can record a video showing how to enter it. Please also supply the spatial reference and the combined scale factor. We will also show how easy it is to create a new parcel fabric and migrate to it (it takes less time than entering a plat)
... View more
2 weeks ago
|
0
|
0
|
102
|
POST
|
@ThomasHoman In that case, this might also be a good source: https://pro.arcgis.com/en/pro-app/latest/help/editing/direction-formats-for-editing.htm
... View more
2 weeks ago
|
0
|
1
|
142
|
POST
|
@ThomasHoman Thanks for sharing. Dumb question... Did you create it to use with paper maps? Hang on the wall to get the new user used to the quadrant bearing? or as an image to insert in a layout? Other?
... View more
2 weeks ago
|
0
|
0
|
162
|
POST
|
The parcel fabric was designed to support Administrative Parcels (like the districts mentioned above). When creating a new parcel type you have the option to make it Administrative. This makes sense when the 'parcels' (admin boundaries) coincide with the parcel layer. For performance reasons, it would be good to try and consolidate the number of 'parcel types'. This approach assumes that the datasets align to each other to start with. If they don't you have to start with a conflation project. Another option, which is more labor-intensive and requires good 'bookkeeping', is available for those using ArcGIS Enterprise: use the geoprocessing Generate Parcel Fabric Links between 2 moments in time, and then apply the generated links and anchor points using the Rubbersheet Features tool to related data.
... View more
2 weeks ago
|
0
|
0
|
88
|
POST
|
An XML Workspace is useful when you want to create an identical schema in multiple environments, for example - for digital submission workflows, before the data is appended to a named version. In your case, you are correct - deleting the dataset and copying the updated data from the file geodatabase is the most straight forward. The reason deleting rows is slow is because of the messaging that takes place between related tables (relationship classes), the need to update the dirty areas and error tables every time a feature is deleted, potentially firing attribute rules as well.
... View more
4 weeks ago
|
1
|
1
|
393
|
POST
|
When the data is copied from a file to an enterprise geodatabase, the table names used in the expressions should be swizzled to the new names. If the rules use table names that are not available in the source and target, I would disable those rules. If that approach fails, you will quickly find out. BTW - if you want to create an empty schema quickly, instead of using delete rows, you can export an XML workspace (schema only), delete the data, and then import the XML Workspace to create an empty schema.
... View more
4 weeks ago
|
1
|
1
|
145
|
BLOG
|
If you are using an enterprise deployment (feature services) and would like to see the name of the record in the popup, you will need to update the name of the relationship class with the name of the relationship between the 'layers'. You can find that name in the layer properties 'Relates' tab: Once you have updated the pop expression with the relationship name you should be good:
... View more
a month ago
|
0
|
0
|
57
|
Title | Kudos | Posted |
---|---|---|
1 | 4 weeks ago | |
1 | 4 weeks ago | |
1 | a month ago | |
1 | 03-14-2025 06:16 AM | |
1 | 02-10-2025 01:14 AM |
Online Status |
Online
|
Date Last Visited |
Tuesday
|