|
IDEA
|
@DarylHochhalter We recommend you watch this recording about how to COGO in ArcGIS Pro. COGO did not go away in ArcGIS Pro - it just got better. If you have COGO values today in ArcMap (those are text fields) you can use this script to convert them to the improved COGO schema in ArcGIS Pro. If you are using COGO entry to maintain parcels you should migrate to the parcel fabric. It will improve the efficiency and quality of your data. ArcGIS is a 'System of Record' - so if you go through the effort of manually entering COGO measurements you might as well persist them as attributes. This will also allow you to perform better quality assurance and the parcel fabric has dedicated layers as well as attribute rules (validation) to catch any errors. Loading COGO from Sketch will fail if you don't have the correct ground-to-grid (combined scale factor) correction turned on. Migrating your data to the parcel fabric is easy because the new parcel fabric controls simple feature classes. It also uses a geodatabase topology which you might already be familiar with. Beyond COGO you get many more capabilities that are required to maintain land records / cadastral records. It only takes a few days to a couple of weeks for most editors to get used to editing in ArcGIS Pro. There is also a dedicated training course for parcel editing.
... View more
11-07-2023
12:02 AM
|
0
|
0
|
2853
|
|
IDEA
|
@SarahSibbett These are the 7 steps required if using the Merge Points idea: 1. Create an active Record 2. Create a new point and enter the XY Coordiantes 3. Attribute the new point 4. Launce the merge points tool 5. Set the merge points settings (preserve attributes, only geometry) 6. Select the points to merge - must be only 2 - right?! What if there are 3 or more? 7. Press Merge Points These are the 5 steps required if using the Edit Vertices idea: 1. Create an Active Record 2. Select the point to be updated 3. Launce the Edit vertices tool and enter the XY coordinates 4. Attribute the point 5. Associate the point to the active record Did I get it right?
... View more
11-02-2023
04:47 AM
|
0
|
0
|
4256
|
|
IDEA
|
@SarahSibbett If the editor knows which points need to be updated they can: Select the point Update its geometry using the Edit Vertices tool (note: the tool needs to be enhanced. Currently it moves the point but does not update the parcel and its lines) (optional) update any other attribute and/or associate to a record We can also prevent/warn the user if this movement breaks the data integrity of the parcel.
... View more
10-31-2023
06:39 AM
|
0
|
0
|
4280
|
|
IDEA
|
@SarahSibbett Does the editor know which point they are going to update? If yes: would improving the Edit Vertices tool such that after updating a point XY coordinates it maintains the parcel topological integrity make sense? (one step instead of 2 step process)
... View more
10-30-2023
06:02 AM
|
0
|
0
|
4314
|
|
IDEA
|
@SarahSibbett @SusanHenton writes that "The control points we are importing usually do not sit on the parcel corner they represent." Are they imported or entered manually? Assuming you read the XY coordinates from a spreadsheet you can automate this process and string the Geoprocessing tool mentioned above. Importing points from the same source to the same target is not supported and is not really an 'Import'.
... View more
10-27-2023
12:57 AM
|
0
|
0
|
4346
|
|
IDEA
|
Did you consider using the geoprocessing tool Import Parcel Fabric Points? It allows you to match new points with existing points and choose the type of update: For example - only update the geometry but preserve the attributes of the target point.
... View more
10-25-2023
08:10 AM
|
0
|
0
|
4384
|
|
POST
|
@CFECAK Did you check your editing status? Could you please ensure your links, anchor points, parcel fabric points, and the parcel being adjusted are all editable?
... View more
10-15-2023
05:14 AM
|
0
|
0
|
1204
|
|
POST
|
There are 2 options: Any system attribute rule can be modified. You can modify the rule 'MUST HAVE A RECORD' to always return 'true' for these specific parcel types. However, I would recommend creating a record called 'Unknown', 'CAD NSDI', or 'BLM' and associating them to the parcels at hand. Why? In the future, you might have a valid source for these parcel types and it would be easy to distinguish between parcels that have no record (CreatedByRecord IS NULL) and those that are associated with the 'Unknown' record.
... View more
10-10-2023
11:25 PM
|
0
|
1
|
1692
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 4 weeks ago | |
| 1 | a month ago | |
| 3 | a month ago | |
| 2 | a month ago | |
| 1 | 06-12-2023 01:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|