|
POST
|
Hi Austen, I am sorry to hear of the challenges you are running into. You are correct that the SOURCEID/FEATUREGLOBALID are not required for trace locations coming from a user defined feature class. When these fields are absent from the schema, the geometry of the input feature class is used to intersect the geometry of the network feature and place the starting points. The team addressed issues related to trace locations placed on junction features in the 2.7 release. It sounds as though the issues you are seeing are specific to Shortest Path traces alone? Is that correct or are you seeing this with other trace types as well? One issue that we were unable to get into 2.7 related to placement of starting points on junction features when performing a shortest path trace. If this is encountered only with Shortest Path traces you may be encountering this behavior; however, in that scenario populating FEATUREGLOBALID enabled you to work around that limitation. One additional scenario that could trigger 002512 is when more (or less) than 2 trace locations exist. To confirm, I reproduced this again with a 2.7 client before testing with a recent 2.8 build where I was no longer able to reproduce the issue. Can you confirm whether creating a new junction feature class and populating this with the GLOBALID of the source network feature allows you to run the trace? It is possible I am missing a component of your workflow. One other potential. am not sure if this would be feasible based on the length of your edge features in the network; however, one potential solution in the interim would be to place the user-defined starting points along an edge. Thanks, Jon
... View more
01-27-2021
01:34 PM
|
0
|
2
|
3885
|
|
POST
|
@JohnGaiot It is possible to have multiple trace networks in the same feature dataset as long as the participating feature classes aren't the same; however, this appears to be a defect. I apologize for the inconvenience. We have been able to reproduce and have created an internal issue to be addressed. You can track this as BUG-000136866.
... View more
01-20-2021
06:23 AM
|
1
|
2
|
4157
|
|
POST
|
You should see errors with errortype = 1 with a message of: "The geometry for the network feature is empty." if these are preset in your UN. I tested a similar case on my end and was unable to reproduce this behavior. I found that I was able to successfully upgrade a UN dataset from v3 to v4 on 2.6.3 with empty geometry records in one of my network classes. I would recommend reaching out to Support to get a new case created. This may be data specific and Support would be able to help identify the issue for resolution or provide us with a reproducible case for further review. Thanks, Jon
... View more
01-11-2021
09:32 AM
|
1
|
1
|
2378
|
|
POST
|
@geonexusjames I am going to look into this issue you reference with upgrade dataset. You can identify empty geometry within the UN by reviewing the point errors table. Features with empty geometry will generate an error with the ID =1 when the network topology is enabled. These can also be visualized at the lower left-hand corner of the UN's Service Territory. Once identified, you should then be able to use the Origin Network Source ID and Origin Global ID to identify the class and record that caused the error.
... View more
01-11-2021
08:04 AM
|
3
|
3
|
2381
|
|
POST
|
"The issue that I could still use help with, is getting the downstream WRProxyMZ point selected when the starting flag is in the middle of an edge upstream from the WRProxyMZ point. See the first screenshot in the OP. Basically, I'm trying to get the orange point labeled 1378 to be selected in a downstream trace using the green circle, which is partway up the upstream edge, as the starting point. When you set up a trace like that in the first post, do you get point 1378 selected?" @TimWhiteaker This behavior is one of the items that I've brought to the team for review. As a workaround, the WRProxyMZ junction will be selected in the trace result if you place the barriers interactively using the Trace Locations pane.
... View more
12-17-2020
10:24 AM
|
1
|
0
|
3070
|
|
POST
|
With the release of ArcGIS Pro 2.7, a new capability called Trace Configurations is available for use with the trace network. This video on the topic was recently published with a focus on the ArcGIS Utility Network; however, wanted to share here as the same concepts and tools apply when working with the trace network as well. Learn more about how to use trace configurations in a trace network
... View more
12-16-2020
02:00 PM
|
0
|
1
|
2006
|
|
POST
|
Hi there Tim, I walked through your scenario and I am seeing the same. Sorry for the inconvenience caused by this. I am going to bring this back to the team for review.
... View more
12-16-2020
01:44 PM
|
0
|
0
|
1082
|
|
POST
|
Good morning Chris, Would you be able to provide sample data displaying the issue to review?
... View more
12-07-2020
08:41 AM
|
0
|
0
|
835
|
|
POST
|
Good morning Tim, Selections sets are not honored on the class used as the input for either the Starting points or Barriers parameter in the Trace tool. The best approach would be to create a layer file from the selection and use this as the input. This is briefly discussed here in the web help.
... View more
12-07-2020
08:26 AM
|
0
|
0
|
1117
|
|
POST
|
Copying this from a reply in another thread to clarify when SOURECEID and FEATUREGLOBALID fields are used when working with starting points and barriers in a trace network trace. When placing starting points and barriers in a trace network, the SOURCEID / FEATUREGLOBALID are not required; however, these fields are honored if present and require the inclusion of valid values to be used. Using SOURCEID and FEATUREGLOBALID to specify trace locations in a feature class allows you to filter which features are used as trace locations. Perhaps you have a feature class that contains features you want to use as barriers; however, you only want a certain type of feature, or specific set of features to serve as barriers... In this case you could populate only the features you want to serve as barriers with SOURCEID/FEATUREGLOBALID information. When the trace is executed, only these features would be used as either the starting point or barrier for the class. To clarify, case, if your class has 20 records, but only 2 have SOURCEID/FEATUREGLOBALID populated with a valid value, only those 2 would be used as starting points or barriers in the trace. If these fields are not present, the geometry of the feature class will be used to intersect the network feature geometry and place either the starting point or barrier. user-defined feature class used as a barrier feature without SOURCEID/FEATUREGLOBALID This is outlined here: https://pro.arcgis.com/en/pro-app/help/data/trace-network/starting-points.htm https://pro.arcgis.com/en/pro-app/help/data/trace-network/barriers.htm If this does not address the original use case above please reach out with additional details and I can review further.
... View more
12-07-2020
08:08 AM
|
0
|
0
|
1769
|
|
POST
|
Thank you again for the clear use case and data. With your use case we were able to identify another issue and have implemented a fix related to placement of starting points in 2.7. Another issue has been created to include barrier features in the trace result when using a network junction feature class as you were doing in your initial note. As you noted with case "a", interactive placement of trace locations using the Trace Locations pane will allow you to place starting points or barriers on an edge or junction feature. This is the default method for placing trace locations For case "b" below, I am curious if the edge element selected is upstream or downstream of the junction feature that is not selected. If you were to interactively place a starting point at the endpoint of a line from a small scale this could inadvertently place barriers on both adjacent endpoints which could explain why the junction feature is not included in the result set. I d id notice in my testing that if I am zoomed out a bit, a barrier was placed on both the upstream and downstream edge surrounding the junction. Alternatively, you could be placing the barrier on the endpoint of the edge upstream of the junction feature alone. Testing on my end using 2.6.3 shows that if the barrier is placed on the endpoint of the edge downstream from the junction, the junction is included in the result. Juncitoin feature included in trace result Barrier interactively placed on endpoint of edge downstream of the junction feature Regarding your question about the need for SOURCEID / FEATUREGLOBALID fields when placing trace locations. We have an open issue to address some issues that are encountered when using network features (such as WRProxyMZ) as barriers in a trace. While these are honored as barrier features, there may be inconsistencies including these in the trace result as you have noticed. The alternative solution for this is case "a" as you noted above. Another approach would be use to another user defined class for the trace locations. When placing starting points and barriers in a trace network, the SOURCEID / FEATUREGLOBALID are not required; however, these are honored if present. Using to determine trace locations allows you to filter which features are used as trace locations. Perhaps you have a feature class that contains features you want to use as barriers; however, you only want a certain type of feature, or specific features to serve as barriers... In this case you could populate only the features you want to serve as barriers with SOURCEID/FEATUREGLOBALID information. When the trace is executed, only these features would be used as either the starting point or barrier from the class. To clarify, case, if your class has 20 records, but only 2 have SOURCEID/FEATUREGLOBALID populated with a valid value, only those 2 would be used as starting points or barriers in the trace. If these fields are not present, the geometry of the feature class will be used to intersect the network feature geometry and place either the starting point or barrier. user-defined feature class used as a barrier feature This is outlined here: https://pro.arcgis.com/en/pro-app/help/data/trace-network/starting-points.htm https://pro.arcgis.com/en/pro-app/help/data/trace-network/barriers.htm Thanks, Jon
... View more
12-07-2020
07:55 AM
|
0
|
1
|
3096
|
|
POST
|
Good morning Tim, I wanted you to know that I was taking a look at the use case you outlined above. I agree that the behavior appears strange. Could you let me know which version of ArcGIS Pro 2.6 you are working with? Is this 2.6.0 or do you also have a patch applied? (2.6.3 for example). I'll reach back out once I've had an opportunity to dig in a bit more.
... View more
12-02-2020
10:36 AM
|
0
|
4
|
3108
|
|
POST
|
John Gaiot A new result type option (Network Layers) will be available in the 2.7 release to provide this type of functionality. With this result type option selected, a new group layer will be created with a name you provide. The group layer will contain a collection of sub-layers (feature layers) corresponding to network sources belonging to the trace network with trace results. The actual trace results are selected in each of these sub-layers and only layers that have trace results in them are added to the output group layer. This should enable you to access information about the network features returned in the trace for use in other tools for iterative scripting.
... View more
11-03-2020
11:34 AM
|
1
|
1
|
2913
|
|
POST
|
Hi Robert Thomson I sent a message which should be visible in your inbox to the left of your profile badge at the top of the screen. I'd like to review your data if possible. Could you reach out to me at - jderose at esri.com?
... View more
09-15-2020
09:16 AM
|
0
|
0
|
2990
|
|
POST
|
Hi Robert Thomson I've reached out via direct message to discuss a review of the scenario in more detail to see if we can get to the bottom of what might be going on.
... View more
09-08-2020
09:10 AM
|
0
|
2
|
2990
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-12-2025 01:04 PM | |
| 2 | 06-24-2025 08:00 AM | |
| 1 | 10-14-2024 01:14 PM | |
| 1 | 08-29-2024 09:07 AM | |
| 1 | 06-18-2024 12:48 PM |
| Online Status |
Offline
|
| Date Last Visited |
a month ago
|