Latest Contributions by MelindaMorang

In case this topic is still relevant to you, I wanted to share that with the ArcGIS Pro 3.4 release, you can now create a new Public Transit Data Model feature class, LVEShapes, to store the pretty on-street transit route shapes for visualization instead of just the straight-line stop connections in the LineVariantElements feature class.  You can create an LVEShapes feature class from a GTFS shapes.txt file when running the GTFS To Public Transit Data Model tool. Once you have a transit-enabled network dataset that includes LVEShapes, you can solve a Route or Closest Facility analysis and use a new downloadable prototype tool, Replace Route Geometry With LVEShapes, to post-process the output routes to swap the geometry derived from LineVariantElements with geometry derived from LVEShapes.  That tool is part of the Transit Network Analysis Tools download, which you can get from GitHub or ArcGIS Online. ... View more

I know this post is from quite a long time ago, but I wanted to report back on the functionality that was requested. With the release of ArcGIS Pro 3.4, the Calculate Transit Service Frequency tool (the successor to BetterBusBuffers) has been enhanced to include an option to output transit statistics using actual route shapes instead of straight lines. To use this option, you have to run the GTFS To Public Transit Data Model tool in ArcGIS Pro 3.4 or higher to with the option to use your GTFS shapes.txt file to generate the new LVEShapes feature class in the public transit data model. Instead of this:   You get this:     ... View more

I know this post is from quite a long time ago, but I wanted to report back on the functionality that was requested. With the release of ArcGIS Pro 3.4, the Calculate Transit Service Frequency tool (the successor to BetterBusBuffers) has been enhanced to include an option to output transit statistics using actual route shapes instead of straight lines. To use this option, you have to run the GTFS To Public Transit Data Model tool in ArcGIS Pro 3.4 or higher to with the option to use your GTFS shapes.txt file to generate the new LVEShapes feature class in the public transit data model. Instead of this:   You get this:     ... View more

I think you can achieve this with some joins and post-processing. The FromJunctionID and ToJunctionID fields in Edges refer to the ObjectID values in Junctions.  The Junctions output's SourceType field will be NA_CLASS for stops and NETWORK for intermediate junctions that are part of the network.  If you join these two tables, you can figure out which edges started or ended at a stop instead of a regular junction, and you can sum or otherwise combine the intermediate rows. ... View more

Okay.  Can you tell us more about your desired workflow?  Why do you want to create a travel mode in Python and save it permanently to the network dataset?  (This doesn't sound like an unreasonable request, but I need to better understand your needs to prioritize this enhancement and determine whether some existing workflow could meet your needs.) ... View more

The SourceID field refers to the feature class ID of the network dataset source feature class the point was located on.  So if it locates on Streets OID 500 (I made that up), it will have a SourceID of 4 (or whatever the feature class ID of Streets is) and a SourceOID of 500. Some networks have multiple edge sources (like Streets and Sidewalks, for instance), or sometimes your locate settings allow you to locate on both edges and junctions.  The SourceID field helps you distinguish which of these network source the point located on. This documentation explains the meaning of the various network location fields: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/locating-analysis-inputs.htm#ESRI_SECTION1_9FF9489173C741DD95472F21B5AD8374 However, reading between the lines of your question, I'm guessing what you're actually wanting to know is how to relate the points loaded into your NA layer sublayer (Facilities, Incidents, etc.) back to the original dataset you loaded.  You are looking for a way to join the data using the ObjectID or some other unique identifier.  Is that right? Here's the process I recommend for that: Make sure your input points have some unique ID field.  You can use the ObjectID field if you want, but if you have some other unique ID field in the data that you use for your record keeping, that might work better. After creating your NA layer, use the Add Field To Analysis Layer tool to add a field to the sublayer you're going to add the points to (Facilities, Incidents, etc.).  Give it whatever name and type make sense.  You are going to map your input data's unique ID field to this new field. When you run Add Locations, use the field mapping control to map your input data's unique ID field to your newly added field. After Add Locations runs, you can run Join Field or Add Join or whatever other procedure to transfer the information you need back to your original dataset.  You can use the field you added to the sublayer and the original data's unique ID field as the fields to join with since they should have corresponding values. ... View more

We investigated this problem and found it to be a very simple bug.  We fixed it, and the fix will be available in the forthcoming ArcGIS Pro 3.4 release.  We also flagged the issue as something we can potentially fix in future patches of older versions of the software. ... View more

Hello.  Thanks for submitting an idea! You can create a travel mode in Python using the arcpy.nax.TravelMode() class as documented here: https://pro.arcgis.com/en/pro-app/latest/arcpy/network-analyst/travelmode-nax.htm.  Does this serve your needs? The only thing this cannot do is save the travel mode permanently to the network dataset.  Is that the functionality you're asking for? ... View more

The Calculate Locations issue is now logged in our system as BUG-000170977.  If you need updates on this issue, you can contact Esri Support with this bug number.  I will also post an update here once we've fixed it. ... View more

Okay, I understand the problem, and I can reproduce it on my end.  It seems like a bug in the Calculate Locations tool that the Status field is coming back as 0 instead of 7 for those points.  I will log the issue, and we'll see about fixing it. In the meantime, a workaround for you is to use the Add Locations tool instead of Calculate Locations.  You can create a dummy NA layer of any type and use Add Locations to load your points into it to calculate the network locations.  I just tested this, and this definitely works and returns the correct code of 7. ... View more

Hi, just wanted to give an update.  We have fixed the issue, and the fix will be available in the upcoming Pro 3.4 release.  Unfortunately, although the updated network will work properly in Pro 3.4+, it will still have the same problems in older versions of Pro.  We have flagged the issue as a candidate for future patches of older Pro versions. ... View more

I recommend approaching this using two major steps: First locate all the points on the network and identify the ones that don't locate on the closest network element. Then, using the remaining good records, do your Closest Facility analysis to identify any points that can't be reached for some other reason (disconnected network, other weird situations). Here is a more detailed breakdown of how you would do this: Add a field named "Status" of type Long to your feature class of input address points. Run the Calculate Locations tool on your feature class of input address points. Set whatever search tolerance and other locate settings make sense for your use case. Be sure to set the travel mode you intend to use for your Closest Facility analysis. Post-process the updated feature class of input address points.  The Status field will have been updated to reflect the point's locating status.  Select all features that have a Status field value of 1 (Not Located) or 7 (Not located on closest).  (Alternatively, select all features with a value not equal to 0, which is the normal code for OK.)  Read more about the Status field codes here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/closest-facility-analysis-layer.htm  The selected features are the ones that did not snap to the closest network element and are therefore invalid/not routable according to your rules.  Do whatever you normally do to update your records with this information. Switch the selection so only the good records are selected. Create your Closest Facility layer and configure the settings as needed Use the Add Locations tool to add the selected address points (the good records).  You can use the field mappings to use the pre-existing location fields that you already calculated, and this will save you some time. Add your fire stations as Facilities. Solve the analysis. Post-process the results to check for any address points that could not be reached using your normal method or by looking at the Status field, and update your records. I'm still not sure what problems you're having with Search Tolerance, but if you continue to have them, feel free to add screenshots or specific steps, and maybe I can see where the problem is. ... View more

I'm sorry you're having trouble migrating this workflow from ArcMap.  I'm happy to help you find a way to do this in Pro, which may be different from the way you did it in ArcMap.  However, I still don't have a very clear picture of exactly what you're trying to do.  What data are you starting with, and what information do you want to get from it?   "finding a lot of issues with changing the settings like the search tolerances etc. There does not seem to be a lot of consistency in results." Can you describe these problems in more detail?  What is your overall workflow?  Maybe we just need to find the right set of steps for you, and we can resolve these issues. Another idea for you: Have you tried symbolizing the network dataset in the map by restriction status?  You can adjust the network dataset symbology to symbolize a particular travel mode, and it will visually show you which streets are restricted, etc.  Some documentation on how to set this up: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/network-dataset-layer-symbology.htm  ... View more

We provided information to the user, and he hasn't responded back four months after we asked him if he needed further help or if his needs weren't satisfied by the existing functionality.  Closing this issue under the assumption that the software already does what the user needs. ... View more