Latest Contributions by MelindaMorang

Unfortunately it is not possible to use that tool with a service. ... View more

Yes. You can use the Copy Traversed Source Features tool for this. ... View more

Are you trying to calculate the optimal path from villages to urban centres using a road network? If so, Network Analyst is the right tool for that job. However, you need a road network, not a DEM. Here is a tutorial to get you started: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/od-cost-matrix-tutorial.htm But since you mentioned a DEM, does that mean you actually want the least-cost path through the DEM, like a watershed analysis? If so, this is not the correct forum. You should ask your question in the Spatial Analyst forum: https://community.esri.com/t5/arcgis-spatial-analyst-questions/bd-p/arcgis-spatial-analyst-questions ... View more

When you create and build a network dataset, the build process automatically generates a feature class of "system junctions". These are point features representing locations in the network where edges intersect. You should not edit or remove or interact with this auto-generated feature class. It's just there so everything else will work right. In your old shapefile network, la_streets_clip_UTM_ND_Junctions is probably the auto-generated system junctions. Don't bother exporting that or using it to create your new network. Just leave it out. Then, when you run Build Network to build your new network, it will auto-generate a fresh system junctions feature class. This is the expected, correct behavior. ... View more

That's correct. Feature Class To Feature Class and Copy Features do not work with network datasets. There is no way to convert or export a shapefile network dataset. You have to recreate it from scratch in a file geodatabase.  Here is the procedure: Create a new file geodatabase Create a new feature dataset within the file geodatabase in the spatial reference you want (you can even import the spatial reference from the shapefile to make sure it's the same) Run Feature Class To Feature Class or Copy Features to export the la_streets_clip_UTM.shp shapefile (which has the streets data) to a new feature class in the feature dataset. Use the Create Network Dataset tool to create a new network dataset in the feature dataset using that new street feature class as a source Manually configure all the network dataset properties to match the properties of the original shapefile network dataset. Depending on how complex your shapefile network is, this may take some work. I'm sorry there isn't an easier way. Run the Build Network tool to finalize the network. Address any build errors if needed, then test and validate your network. ... View more

You are in the right place to get help with this problem. The issue is that shapefile networks just aren't well supported with newer functionality.   Here is a tutorial that shows you how to create a file geodatabase network dataset in Pro: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/how-to-create-a-usable-network-dataset.htm You may be able to use the street data from your shapefile network dataset if you copy the shapefile into a file geodatabase feature dataset. Try using Feature class To Feature Class or Copy Features. ... View more

Can you give some further details about your workflow? That error is unexpected, but there's not really enough information here for me to help you figure out what went wrong. ... View more

I'm happy to help you with this. My guess is your issue is one of the following: Connectivity policy - did you get the connectivity policy right? Also, did you use the connectivity policy (Any Vertex/Endpoint) that makes sense for your streets? Did you get your analysis settings right? Are you using a specific date or a weekday that makes sense for the data you have? Are you using a time of day when there is transit service? Is the walk time along your streets being calculated correctly? If, for example, the walk time for all streets is accidentally 0 or very tiny, then the network will never use the transit lines because they will always be suboptimal compared to using the streets. If none of those suggestions help you resolve the issue, I can take a look at your network if you can share it, or you could post some screenshots of your settings. FYI, no special Directions settings can be configured for transit lines. Our Directions engine does not yet support transit directions. ... View more

That definitely seems too long. It's possible that there could be an issue with the locations of the stops or with your network dataset, or the relationship between the two. The tool uses the Network Analyst Route solver, and that solver will try to find a path through the network from each stop to the next stop in the sequence. If something is wrong with the network or the stop locations, it's possible that it could be searching the entire network dataset trying to find a path. If the network is large (like all of Europe, for example), that could take a really long time.  Have you tested or used this network dataset outside of this tool? If not, that's my next recommended step. Run some standard Network Analyst workflows to make sure it's working properly. If you find out there's something wrong with the network, I can probably give you some tips on how to fix it. However, I cannot provide any more detailed help with the Generate GTFS Shapes tool because it is deprecated and no longer supported. You should switch to ArcGIS Pro and use the tools there. They are more thoroughly tested, probably run faster, and you can get full tech support on them. ... View more

If you are using your own data to define junctions, then the automatically generated SystemJunctions feature class could be empty. This is because your own junctions adequately serve the purpose, so the software doesn't need to automatically create any. The SystemJunctions feature class will still be created, however. ... View more

The values for route_type in your data above are 712, 701, and 704. Those do not correspond to any of the official GTFS route_type enum values, which are 0-7, 11, and 12. (See https://github.com/google/transit/blob/master/gtfs/spec/en/reference.md#routestxt) If you want to use the network to generate shapes for these modes, you need to configure the checkboxes in the UI like this because all these modes fall into the "Other / Type not specified" category. (Note that this tool has not been updated since route_type 11 and 12 were added to the specification, so currently those supported types also fall into the "Other / Type not specified" category. Please note that this downloadable version of Generate GTFS Shapes is now deprecated. I will not be making further updates and cannot provide extensive tech support.  To create a shapes.txt file for your GTFS dataset in ArcGIS Pro 2.6 and higher, please use the Generate Shapes Feature From GTFS and Features To GTFS Shapes tools. The new core tool in Pro has essentially the same behavior for unrecognized modes. You can select the "Other transit mode" box to use the network to generate shapes for all modes not recognized by the GTFS specification.   ... View more

Regarding directions text: No, there is not currently any way to get further details in your directions. We have not updated the directions engine to report any details about the public transit service used. There are technical reasons for this. The main one is that although the Public Transit evaluator internally has access to the route and trip IDs that were used, an evaluator cannot return this information to the directions engine. It can only return the travel time. Updating evaluators to return additional information would be a major surgery in our network data model and associated code, and this is not work we have prioritized yet. Our public transit capabilities are intended for analysis, not for passenger-facing apps where directions should be used. Regarding the TotalWait_ and TotalViolation_: These fields do not mean what you think they mean. They do not relate to the time a passenger would wait for a bus, for example. Rather, these are standard Route output fields that are only populated when using time windows. Please read this documentation for a description of what these fields mean.   Regarding limiting transfers: There is currently no way to do this, although it's something I know is really important! My team was recently brainstorming some enhancements that could potentially make this possible, but we do not currently have any solid plans to implement anything. ... View more