|
POST
|
The utility network does not perform those calculations, but the utility network foundation data model contains all the necessary attribution to perform many different calculations like this (which is why the tables have few fields). You can either build your own tool to do this or look for an Esri business partner with a solution that can perform these calculations and integrate with the utility network.
... View more
10-28-2024
05:30 AM
|
0
|
0
|
1693
|
|
POST
|
This does not seem like the expected behavior, and I would log a case with support. If you recreate the rule to swap the from/to order of the lines so its from lateral to main via fitting, does it work?
... View more
10-25-2024
05:00 AM
|
0
|
0
|
1774
|
|
POST
|
I just tested this out locally, and in order to access the version URL you need to remove the curly braces. If I forget to remove the curly braces, then I get the error you see above. Another important thing to remember is that you can't undo or discard edits in default so you shouldn't need to start/stop editing. If you try to start editing in default you will get this error:
... View more
10-25-2024
04:56 AM
|
1
|
1
|
4984
|
|
POST
|
There are also geoprocessing tools that allow you to bulk export and add attachments, these tools do respect selected features (even when run standalone) so you'll use layers to manage which attachments to export.
You can also do this using the ArcGIS API for Python to individual download and add attachments between the two environments.
... View more
10-21-2024
01:28 PM
|
0
|
0
|
2268
|
|
POST
|
It sounds like you're using one of the earlier utility network foundations that used related records for wires, instead of non-spatial objects. While non-spatial objects are included in the JSON by default, since they participate in the subnetwork as content, if you need additional related data you will need to write a script or tool to query the database to get any important related records.
... View more
10-21-2024
01:21 PM
|
1
|
0
|
1353
|
|
POST
|
The tool updated the rows it found matches for, then inserted the rows it couldn't find matches for. Doing both an insert and an update is what the append tool does when you select the Matching fields options. This is why this is often referred to as doing an "Upsert" because the tool will first "Update" rows it matches, then "Insert" the rows it doesn't.
... View more
10-17-2024
12:01 PM
|
0
|
0
|
428
|
|
POST
|
If your source data uses subtypes you can ignore this parameter. This parameter allows customers to identify fields that can be used to help classify the features in their source data in a way that makes them easier to create mappings for. One example we use in the tutorial is the fitting layer defines all the different types of fittings using the fittingtype field. By putting that field in the source types parameter the tool will automatically look at the contents of that field in your source data and create separate mappings for each type of fitting in your data. This save you from having to manually create separate rows for your different types of fittings (end cap, coupling, etc).
... View more
10-17-2024
07:13 AM
|
1
|
3
|
2323
|
|
POST
|
Field names for the screenshot would be appreciated, so I'm going to have to make some assumptions. I'm going to call your first column a GUID, your second column and Object ID, and the third column a Global ID.
Global IDs are a special, unique identifier for a table, so your input dataset (the one with changes you want to push) needs to reference the Global ID of each row in the target dataset (the one being updated). So your input dataset should have a foreign key column the values from the Global ID (third column) of the target table. This will allow the append tool to know how to link the values from the two tables.
In your screenshot it looks like both tables have their own unique Global IDs, which means they'll never be able to match, which is why your rows are being appended and not updated..
... View more
10-17-2024
06:48 AM
|
0
|
1
|
2898
|
|
POST
|
Because Adding Rules uses the SDE connection, and requires an exclusive schema lock, you will need to stop any services connected to that database before you can add a rule. You will also need to make sure that there are no other connections to the database.
... View more
10-17-2024
06:35 AM
|
0
|
0
|
1412
|
|
POST
|
Double-check that the data type and formats of the input/target match fields are identical. As an example, if the field is a long in one database but a double in another this could cause an issue (this can happen with object id fields if you create them using views).
... View more
10-16-2024
12:20 PM
|
0
|
1
|
2917
|
|
POST
|
If you're just updating rows in the table every night global ids and object ids will be preserved because you're not deleting features every night.
... View more
10-15-2024
02:35 PM
|
0
|
1
|
2945
|
|
POST
|
Instead of deleting all the features every day, push inserts/updates/deletes to the layer. If you're only ever adding/updating values you can use the Append tool to do upserts by specifying a match key. If you need to handle deletes you can run the append then delete any rows that are no longer present in the source data.
Remember that when you edit a table that has archiving enabled that every edit is tracked in your database. This means that if you delete the contents and reinsert them every day, your database is recording all those edits. If your table is large, you should consider periodically trimming the table.
... View more
10-14-2024
08:16 AM
|
2
|
2
|
3024
|
|
POST
|
There is no one trace you can do to solve this problem; you will need to construct a workflow (outlined above) to help answer these questions. Because this is a very specific kind of analysis, I recommend you post your questions on the water resources community site: Water Resources - Esri Community
It sounds like you're trying to areas of the network where there are less than 5 features upstream from your starting location. You are not going to be able to do this with any kind of function or function barrier, since those can only calculate statistics or cause a trace to stop prematurely. If these culverts are connected to an outlet, then you would need to analyze all your outlets to find them. If these culverts are disjoint, then you could first need to run a disjoint analysis and identify all the island in your network to determine which ones meet your criteria. This is a very advanced analysis that will take time to develop and understand, which is why I suggest you reach out to the water resources community to see if someone has a model they can share with you.
Here is an article that discusses the trace framework more in-depth: Exploring the ArcGIS Utility Network Trace Framework (esri.com) . It was written about the UN, but most of the concepts in this article are shared between the TN and UN framework.
You can also find a presentation about the trace framework here: ArcGIS Utility Network: Advanced Network Management - Esri Videos: GIS, Events, ArcGIS Products & Industries
... View more
10-09-2024
11:23 AM
|
0
|
1
|
3821
|
|
POST
|
A function barrier determines the criteria for when the trace should stop. It is as you've described, you can stop tracing when you've traversed 10 features.
For what you're trying to do you'll need to either use selections or parse the JSON results to answer your questions. Brute forcing the problem will be quite slow (24 hours to analyze a network of 100k features), but with some clever tricks you can get the process down to being <30 minutes for a similarly sized dataset.
How much time you invest in creating a solution to the problem depends on how often you need to answer this question. Rhetorical question time: Is this a one-off thing you're doing now? or part of a larger analysis/quality assurance/regulatory requirement?
... View more
10-09-2024
10:34 AM
|
0
|
1
|
3826
|
|
POST
|
I would avoid using the word subnetwork to describe your situation with trace networks, because it is a very specific word used to describe a feature of utility networks so it will often lead others to believe you are using a stormwater utility network. If you were using a stormwater utility network, these situations would be easier to discover but you would also have to adopt that data model.
1 - A starting location can be placed on each point feature, or at any point along a line.
2 - Look at the schema of the starting points layer to answer this question. You'll need to uniquely identify the feature within the network, and if it is a line feature you will need to say what percentage along the length of the line to start at. You must pass in the trace locations layer, which has a very specific schema. The utility network has a GP tool call "Add Trace Locations" that makes this process easier, but unfortunately there is no corresponding tool for trace networks.
3 - I wrote an article about extracting JSON files using trace and parsing JSON files for the utility network. It's not a 1:1 for trace networks, but many of the same concepts apply. The parsing article includes some code samples to get you started (for the utility network), but again you should be able to adapt them.
The community site is usually the best place to have these discussions, if we get too far off-topic we can create a new thread.
... View more
10-09-2024
09:47 AM
|
0
|
1
|
3846
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | 03-30-2026 07:24 AM | |
| 1 | yesterday | |
| 1 | Thursday | |
| 1 | Thursday |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|