Validate _connectivity rule in AA

2262
17
04-18-2017 03:09 PM
elvissoto
New Contributor

I work for a gas company, we have point feature class which has 5 subtypes with different connections like reducer has 2, three way tee has 3  and so on , I am trying to set Validate _connectivity rule for my value method in domain table, I am not sure how to use subtype under Table name. Can anyone help me?

0 Kudos
17 Replies
MikeMillerGIS
Esri Frequent Contributor

Last value is missing the value info

Here is the note from validate connectivity

Trying: VALIDATE_CONNECTIVITY
Feature and valueinfo is valid
Checking if feature is in a Geometric Network
ERROR: Feature is not a Geometric Network feature
Finished: VALIDATE_CONNECTIVITY

0 Kudos
elvissoto
New Contributor

Thanks for your response.

How about SPLIT_INTERSECTING_FEATURES methods, why it is not breaking main, does it have to be in Geometric Network too?

My another concern is placing End cap is taking long time about 5 min, if you see highlighted portion of log file , it is querying for 713300 features, I think that's the reason the process is taking longer. Also what does index 15 represents?

I use same Intersecting _Feature method for service line, which works fine, it took 2 sec to pull main ID field from Main feature class into service line table, when you see log file it is querying for only 1 feature which it should be doing.

Please help me with my questions.

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

What is your spatial reference?  

as for the split, the split operation is only returning one feature

  Split return no features

can you provide a sample dataset?

0 Kudos
elvissoto
New Contributor

If possible can you give your Email ID, I will send sample data to that, Instead of posting data online.

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

Mmiller@esri.com<mailto:Mmiller@esri.com>

Sent from my Verizon Wireless 4G LTE DROID

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

Doing some debugging:

The SPLIT_INTERSECTING_FEATURE rule is not valid for geometric network features.  You can use the Add Point and Spit Intersecting line construction tool though.  There is a note in the help already

http://solutions.arcgis.com/shared/help/attribute-assistant/documentation/methods-all-methods/#split...

When using Intersecting_Edge, you only need to specify the field, not Layer|Field in the value info as it detects the edge from the geometric network.

For intersecting feature with lots of features, what scale are you editing at?  The current code evaluates the map tolerance as well as the xy resolution to ensure the point finds the line.  The problem with the map tolerance is as you zoom out, the search area widens.  I think I revert this and only use data tolerance.  Your map, you do not happen to be in Decimal Degrees, are you?

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

I posted a preview build here, can you try this version.

local-government-desktop-addins/PreviewBuilds at dev · Esri/local-government-desktop-addins · GitHub 

I updated the intersecting feature logic and added some error messaging

Intersecting_feature - Search tolerance rework · Issue #236 · Esri/local-government-desktop-addins ·... 

Also expose a new option in the aa.config to clear the last value on stop editing like you requested.

New Option - AA - Clear last value on stop editing · Issue #235 · Esri/local-government-desktop-addi... 

0 Kudos
elvissoto
New Contributor

When using Intersecting_Edge, you only need to specify the field, not Layer|Field in the value info as it detects the edge from the geometric network----We don’t have geometric network built in so I am not sure whether method works for us.

 

For intersecting feature with lots of features, what scale are you editing at?  It depends on Technician; we don’t have standard scale value.

 

The current code evaluates the map tolerance as well as the xy resolution to ensure the point finds the line.  The problem with the map tolerance is as you zoom out, the search area widens,  I think I revert this and only use data tolerance —I noticed that too , now adding feature is not taking too long.

 

Your map, you do not happen to be in Decimal Degrees, are you?----No we don’t.

 

Also expose a new option in the aa.config to clear the last value on stop editing like you requested.--- It works now, whenever I stop the edits it erases my values. This is what we are looking for.

 

 

Mike ,thanks for your help.Awesome work!

 

 

 

 

 

 

 

0 Kudos