Latest Contributions by MelindaMorang

‎03-09-2021

Hello Stephane. Could you please provide further detail about the problem you're experiencing. In particular, what is "the road tool with the ESRI Network in PRO"?

‎03-03-2021

You could start with Esri Support: https://support.esri.com/en However, from what I understand, Support usually answers simple questions, provides basic guidance, and investigates potential bugs. It sounds like you're looking for someone to help you in detail. That might be more like a Professional Services engagement if you have the budget for it. https://www.esri.com/en-us/arcgis/services/consulting

‎03-03-2021

Yes, this is feasible but challenging. I do not have any magical suggestions on how to do it successfully. You need to somehow calculate the slope for each street feature in your network's source feature class based on the DEM. This can be tricky because you could potentially have a street segment that goes down and back up a huge hill, and the average slope is 0. Anyway, assuming you have calculated the slope in a way you're happy with, you can use the slope field in your source feature class to calculate a cost attribute using the slope value. Or perhaps you could make a descriptor for slope and calculate the cost as a function of the descriptor and some constant or parameter. Sorry, this is a very vague answer. Your problem has become quite complex, and it's reaching the limit of what I'm able to advise upon here on Geonet.

‎03-02-2021

No, the Create Network Dataset tool creates a network dataset, which is a specific type of object. That is the only output of the Create Network Dataset tool. The network dataset contains a set of properties you can configure, and internally it tracks edges, junctions, and turns. However, these edges, junctions, and turns are drawn from separate feature classes. You can specify your own junctions if you have them, but if you don't, when you run Build Network, it will automatically generate junctions at locations where the network edges are connected to each other.

‎03-02-2021

Okay. I think I understand where the confusion is coming from. The Create Network Dataset tool just creates the network dataset with some default properties and using the data you provide as sources. The network dataset isn't ready to use at this point. You need to update any of the properties (like adding restrictions or configuring Directions or whatever), and then you need to run the Build Network tool. Build Network takes all the input data and all the properties and cooks it all together into a usable network dataset. At this point, it will auto-generate junctions at the points where edges are connected to each other.

‎03-01-2021

Hi. Can you provide some more details about your workflow? Are you using the Create Network Dataset tool, or are you doing some other procedure? Please describe. When you say "The process will run and will create a Edge for ND, but the Junction attributes has no information, No Junctions were created in the process.", what "process" are you referring to? Do you mean you ran the Build Network tool, and it didn't create any junctions? Or something else?

‎02-26-2021

For Question 1, I think you can probably use the Copy Traversed Source Features tool. For a Route or Closest Facility layer, this tool will output a copy of the network edges, junctions, and turns that were traversed by the route. You can look for duplicate SourceOID field values to identify streets that are used by more than one route. For Question 2: I think Copy Traversed Source Features can help you with that, too. You will just have to eliminate duplicated segments and then count the length of what's left. For Question 3: I think that's correct, but I am going to ask a colleague to look at this post to confirm.

‎02-25-2021

If you followed the steps in the tutorial and used the provided network dataset template, it should have created impedance attributes called Public Transit Time, Walking Time, and Length. I don't know why it wouldn't do that. That seems weird. You can certainly configure those attributes yourself according to the needs of your analysis. You need to select "Public Transit" as the evaluator type for the LineVariantElements source. You also need to configure a walk time calculation for the Streets source. If you need help with that, the best thing to do is contact Esri Support. they can figure out either a) why the tutorial steps didn't work for you or b) help you figure out how to configure your cost attributes correctly if you're setting things up manually. https://support.esri.com/en

‎02-23-2021

You probably ran into some bug from an old version of Display GTFS Route Shapes that was fixed at some point. That tool is now deprecated anyway. For future readers of this post: Use the GTFS Shapes To Features tool available in core ArcGIS Pro if you want the same functionality.

‎02-22-2021

Hello Patrick. I looked at your network, and I think I know what the problem is. The WalkTime cost attribute included in the network by default (created from the provided template) is not really meant to be used to model walking only. I realize this is a bit misleading. Essentially it is there to help create a reasonable walk time estimate for use in the transit calculations and so you can accumulate the total walking time used in your transit journeys. For this reason, it calculates the walk time along transit lines (LineVariantElements) and StopConnectors as 0. If you use the WalkTime cost attribute directly, it sees the transit lines as free to use, so your routes will be all weird. If you want to use this network to model walking, you can do one of two things. 1) Cheat. Use your transit travel mode, but just don't set a time of day. The transit lines will never have any service and will be effectively restricted, and so all calculations will default back to walking. 2) Continue along the route you're currently on, but fix your walking travel mode. The easiest thing is to create a restriction attribute that makes LineVariantElements and StopConnectors restricted all the time and make sure this restriction is turned on for your Walking travel mode.

‎02-19-2021

Hello. There doesn't seem to be anything wrong with your LineVariantElements. The GTFS To Network Dataset Transit Sources tool generates a straight line between each pair of connected transit stops. If your system doesn't have long-haul commuter routes from the suburbs to downtown, for example, you won't get long spiky lines. Instead, you'll just get a straight line that goes for a few blocks between stops. If you zoom in close, I'm sure you'll see that the lines do not actually follow all the curves in the streets and are probably offset from the street centerlines. Whatever problem you're experiencing likely comes after this point, but I cannot quite tell from your description what's really going on. If you're following the tutorial, you should have been able to create your network dataset from the provided template. Did that work? If so, that should have automatically created the network dataset with an impedance attribute that uses the "Public Transit" evaluator for LineVariantElements, and thus uses the public transit schedules for calculating travel times. Please describe further the problem you're experiencing, and I'll do my best to help you sort it out.

‎02-17-2021

To map the frequency of public transit service, you can use the Count Trips on Lines tool in the BetterBusBuffers toolbox: http://esri.github.io/public-transit-tools/BetterBusBuffers.html However, this tool will not map the frequency of bus service on the streets. The lines produced by the tool are simple straight lines connecting adjacent stops. I have not found a good way to match these lines to the underlying street features, unfortunately.

‎02-13-2021

Did you ever find a solution to this problem? Another user reported a similar issue to me, and I still cannot reproduce it.

‎02-13-2021

Hello June. It looks like Digital Transport For Africa made a copy of my GitHub repo a long time ago. I don't recommend using anything you find there. First of all, this is the authoritative version of the Add GTFS to a Network Dataset toolbox is here: http://esri.github.io/public-transit-tools/AddGTFStoaNetworkDataset.html. Note that this toolbox is now deprecated anyway, even if you get the latest version. I no longer recommend that people use this, and I do not provide extensive tech support anymore for it. Second, that toolbox does not work in ArcGIS Pro. If you want to do analysis with public transit data in ArcGIS Pro, you do not need any additional, downloadable tools. The functionality is now available out of the box. Learn more here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/network-analysis-with-public-transit-data.htm The best way to get started is to follow this tutorial: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/create-and-use-a-network-dataset-with-public-transit-data.htm Note that the tutorial includes some data and a network dataset template as well, but it's designed specifically to work for ArcGIS Pro. Hope this clarifies things!

‎02-12-2021

So far I have not been able to reproduce the original problem. Question: When you did the “Connect the transit stops to the streets” part of the tutorial, for Input Streets Features parameter in the tool, did you select the Streets feature class in the target feature dataset? Or did you accidentally select the one in the original location?

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by MelindaMorang

Re: Route tool for walking distance

Re: Use of "Location Allocation" option to determine locations of a Wastewater treatment plants

Re: Use of "Location Allocation" option to determine locations of a Wastewater treatment plants

Re: Creating Network Dataset in ArcGis Pro. Junction fail to be created with edge.

Re: Creating Network Dataset in ArcGis Pro. Junction fail to be created with edge.

Re: Creating Network Dataset in ArcGis Pro. Junction fail to be created with edge.

Re: Use of "Location Allocation" option to determine locations of a Wastewater treatment plants

Re: GTFS to Network Dataset Transit Sources tool - LineVariantElements feature continues to follow the streets

Re: Display GTFS Route Shapes generates incomplete shapes

Re: transit network dataset modified to include walking; walking results erroneous

Re: GTFS to Network Dataset Transit Sources tool - LineVariantElements feature continues to follow the streets

Re: GTFS error

Re: Calculate Accessibility Matrix Error

Re: Create Network Dataset From Template

Re: GTFS Network Dataset never uses transit options... again

Re: TransitNetwork for multimodal analysis?

Re: Network analyst public transit tool Prepare ti...

Re: Network analyst public transit tool Prepare ti...

Re: How do I fill in the blank areas where streets...

Re: Route Solver - Add Locations - Convert Model B...