Latest Contributions by melisahansen

Thanks for the response! This does not work very well for us. The trace option is kind of clunky for us and does not trace all lines that are connected each segment would need to be traced separately, and this isn't effective. Do you know if there are plans in the future to bring back the option to load from sketch?

@JDOverton We are currently in 3.1. Basically, we could select an existing parcel, click edit vertices, and in the GOGO window, load it as a sketch. This would populate the bearings and distances of the existing feature. This is not an option we have found in Pro. Currently in Pro, we would have to COGO the entire parcel from scratch, where previously I could just edit the traverses imported.

@AmirBar-Maor our organization also uses the Load traverse from Sketch as it makes our workflows much faster. We are not actively using parcel fabric and do not have plans to just yet. As anonymous user stated, being able to bring in an existing parcel to the traverse tool, is much faster when editing existing parcels. Currently in Pro, I would have to COGO the entire parcel from scratch, where previously I could just edit the traverses imported. ArcMap, was more flexible and efficient to our workflows. Are there plans to bring this option into Pro?

@J_D_Overton is there no longer the option to Load Traverse from Sketch? This was an important part of our workflow that has seemed to go away.

‎07-15-2024

@Robert_LeClair has this enhancement request been completed? We still can't see data created via python script unless we manually refresh a version.

‎04-02-2024

Hi @MelindaMorang This issue is not unique to ArcMap, we have tested in both ArcMap and Pro, created networks in both and tested in both, and the issue is the same. As shown in the image below, it calls the 2nd exit the 3rd. Based on the logic we are seeing the only roundabouts that would produce the correct directions would be traffic circles with one single segment for entry/exit as shown in figure 2 below. We will submit a ticket in hopes of a resolution. Figure 1. Incorrect directions on roundabouts with divvied entry/exit. Figure 2. Directions function properly in this configuration but does not reflect the layout of most traffic circles.

‎04-02-2024

@MelindaMorang, doing what you stated, does not solve this issue. Please see examples below where I added in a segment between exit 1 and 2. Now, it recognizes exit 2, but now if it were to go around the circle back to the original location, it would then call it exit 4. This issue just compounds as you add in breaks. Even if you add a break in one location it doesn't fix the directions for all exits. Figure 1. Segment added. This corrects the directions for exit 2, however it extends the issue to the following exits. Figure 2. Same issue, now moved to what is now exit 3 on this route. This would be the same issue if there were another exit.

‎04-02-2024

Hello @MelindaMorang, thank you for the response! The picture in the 3rd example is what I would expect. The route in image 3 does not actually travers a segment classified as a roundabout. The issue is more with image 2. Image 2, the directions state to take the first exit because it only traverses 1 segment classified as a roundabout, however, it is clearly taking the second exit. This issue seems present no matter how a traffic circle is drawn due to the fact that the number of traversed segments classified as a roundabout will never be accurate for each exit (1st,2nd,3rd, etc.). Can you provide an example of the directions properly identifying each exit along a roundabout regardless of which exit the route starts?

‎04-01-2024

Hello, @MelindaMorang, do you have any suggestions for this issue?

‎02-22-2024

@DanPatterson this seems to be the issue for many people. If you look at the link I posted many people discuss the "current" keyword and how it does not work. It seems that when a tool is ran that creates data, the layer does not refresh, and you cannot see the data until you close and reopen the project.

‎02-21-2024

@DanPatterson Hi Dan, we are running a tool from a toolbox, the data/map does not refresh in ArcPro. In ArcMap these tools worked and you could see the data created by the tool, this is not the case in Pro. Previously we used: def RefreshMap (): mxd = arcpy.mapping.MapDocument('CURRENT') df = arcpy.mapping.ListDataFrames(mxd, "Layers") [0] df.zoomToSelectedFeatures() arcpy.RefreshActiveView() This does not work in Pro, and we have not found an equivalent option other than closing the project and reopening, which is not sufficient. And using the refresh at the bottom right of the screen also does not work. These are the same issues from the previous thread I shared. Thanks!

‎02-21-2024

There has been similar post in the past regarding being able to refresh the map after a python script has run, has there been any updates to this or is there still no solution. The thread below was from 2017, and I have not found a good solution still. There seems to be no resolution to the previous thread about this. ArcGIS Pro | ArcPy - How To Refresh the Map - Esri Community

‎02-21-2024

Has there been any updates to this?

‎02-20-2024

Hello everyone. I'm hoping someone has a suggestion for what seems to be a limitation during the process of configuring directions. Figure 1 below shows the 4 segments classified as a roundabout (5). As you can see in Figure 2 below, it says to take the first exit on the roundabout because the route only traverses one segment classified as a roundabout, but it's really the second exit. Similarly, in Figure 3 below, you can see it does not recognize the roundabout at all because it does not touch any of the segments classified as a roundabout. These issues are persistent between many roundabouts no matter how they are drawn. Does anyone have any recommendations? Thank you in advance! Figure 1. 4 segments classified as roundabouts. Figure 2. Directions stating to take the first exit on the roundabout. Figure 3. Directions not recognizing roundabout.

‎02-20-2024

@Robert_LeClair thanks for the suggestion. We ended up figuring out the issue, we were missing "Must not intersect or touch interior with". That catches the errors we were expecting to find. Thank you!

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by melisahansen

Re: Traverse in ArcGIS Pro

Re: Traverse in ArcGIS Pro

Re: Load Sketch into the Traverse tool without Parcel Fabric/COGO Enable for ArcGIS Pro

Re: Traverse in ArcGIS Pro

Re: How to refresh attribute table after editing data with Python script?

Re: Configuring Directions for Traffic Circles-Network analyst

Re: Configuring Directions for Traffic Circles-Network analyst

Re: Configuring Directions for Traffic Circles-Network analyst

Re: Configuring Directions for Traffic Circles-Network analyst

Re: Refresh Map after python script

Re: Refresh Map after python script

Refresh Map after python script

Re: ArcGIS Pro | ArcPy - How To Refresh the Map

Configuring Directions for Traffic Circles-Network analyst

Re: Topology rules not catching dangles

Refresh Map after python script

Loading Incidents/Facilities is very slow

Re: When developing a network with weight restrict...

Re: Address locator doesn't always work when using...