Latest Contributions by MelindaMorang

@RussellProvost1 Were you able to get your scripts working, or do you still have an enhancement request or questions?  Thank you. ... View more

From the comments in this thread, I believe the original idea was based on an incomplete understanding of the analysis limits or confusion between two different solvers.  This thread hasn't had any activity in over two years, so I'm closing it.  Feel free to leave another comment if you feel that your idea or question has not been sufficiently addressed. ... View more

When you say "A new, complete build removes this error", do you mean that your network dataset was in an unbuilt state when you were using Explore Network initially?  Like maybe you edited the attributes or evaluators?  If that's the case, maybe the Explore Network tool was getting confused because of the change, and closing and reopening Pro refreshed some sort of cache.  Essentially, until the network is built, the changes to the attributes are not reflected on the internal, logical network that Explore Network reads, and the values might be incorrect. If the problem is still reproducible after the network has been built, then I would consider it a bug of some sort that we would want to investigate. ... View more

If you can share your data and the changes you made to the network dataset properties that reproduce the problem, we can take a look.  Alternatively, you can submit a ticket through Esri Support (or through your distributor), and we can look at it that way as well. ... View more

The Network Analyst extension deals exclusively with transportation networks, so I'm going to move your question to somewhere that the right people are more likely to see it.  I hope you find the answers you're looking for. ... View more

Are those grid lines the streets (edges) in your network?  If so, then it's likely that some of the points are being snapped to the street locations outside the 23km cutoff distance.  You an see where the selected streets extend beyond the edge of the service area. When you do a network analysis, the input points must be "located" on the network, meaning the closest non-restricted location on the network is found, and that location is used as the start and end point for the analysis.  Since it looks like your evenly spaced input points are much denser than the grid network, a lot of them will be snapped a fairly large distance to the closest location on the grid.  The snapping distance is not counted as part of the 23km cutoff.  Here is some documentation about the locating process: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/locating-analysis-inputs.htm ... View more

Assuming you have configured your PublicTransitTime cost attribute according to our tutorials and/or used our network dataset template, then solving using this cost attribute works as follows: the travel time along public transit edges in the network uses the transit schedules and models riding transit, and the travel time along street edges in the network uses walking time along those streets.  So, solving using PublicTransitTime is a complete solution to model a traveler who can take transit but must walk along streets to get from their initial location to transit stop, make transfers between stops, and get from the final transit stop to their destination.  You don't need to add anything else to the analysis to make it correctly model walking when not using transit. The WalkTime cost attribute is a completely separate cost attribute that is configured in our template primarily to support accumulation.  If you set this as an Accumulate Attribute, it will tell you how much travel time was walking because it returns the walk time value along streets and returns 0 for transit lines.  You can read about Accumulate Attributes in this documentation page for closest facility layers (it's a long page, so search for "Accumulate Cost Attributes".) ... View more

That second warning message tells you what's wrong.  You can click the warning link to see the documentation for that message, which should give more details.  But, basically, you need to check on the option to interpolate blank stop times.   ... View more

I can help you with this, but your screenshot of the error message has the detailed messages cut off.  Can you copy/paste the full list of errors?  One of those should give more details about what went wrong. ... View more

You could change your restriction's usage type to "Avoid High" instead of "Prohibited".  This will allow the biker to use the large roads if no other path is available.  Documentation: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/restriction-attributes.htm#GUID-E02CEE7B-7957-490F-BAD9-611FB50EB444 ... View more

The travel mode type doesn't really do a whole lot, but if you set it to Walking, it will use a smaller pixel size for your Service Areas and make the polygons a bit more detailed.  But it doesn't do anything to affect the actual analysis result. If your road is "major" but also has a bike lane, you should probably just make it not restricted.  Otherwise, bikes won't be able to ride there, which isn't your intention. Note that crossing major roads can still be a challenge/problem on a bike, so it may not be that inaccurate to show that the area across the street is inaccessible unless you have good infrastructure for crossings and left turns. ... View more

I'm having a little bit of trouble understanding exactly what your screenshot is showing, but here's a guess.  You said you set up some restrictions to prevent bike travel on major collectors, major arterial roads and interstates.  The locations where your facilities are located look like they are on larger roads.  Are those collectors?  It kind of looks like the facility is getting snapped to the closest non-restricted road segment (one of those side roads), and, since bikes aren't allowed on the main road, it can't cross the street and get into the neighborhood on the other side. One thing that might help you visualize what's going on is configuring the network dataset layer symbology to show the restriction status.  You can configure the edge symbology to show the edges that are restricted according to a specific travel mode.  Here is some documentation about network dataset  symbology: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/network-dataset-layer-symbology.htm ... View more

When you create a network dataset using the Create Network Dataset tool, you can choose which type of elevation model you want to use: No elevation, Z-level fields, and 3D Z coordinates.  If your data is 2D and does not have Z-level fields (FZLEV and TZLEV), then you would need to create the network using no elevation.  This will still produce a valid and usable network dataset.  You just may have some problems modeling overpasses and underpasses.  You will want to carefully check those to make sure they don't have endpoints or vertices (depending on your connectivity policy) to prevent them from connecting at those locations (so the driver can't turn left off a bridge and start driving on the road that goes under it, for example).  But as long as the roads don't meet at an endpoint/vertex at the location where they cross, it should still work just fine. Here's some documentation that should help: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm ... View more

I see.  That makes sense.  Unfortunately, our tools just aren't set up very well for this type of application because we don't emphasize the passenger-facing experience.  The geometry just isn't going to look pretty without quite a lot of effort on your part. The other problem you will likely encounter is that the transit travel time and best route may vary substantially throughout the day depending on the start time because the available transit service changes.  You would need to account for this somehow, but it's a tough problem to solve.  Some of the tools available for download described in https://github.com/Esri/public-transit-tools/blob/master/transit-network-analysis-tools/UsersGuide.md help to summarize results over a time window, although I'm not sure how well it will work for your needs since you ultimately want to give your tourists a simple recommendation. Sorry I can't be more helpful. ... View more