IDEA
|
@-_Ashley-B-Potter_- my comment was from 2014. Back then we worked with the State of Montana (MSL) and the State of Utah (SITLA, AGRC, BLM). Since then BLM has also adopted the parcel fabric and for the most part moved to the new parcel fabric in ArcGIS Pro. Which organization do you work for? in which state? maybe @MikeZummo or @JerryNeff can help.
... View more
Wednesday
|
0
|
0
|
16
|
POST
|
@DenverBilling Overwriting feature classes can be dangerous... I usually delete the feature dataset on my enterprise before copying the updated feature dataset from staging. Then you can follow the steps to publish it for editing. This process is well documented here: https://pro.arcgis.com/en/pro-app/latest/help/data/parcel-editing/workflow-publishpf.htm
... View more
Wednesday
|
0
|
1
|
36
|
POST
|
And here is another idea, assuming I understand it right 🙂 The good thing about records is that they are a simple feature class and you can edit any attribute you want. From my understanding, the records were not created correctly and you want to recreate them. In that case the steps would be: Open the Attribute table and select all the record features Delete them Save edits Run the geoprocessing tool Create Parcel Records. You can use an expression if you want to refine the resulting record name. But... you probably already created some records since the migration in December that you want to keep. In that case: Make sure to only select the records that were created during data migration. You can use the editor tracking field for that. Likewise, for the input parcel features for the geoprocessing tool Create Parcel Records - select the features that were created in December. You can use the editor tracking field for that. You can batch-update the record type in the attribute table. Select the records you want to update and use the Calculate field to update them. You can even temporarily join the records table to another table if you need to. Hopefully one of these answers helps you and others in the community
... View more
Wednesday
|
2
|
1
|
34
|
POST
|
Hello @DenverBilling The term "hosted" usually refers to storing the data in the Enterprise's internal self-managed datastore. If your data is on an enterprise geodatabase (using a DBMS), you cannot edit the data directly. We recommend performing all the data migration on a file geodatabase, then copying it to the Enterprise geodatabase, and publishing it for multi-user editing (branch versioning). Using the geoprocessing Truncate on a table that is controlled by a geodatabase topology will not work. Instead, use the geoprocessing tool 'Delete Rows'. So the workflow might look like this: Copy the data to a file geodatabase: copy the entire feature dataset is the preferred way. Use geoprocessing tool Delete Rows to empty it Append the data to to the empty table Copy the feature dataset containing the parcel fabric back to the enterprise geoedatabsase. If you have a very large amount of data you can consider running the geoprocessign "Disable Parcel topology' before deleting the rows and appending the data, append the data and then run geoprocessing tool Enable Parcel Topology. Let us know if this worked for you
... View more
Tuesday
|
1
|
1
|
75
|
BLOG
|
@KatClifton If you are upgrading from the ArcMap Parcel Fabric to the new one you do not need this step. This tool is only intended for customers who used the old ArcMap COGO schema (string-based).
... View more
a week ago
|
1
|
0
|
198
|
POST
|
Apologies for this issue. As stated correctly by @AliciaTompkins this issue has been fixed in ArcGIS Pro 3.3. We also plan to include the fix in the next 3.2 patch (3.2.3).
... View more
2 weeks ago
|
0
|
0
|
104
|
IDEA
|
The parcel fabric uses standard geodatabase topology, and since topology runs on the entire table, ignoring any filtering, it is not possible for it to ignore certain parcel states. Maybe a better location for such an idea, for topology to ignore certain features using a SQL query, should be part of the geodatabase ideas?!
... View more
3 weeks ago
|
0
|
0
|
65
|
IDEA
|
The Highlight Gaps and Overlaps tool has been enhanced to work on all visible layers with ArcGIS Pro 3.3. Using subtypes can add complexity to your rules, layers, and editing feature templates - so make sure you really need them.
... View more
3 weeks ago
|
0
|
0
|
66
|
IDEA
|
Closing the idea: No clarifications provided No other users found value in it
... View more
3 weeks ago
|
0
|
0
|
44
|
IDEA
|
@JeffWard In this example, using ArcGIS Pro 3.3, the curve entry was changed from 'Delta Angle' to 'Arc Length'. Both values reflect the data as it was entered. This allows the user to compare the entered data to the entries in the traverse grid. Did we solve the problem? or are you asking for a 'refresh' button to show you the values in a certain way = Delta Angle, chord, Arc Length? Couldn't that just be a label expression that shows all 3 for any curve?
... View more
3 weeks ago
|
0
|
0
|
44
|
IDEA
|
We no longer plan to make any enhancements to ArcMap Parcel Fabric. The new parcel fabric does not have line categories.
... View more
3 weeks ago
|
0
|
0
|
43
|
Title | Kudos | Posted |
---|---|---|
2 | Wednesday | |
1 | Tuesday | |
1 | a week ago | |
1 | 3 weeks ago | |
2 | 03-08-2024 04:52 AM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|