Latest Contributions by MelindaMorang

Hi. Thanks for your question. I don't know the details behind exactly what Google Maps does, but I can at least try to explain what Esri's tools are doing and some areas where they might be different. First, it's been a while since I've looked at WMATA's GTFS data, but I recall that in the past it didn't include a calendar.txt file and used a calendar_dates.txt file for everything. This means it is not possible to do an analysis for a generic Wednesday. Instead, you have to pick a specific Wednesday when setting your analysis settings. Please be sure you've checked for this scenario. If you're running your analysis for a generic Wednesday or a specific date that is outside the date range the input GTFS data is valid for, the transit may not be getting used at all, and this would account for the discrepancy. Basically all routes are walking only. Also, if the routes or Service Areas appear unreasonable, it's possible something isn't configured right in your network dataset. If this is the case, we can try to debug this, or if you care share your data, I can take a look. We want to rule out any network configuration problems before examining any differences in results between Esri and Google. One difference between Esri's transit solves and Google Maps is that Esri's solvers use the exact time of day configured by the analyst as the starting or ending time. It's hypersensitive to this start time, and the result might be different if you choose a start time a minute or two off. I don't really know what Google does, but since they are designed more for passenger-facing routing apps, I think they're employing some sort of fuzzy start time logic to find the best or most sensible route. If leaving one minute earlier allows you to arrive at your destination 20 minutes earlier (because you don't miss a useful bus), I think Google will find that, but Esri's solvers don't have this functionality. The downloadable Transit Network Analysis Tools may help you to account for this in an analysis. The difference in street data is also a consideration, although the Streetmap Premium Custom Roads data should be of a high quality and include various pedestrian pathways and useful attributes. Google may have slightly different information about pedestrian paths, although probably not substantial differences that would account for huge discrepancies in travel time. Hope this helps a little.

‎03-20-2024

Yeah, I'm not sure what that error code means. The tool's code is not raising that error, so it means the error is probably occurring before the tool's code even starts running. Where are you running this code? From a standalone Python script? From a notebook within Pro? From a notebook somewhere else? Did you import the toolbox using arcpy.ImportToolbox() or arcpy.AddToolbox()?

‎03-20-2024

The documentation on the GitHub site should explain all the tool inputs and their requirements. It sounds like your input data is not in an ArcGIS feature class or table or whatever but rather some sort of dataframe (pandas?). For the tool to accept that as input, you have to first convert it to a feature class. You could try using XY Table To Point or manually constructing a feature class with an Insert Cursor. I can't really advise without knowing what type of data frame you're using or what's in it.

‎03-20-2024

You should just be able to download the toolbox from https://github.com/Esri/large-network-analysis-tools and use it as is, I think.

‎03-18-2024

This GitHub repo may be helpful to you: https://github.com/Esri/large-network-analysis-tools. You might be able to use the tools provided there out of the box. If you need to update or write code yourself, this DevSummit presentation may be helpful: https://mediaspace.esri.com/media/t/1_hzppnv8p

‎03-08-2024

Hi Riccardo. This sounds like a pretty complicated problem, and I'd say it's unlikely we'll be able to solve it here in Esri Community. Have you reached out to Esri Support yet? My guess is there's some sort of version incompatibility between the template created by ArcGIS Pro and what Server 10.9.1 does to interpret this template. But I really don't know for sure. Do you have a way to run Create Template From Network Dataset on the 10.9.1 Server from a well-functioning network? Maybe that template will work better on the 10.9.1 Server than the one created in Pro. Also, I know this may not be possible for various business reasons, but do you have the ability to update your Pro and Server versions? 10.9.1 is based on the old pre-Pro codebase, so things just behave differently sometimes. You're much less likely to experience compatibility issues when using Pro with Server 11.* since 11+ uses the same codebase as Pro. (Also note that Pro 2.9 is getting fairly old at this point as well.)

‎02-27-2024

The Solve Large Analysis With Known OD Pairs tool in the GitHub repo generates routes between origins and preassigned destinations. It uses the Route solver behind the scenes, not the OD Cost Matrix solver. If you want routes between preassigned OD pairs, you can use this tool. If you want some other kind of Routes, like routes with more that two stops or routes where you don't have preassigned OD pairs, then you're right: these tools don't currently have anything for your use case. Can you explain more about what you're trying to do and the size of your problem?

‎02-20-2024

"I wish I knew how exactly the scratch gdb was possibly corrupted" Me too! I'd love to get that fixed on our end. Glad that worked!!

‎02-16-2024

One further thought (after looking at the tool code): Try printing the value of arcpy.env.scratchGDB in your code and see what it points to. Delete it, and try running the script again. I've seen cases where the scratch gdb gets corrupted, and then weird things happen. Possibly it works when you run the tool in the Pro UI because it's pointing to a different scratch gdb.

‎02-16-2024

Okay. Well I don't see anything obvious from just looking at the script, unfortunately. You may need to call Esri Support so they can dig into your data and script in detail and figure out what's happening.

‎02-16-2024

Does the tool still error if you replace "Streets" with the full path to the streets feature class? Maybe the tool isn't correctly paying attention to the workspace environment set in the script.

‎02-15-2024

Hmm, I'm not sure why you're getting that error based on what I see in the code. However, the one thing that jumps out at me is the way you're constructing filepaths in the Python script. It's safer to use os.path.join() to construct paths from multiple components rather than the + operator. It doesn't seem like the way you have them should cause an error, but it's not really the best coding practice. Try updating like this, and see if that fixes it: streets_dir = os.path.join(proj_dir, '\data\raw\Street_Centerlines\Street_Centerlines.shp')

‎02-14-2024

Hi Ryland. We don't have any tools within the ArcGIS platform that can help you create full GTFS feeds for proposed changes, unfortunately. Maybe another reader will have a suggestion, but my sense is that this is probably not the right forum to find help. Regarding how to configure your proposed changes, you have two separate ways you can think about this: Create a separate GTFS dataset for each scenario, and a separate network dataset for each. Create a single GTFS dataset that has the proposed changes in it and a corresponding network dataset, and turn on/off service for certain routes/trips for each analysis. If the changes are self-contained (like removing trips from a route or adding an entirely new route), option 2 would work okay. You can create travel modes for each scenario that configure the supported parameters on the Public Transit evaluator: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/public-transit-evaluator.htm#ESRI_SECTION1_9FF9489173C741DD95472F21B5AD8374. Those can be used to turn on/off service on routes and trips. But if the changes are at all complicated, it's easier to create separate networks for each.

‎02-13-2024

First off, if your network still shows dirty areas in the map (usually a purple box covering all or part of the network), you need to run the Build Network tool. This tool incorporates edits to the network dataset properties and feature geometry into the internal logical network. If you don't do this step and you try to solve network analysis when you still have dirty areas, any changes you made to the network might not get used. So, if you did something with your transit lines and didn't build the network, this might be the reason they are never used. If that isn't the issue, then here are the typical reasons that the transit lines are not used: The date and time you chose for the analysis has no transit service. If you chose a specific date, and that date is outside the range of valid dates in the Calendars table, then there's no service. Or, if you used a generic weekday, but the Calendars file is empty, there will be no service because you have to use a specific date for this dataset. You have a connectivity problem. It's usually where the StopConnectors meet the streets. You can use the Explore Network tool to click on a stop connector and make sure it highlights the street it appears to connect to to show that it is actually connected. Your evaluators are configured incorrectly. If you used the provided template and didn't change anything, this probably isn't the issue, but it's worth double checking that for the PublicTransitTime cost attribute, the LineVariantElements edge source uses the Public Transit evaluator. You're using the wrong travel mode, or your travel mode is configured incorrectly. If you used the provided template and didn't change anything, this probably isn't the issue, but it's worth double checking that the travel mode you're using for your analysis uses the PublicTransitTime cost attribute for its impedance and doesn't have any weird restrictions that make travel on the transit lines restricted. I noticed in your screenshot showing the table from Explore Network that the transit line is showing Prohibited in both directions. That makes it seem like a problem with your cost attribute, restrictions, or travel mode. Note that you can flip over to the Settings tab in the Explore Network pane and choose which travel mode to use with the tool, so I can't tell if you're just using the wrong travel mode in the tool or if this is actually a symptom of the problem you're trying to diagnose. In case you haven't found it, here is the text version of the tutorial that the video you watched walks through: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/create-and-use-a-network-dataset-with-public-transit-data.htm The text version has a bunch of links to other help pages that might be useful. If you still can't get your network working, I recommend you contact Esri Support. They can examine your network in detail and help you find what went wrong.

‎02-08-2024

Did you get build errors when you built the network dataset? There are a lot of turn-related checks the build process does, and it will report out specific errors. If you need to check your build errors, open the Build Network tool to build the network dataset. You likely need to rebuild the whole thing so it will look at all the turns, so check on the option to do a full rebuild. When the tool completes, if there is a warning message, check the message text for the path to the build error text file. Open the text file and check the build errors to see if it has flagged anything with your turns.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by MelindaMorang

Re: Discrepancies in travel time with Public Transit Data Model- service area and closest facility analysis

Re: Calculate travel distance between each point

Re: Calculate travel distance between each point

Re: Calculate travel distance between each point

Re: Calculate travel distance between each point

Re: network from Template: geoprocessing vs. local

Re: ArcGIS Pro 2.9 - Route Solver Multiprocessing in Standalone Script

Re: ERROR 000354 when calling Connect Public Transit Data Model To Streets in python script

Re: ERROR 000354 when calling Connect Public Transit Data Model To Streets in python script

Re: ERROR 000354 when calling Connect Public Transit Data Model To Streets in python script

Re: ERROR 000354 when calling Connect Public Transit Data Model To Streets in python script

Re: ERROR 000354 when calling Connect Public Transit Data Model To Streets in python script

Re: Creating GTFS Feeds for Future Scenario Public Transit Network Dataset

Re: Network Dataset not using the transit options

Re: Newtwork Dataset's Turn Issue

Re: Public Transit Model: Change LineVariantElemen...

Re: network from Template: geoprocessing vs. local

Re: Creating GTFS Feeds for Future Scenario Public...

Re: ERROR 000354 when calling Connect Public Trans...

Re: ERROR 000354 when calling Connect Public Trans...