私はガス会社で働いています。ポイントフィーチャクラスには5つのサブタイプがあり、リデューサーは2つ、スリーウェイティーは3つなど、異なる接続があります。ドメインテーブルの値メソッドに対してValidate _connectivity ruleを設定しようとしていますが、テーブル名の下でサブタイプをどのように使用するか分かりません。どなたか助けていただけますか？
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!
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 · GitHub
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-addins · GitHub
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-intersecting-feature
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?
Mmiller@esri.com<mailto:Mmiller@esri.com>
Sent from my Verizon Wireless 4G LTE DROID
If possible can you give your Email ID, I will send sample data to that, Instead of posting data online.
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?
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.
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
Michael Miller any feedback from log file?
Sorry , here is the attachment.
Here I have attached the log file, I am having trouble with VALIDATE_CONNECTIVITY & SPLIT_INTERSECTING_FEATURES methods.
Can you get us a log file?
I also tried this way before, still not working. This is how I config the rule.
You are mixing the subtypes and the rule config
FC|Subtypes in the Table Name field
Nodes in the Value info
NONCon|11 = Table Name
2 = Value Info
Validation - Attribute Assistant | ArcGIS Solutions
Thanks for your response, I am trying to use Validate connectivity rule for reducers & couplings which are subtypes of Non controllable fitting feature class. Where should I enter Valency or Nodes specific number? I try to use under Value info ,Table name & Field name none of them work. Any suggestions?
Example: NoncontrollableFtg_point|11 --11 represents reducer, reducer should have 2 nodes, under which column should I enter 2 number?
For subtypes, you need to use FeatureClass name only, remove the owner and database, then a pipe(|) and the list of subtypes. That will restrict the rule to process only on that subtype.
so in your example. Main_LINE|1,2,3
No one answer my previous question, hopefully I will get some help for this issue..... I try to set up some rules for dynamic table, except last value rule none of them are working. here I have attached the table , not sure what mistake I am doing . I would appreciate any help.
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
