Latest Contributions by MelindaMorang

Hello Majid.  The accumulate attributes option is not currently available from the UI in Pro, but you CAN use it.  The easiest way is to use the Make OD Cost Matrix Analysis Layer tool to create your OD cost matrix layer rather than using the Network Analysis drop-down on the Analysis tab.  This tool has an option for accumulating attributes (note that this option is not available if you're using ArcGIS Online or a portal service as your network data source). You can also modify an existing layer's accumulate attributes using the solver properties object in the python window, like this: doc = arcpy.mp.ArcGISProject('current') mapObj = doc.listMaps()[0] layerObj = mapObj.listLayers('OD Cost Matrix')[0] props = arcpy.na.GetSolverProperties(layerObj) props.accumulators = [<list of attributes you want to accumulate>] ... View more

Actually, the easiest way is to run the Copy Traversed Source Features tool.  This will output feature classes that include the network edges, junctions, and turns that were used to make up the route. ... View more

Hello Jan. You do not need the geometry of your transit lines to match the OSM street geometry.  The Add GTFS to a Network Dataset toolbox will take care of this for you.  It will generate a feature class of transit lines which are simply straight-line connectors between stops.  The network dataset will reference these lines, but the travel times along those lines are calculated based on the GTFS schedules.  So the actual geometry of the lines is irrelevant. The only thing that DOES matter is the location of the stops.  It seems like this is where your real problem lies.  Add GTFS to a Network Dataset finds the locations of all the stops from the GTFS stops.txt file, snaps a copy of the stops to the closest street feature, and draws a connector line from the snapped stop to the original stop location.  This allows you to connect from the streets onto your transit lines.  If the snapped stops don't end up in the right place, then the network will not correctly represent the locations where people can get on and off the transit system. You can use the Edit GTFS Stop Locations tool to correct the locations of existing stops, export the correction back into GTFS, and then run Add GTFS to a Network Dataset using the corrected GTFS.  Another thing you can do is to add station entrances to your GTFS stops.txt file.  To do this, you would add a new entry to stops.txt and give it a location_type value of 2.  You would also have to have a parent_stations set up.  Read the GTFS reference for the explanation.  If you have your stops, parent stations, and station entrances set up correctly, the Add GTFS to a Network Dataset toolbox will take care of constructing the network dataset correctly using that information.  Also, adding station entrances does not affect the GTFS schedules, so you can add them without having to do any major surgery on your GTFS dataset. Hope this helps! ... View more

Hello Cayce.  I can't tell for sure without examining your data, but it looks to me like an issue with your network dataset.  The areas with the strange gaps look like unreachable bits of the network.  There are a couple of possible reasons for this: Those network edges are not properly connected to their neighbors.  Either the geometry is off (tiny gaps or overhangs), the elevation field values (z-levels) are incorrect so the network thinks the roads should connect to their neighbors, or the road and its neighbors don't meet at endpoints or vertices (depending on connectivity policy). These road segments are restricted because you have a restriction attribute that prevents travel on them.  This could be intentional, or the restriction attribute might be messed up.  For example, maybe you have a one-way restriction, but the one-way restriction is preventing travel in both directions on these roads. You can use the Network Identify tool, accessed from the Network Analyst toolbar, to click on your network dataset edges and see some information about them and which other edges they are connected to. Hope this helps you diagnose the problem! ... View more

Hello Victoria and Aaron.  We have fixed the ArcGIS Online Services.  Your Service Areas should be working again from ArcGIS Pro.  I'm very sorry for the trouble, and please let me know if you experience any further difficulties. ... View more

Hello, Nora.  The houses and supermarkets should not be included as part of your network dataset.  Instead, when you do a Closest Facility analysis, they will be added to the Closest Facility layer as "Incidents" and "Facilities".  The network dataset just models the transportation network itself, whereas the network analysis layer which references the network dataset can be set up to solve many different types of problems.  This way you can re-use the network for many different things.  It is not specific to answering one question. Here are some tutorials for the Closest Facility solver: - ArcMap: Exercise 4: Finding the closest fire stations—Help | ArcGIS Desktop  - ArcGIS Pro: Tutorial: Closest facility—ArcGIS Pro | ArcGIS Desktop  ... View more

If you use ArcGIS Pro, you can automatically re-create the network dataset from a template using the Create Template From Network Dataset and Create Network Dataset From Template tools. ... View more