|
IDEA
|
@AbigailSmith18 ArcGIS Pro 3.5 will display the misclose direction and distance: Tip: you can always right-click to copy this information for 'safekeeping'.
... View more
02-04-2025
02:34 AM
|
0
|
0
|
1517
|
|
IDEA
|
@NabilDroby1 thanks for confirming that the misclose as X & Y is not crucial. From our perspective, adding information that cannot help only clutters the UI and adds confusion. The direction and distance, on the other hand, can help identify the course in which the blunder might have occurred.
... View more
02-03-2025
03:15 AM
|
0
|
0
|
1532
|
|
IDEA
|
Hello @NabilDroby1 With the traverse pane in ArcGIS Pro you can set the start and closing location. You can define the location by snapping to an existing point or right-clicking on the map and entering the coordinates values. Use the traverse settings to enter Set your desired closure tolerance. You can also consider using the options to force closure or you can simply enter an asterisk ('*') after the last distance to force it (even if you're outside the tolerance. The traverse courses are numbered using Pro 3.4. Do your deeds include coordinates? If yes you can also start by entering that location as a point. We also recommend reading the help documentation and/or taking a course to learn how to maintain parcels in ArcGIS Pro efficiently.
... View more
02-03-2025
01:23 AM
|
0
|
0
|
2793
|
|
IDEA
|
01-20-2025
04:40 AM
|
0
|
0
|
1075
|
|
POST
|
See the workflow above. You cannot use the geoprocessing Truncate table on a feature class that participates in a topology.
... View more
01-20-2025
01:34 AM
|
0
|
0
|
1678
|
|
POST
|
The parcel fabric uses the standard geodatabase topology. If you see any bugs related to geodatabase topology like validation or error inspector please submit a case with technical support. You are welcome to DM me with your case number.
... View more
01-17-2025
02:28 AM
|
0
|
5
|
898
|
|
POST
|
@MyEthiopia I recommend that you contact technical support and have them look into your specific configuration (DBMS, Enterprise, Pro) and the workflow. Many things might have caused it and we haven't seen that before. Did you calculate a field on a lot of features? could it be that your server timed out? Do you have any attribute rules that might have failed and caused it? Did you check your DBMS logs to see if it failing?
... View more
01-15-2025
06:38 AM
|
1
|
1
|
4597
|
|
POST
|
If anyone else is following this thread and encountered that the geoprocessing tool 'Update COGO' does not recognize the feature class as 'COGO Enabled' here is the workaround. Instead of copying the data from the CAD layers to a new feature class append the CAD features to a COGO-enabled lines feature class. You can use these steps: If you are using the parcel fabric the line feature class is already COGO-Enabled. Else create a line feature class with the correct spatial reference and run the geoprocessing tool 'Enable COGO' Right click on the feature class and Export the feature class as a XML Workspance Document' (schema only). Every time you import a CAD file use the geoprocessing tool 'Import XML Workspace Document' to create a new COGO Enabled line feature class (or an entire feature dataset containing your staging parcel fabric). Use the geoprocessing append to append the CAD features to the COGO-Enabled line feature class. Steps 1 & 2 are only performed once. Steps 3 & 4 for each CAD file you process.
... View more
01-13-2025
01:01 AM
|
1
|
0
|
6596
|
|
POST
|
@kkoffi_crcjv The right thing is of course to open a technical support case... For a feature class to be deemed 'COGO Enabled' all the COGO fields have to exist AND the all have to be 'required'. Could you please open the attribute table of the feature class that got created and hover over the field name? You should see all COGO fields as 'Required': Please also check that the feature layer properties show that it is 'COGO Enabled': If they are not 'required' that is why the Update COGO tool refuses to process them. If it is not COGO Enabled the next step will be to figure out if COGO Enable fails or if they become non COGO Enabled by the Delete field tool. Please share your findings. You can also welcome to DM me and send me your model so we can look closer. I
... View more
01-10-2025
12:20 AM
|
0
|
1
|
6644
|
|
IDEA
|
@JasonBessert Thanks for the clarification. That makes sense.
... View more
01-09-2025
03:16 AM
|
0
|
0
|
1293
|
|
POST
|
@kkoffi_crcjv What is the error tooltip that you get when you hover over the "CAD Reduced Fields"? Could you test if it works when you supply it the previous 'Output Feature Class'? Can you check that the created feature class is indeed 'COGO Enabled'?
... View more
01-09-2025
03:07 AM
|
0
|
1
|
6657
|
|
IDEA
|
Hi Jason, Are you trying to merge two curves into one feature + eliminate the point between them? If yes try this: Make sure you have an active record, preferably of the record that created the curve. select the curves you want to merge Launce the merge tool and merge into 'Existing Feature' Before Merge: After Merge: There is also an idea to interactively fix densified curves (by tracing them).
... View more
01-08-2025
07:25 AM
|
0
|
0
|
1330
|
|
IDEA
|
@MizukiKayano2 LSA uses 'direction sets' as input so it's not that easy just to run a pre-process that flips lines. If you have 5 wrong directions + a few true blunders I would not expect LSA to converge and as @TimHodson has suggested, it would be best to identify and fix those blunders before running LSA. Then you'll be able to catch the 'real' outliers. A simple Attribute Rule calculation rule can detect and fix those blunders for you without any extra user work: the rule can either flip the geometry (SHP field) or add/subtract 180 degrees from the 'direction' (direction field). Where do those '5 blunders' come from? I suspect from an external source like a digital submission process. If that is true - why not improve the digital submission process? You can either reject lines that have the wrong direction or fix them as they come into the system?
... View more
01-03-2025
01:20 AM
|
0
|
0
|
2898
|
|
IDEA
|
@MizukiKayano2 One of the uses of LSA is to detect blunders. Having the wrong geometry, even when flipped, is wrong, and ignoring it can cause downstream effects in other areas. So it would be best to fix those bad geometries. What's the best way to correct the geometry by flipping them? Use the geoprocessing tool Flip Line Use an Attribute Rule (calculation) on the SHP field.
... View more
12-30-2024
03:41 AM
|
0
|
0
|
2939
|
|
IDEA
|
Do you use the attribute rule 'DIRECTION MUST MATCH WITHIN' that is shipped with the parcel fabric before running LSA? What would be the tolerance to consider a line as 'flipped'? (+-180 +???)
... View more
12-20-2024
05:33 AM
|
0
|
0
|
3030
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Friday | |
| 1 | Wednesday | |
| 3 | Wednesday | |
| 2 | Wednesday | |
| 1 | 06-12-2023 01:26 AM |
| Online Status |
Offline
|
| Date Last Visited |
8 hours ago
|