Latest Contributions by MelindaMorang

This code sample or product no longer exists. ... View more

I believe this is often referred to as "rubber banding." Those of you interested in this feature, could you clarify what platform or product you want this in?  What ArcGIS product are you using during your public meetings, and what are your on-the-ground technicians using where they want this behavior to happen? Incidentally, this behavior is already possible if you create an application using the Javascript API. ... View more

Network Analyst fundamentally requires a point as the starting and ending location for an analysis. There simply is not a way to use a polygon without representing it somehow as a point (or multiple points). The trick is to select your representative points in a clever way. You've already noted that the centroid isn't a good representation. That's definitely true for larger polygons, or irregularly-shaped ones. You could choose points representing park entrances. You could chose points where nearby streets meet the park boundaries. You could choose polygon vertices.  You could space points every X meters along the park's boundary. If you choose to represent the polygon with more than one point, you can combine the resulting Service Area polygons into a single feature by choosing the Merge option. This way the result gives you a single polygon that represents the area reachable within a time or distance limit from the park. ... View more

Hello Michael. Were you able to get your work done using the information and suggestions provided by my colleagues above? If so, I will close this Idea. ... View more

I think the feature you're requesting is a "tour" route, to show possible places that can be visited within a given time or distance limit. This is not possible with the tools currently available in Network Analyst, as the algorithms we use for all solvers focus on optimizing the path taken (shortest path problems). The tour problem is fundamentally different and would require implementing a new solver. This is not currently in our product plan. ... View more

We believe the behavior is already implemented the way this user wants, and they offered no further clarification. ... View more

Hello David. You should be able to model this behavior already using the Turn category evaluator.  This special evaluator allows you to configure a global turn delay for all maneuvers of a specific type, such as a U-turn (or a left or right turn, etc.).  If your network has a hierarchy attribute, you can configure a different amount of delay time for transitions between different road classes, which would correspond to your request about speed limits.  You may not be able to explicitly restrict u-turns for certain road classes, but you could enter an extremely large turn delay in order to make them effectively restricted. To set up a Turn category evaluator in your network, Open the network dataset properties Go to the Travel Attributes page, Costs tab Select the cost attribute you want to use in your analysis in the upper half of the page In the bottom half of the page, scroll down to the Evaluators section Find the Turns heading and the row labeled <Default> Use the drop-down to select Turn Category for the evaluator type. In the Value column on the right, double-click the cell to activate the configuration button. Click the button to launch the Turn category evaluator dialog and configure the settings the way you want them. Please let me know if this doesn't serve your needs. ... View more

Your question is somewhat different than the original question, but that's okay. In order for edges to connect in a network dataset, the points of intersection must either have an endpoint or a vertex (or, if your Connectivity Policy is "End Point," you must have endpoints and not vertices).  If you have neither, the network will never connect the edges at points of intersection. Please read the documentation about connectivity in a network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm The easiest way to create vertices at all points of intersection is to run the Integrate geoprocessing tool using a 0 XY tolerance.  Make sure to use the 0 XY tolerance so none of your features get moved, and you might want to make a backup copy of your data first because this tool does modify the input data in an irreversible way. The  Integrate tool creates vertices at the points of intersection, so you can use an Any Vertex connectivity policy, and things should work well. ... View more

No, there's no explicit way to do that. You could potentially edit your data and assign a different line ID to the section you want to turn off. You would have to very carefully read and understand the Public Transit Data Model documentation to make sure you've propagated those changes through all the related tables. And you still have to remember that the service downstream of the part your turning off will still run on the same schedule as before. Another option: Don't put barriers on the transit lines, but put them on all the StopConnectors features that allow passengers to access the transit line. This would work to eliminate all access on and off the line for the section you want to turn off, although passengers already traveling on the line would still be able to go through. You could put a single barrier on the transit line at the start of the closed section, I guess. You would still have to account for downstream affects. ... View more

This was implemented as part of ArcGIS Pro 2.9 and 10.9.1 Enterprise, and the 9.4  release of the ArcGIS Online services in December 2021. With this enhancement, straight-line distance checks for multiroute inputs are done per route instead of for the entire stops dataset. ... View more

Okay, I understand your point about it being difficult to tell which tool history item is which. If you have an idea about how this could be made less confusing, I suggest you post a fresh Idea, but frame it as a generic Geoprocessing request. It would have to be addressed at that broader level, rather than anything specific to a given tool. (In other words, this Idea got my attention because the request is specific to a tool I own, but ultimately a different team would have to evaluate and address it at a level that affects all tools.) Regarding the Network Analyst Ready-to-Use tool deprecation: Yes, once Pro 3.0 is released, there will be some documentation and further information about this. Essentially, these tools were ported over from ArcMap at the very beginning of ArcGIS Pro, but they represent an older way of interacting with the ArcGIS Online Services that we no longer wish to support.  You may notice, for instance, that the tools have a million input parameters, and some of these, like restrictions and impedance attribute, are wrapped up in the concept of travel modes, which were invented later. Users also frequently experience confusion over the fact that these tools always hit the ArcGIS Online services even if the user's active portal is set to an Enterprise portal, and they accidentally burn credits. Long story short, these tools are no longer the way we want users to interact with services. The preferred method is to do your network analysis workflows the same as you do with local data: Create a network analysis layer (referencing the service), Add Locations, and Solve, all using a standard network analysis layer in the map. These layer-based workflows work seamlessly with services, and we hope they are easy to use. If you're not familiar with this procedure, please check out this tutorial, which will run just the same with either the tutorial network dataset or a service. As far as comparing one analysis with another, Pro 3.0 will also include a new tool for copying a network analysis layer, which will make it easier for you to set up a layer with the settings you want, duplicate it, and then add different data to each one. You can run both analyses and compare the results. ... View more

Sorry, should have marked this as "Already Offered". ... View more