nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro Topology Not Working

MichaelSnook

Hi,

I have been attempting to validate topology errors in the Pro Parcel Fabric (feature service) with little success. I can see the errors and the potential fixes for them but when I select the appropriate fix nothing happens. I have tried selecting from the right-click on the error inspector as well as the fix dialog with the same results.

I thought I'd test this out with a simple file geodatabase with just lines and polygons with a 'boundary must be covered by lines rule'. When I attempt to create the topology via the wizard I get a ERROR 999999 message.

Any ideas here? I'm submitting a bug as well.

Thanks!

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

MatthewDriscoll

Any chance you figured this out? I am having the same problems.

KoryKramer

Matthew - sorry that you're running into this. It looks like the following bug was logged BUG-000122096: In ArcGIS Pro, an error occurs when attempting to sa..

You can go to that link and click the Subscribe button. That will provide updates, and also increment the number of customers affected.

MikeSnook

Hi Kory,

Are there any updates to the issue with the Parcel Fabric Topology error inspector described above? I have reloaded a fabric twice with the same results. I am using and PostGres 11 and hosting the fabric via features service for editing in Pro. When I use the topology Error Inspector and attempt to fix errors (any errors at this point) nothing happens when I select 'Fix' from the preview window or if I right-click the errors in the table.

Thanks

Mike

KatherineStaley

I have the same problem.

BranislavBlagojevic

This Bug was noted by users in version 2.3, in Beta 2.4, but the ESRI development team, as well as a number of other non-functional things in ArcGIS Pro, persistently, persistently ... I G N O R E U S E R S!

Anonymous User

I am getting the same error...Please esri QC your products. This is yet another situation where I have to go back to using ArcMap.

ArianaToth

The Bug report linked above says this was fixed in version 2.6 but I'm still having this issue in 2.9.

Esri, please fix this!

MichaelSnook

3.0 doesn't seem to work any better. Topology and tools are really flaky. Sometimes the 'Validate Topology' button on the ribbon will work, sometimes not. Other times when that doesn't work, the 'Validate' button on the Error Inspector will work but sometimes not. Sometimes I can use the 'Fix' pane in the Error Inspector to fix isses that I've highlighted, sometimes not. There's really no rhyme or reason.

I've been through several support tickets with the fabric and it takes so much of my time that I'm hesitant to start another one.

FWIW We are using 10.9.1 Enterprise, Pro 3.0.1 and PostGres 13.3 backend -- all patches installed on relavent machines.

Mike

Vanilla2020

I have the similar issue for ArcGIS Pro 3.12. I cannot select any specific errors in the error table through the Error Inspector window, I can only select the errors on the map. Does anyone have the similar issues?

AzizTejan-Jalloh

I am running into this issue on ArcGIS Pro 3.1.3.

NaomiKalman

I was running into the same problem: flaky, inconsistent. Sometimes it would create a feature in a gap and sometimes not. Delete and merge were working. I have discovered that the create feature option doesn't work when someone has used a true curve option, with a distance and curvature. My workaround has been to pick one side, move the vertices or delete them so that a nice big gap opens up, then re-validate the topology in that area and create a feature in the big, clean space. It will match up nicely with the curve on the other side.

AmirBar-Maor

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.

EddieQuinlan1

AmirBar-Maor, I've been following your videos and instructions for the past 2 years or so while developing and converting our parcel data built with regions in arc/info to our current beta parcel fabric. The issue I'm finding is something as described in this thread, but I'll do my best to describe.

For testing purposes I've been trying to do a simple split of a parcel, utilizing 2 existing points on the polyline and using the traverse straight line tool to draw a line between the 2 points. When I do this, the heads up display indicates the line end points are snapping to that node(s). However, when I get to the point of creating seeds sometimes it will and other times it errors. My issue thought is the topology. When it creates the seeds and the fabric "appears" to be created as it should the topology doesn't appear to be retained. If i zoom in (1:0.01) as far as possible on the point 2 or 3 separate polylines and/or parcels appear to be created and not snapped at the point.

Running the error checking and based on the seeds being created the fabric "looks" like it is correct. But because I visually see the spatial differences between the point, polyline, and parcel, it gives me concern that the topology is truly being enforced. I don't want to lose our topology that has existed for over 25 years in our data. Am i being concerned over something that doesn't exist and is maybe a display issue? I have refreshed the display cache with no luck.

I've tried so many things...... too numerous to mention, but can't seem to get a split to visually snap properly.

I've attached a screen shot to help explain. Any thoughts are much appreciated.

Topology display on fabric.png

AmirBar-Maor

@EddieQuinlan1

It is hard to tell if the issue is a display issue or a topology data issue without having a reproducible case. Can you work with technical support to submit a case so they can have a look into it.
Validate involves 'cracking and clustering' - does validating the extent fixes the issue?
You screenshot shows a parcel labeled as a 'Seed' - a seed should have a smaller geometry bounded by a closed loop of lines. Please try to use 'Shrink to Seed' and then 'Reconstruct from seed'

EddieQuinlan1

Thank you for the insight. After writing my post and further testing, i did see where validate the extent using the geoprocessing seemed to fix the issue. Your response seems to support this. I will need to do further testing to feel confident this is the solution. I will review the "cracking and clustering".

I think one of the issues was my team using the "create seeds" and "build" process; thus believing the topology was built and cleaned (old school arc/info "build" and "clean" topology). This apparently is not the case?

AmirBar-Maor

@EddieQuinlan1 - yes, we will be in the conference and would love to meet.

Please DM me to coordinate + include the organization you work for.

Validate can be executed as an interactive tool using the Validate Extent on the Quality ribbon as well as a geoprocessing tool for validating larger extents that might take a long while to process.
For regular work I would opt for using the interactive tool:

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.