nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Openbaar Vervoer Evaluator Geeft Altijd Zelfde Servicegebied Resultaten Terug

HeatherShearer55

Hallo, ik werk aan een netwerkanalyse met behulp van de ArcGIS Pro tutorial sjabloon netwerk. Ik heb alles gelaten zoals het was, behalve dat ik een loopmodus (afstand) heb toegevoegd. Echter, ongeacht welke dag en tijd ik invoer, geeft de openbaar vervoer analyse altijd dezelfde polygonen terug (ik heb de connectiviteit gecontroleerd, de tijd naar UTC veranderd en weer terug, enzovoort). De loopberekening werkt heel goed, maar niet het openbaar vervoer. Zou het probleem kunnen liggen bij de GTFS-bestanden die ik heb gedownload van de openbaar vervoersautoriteit en niet bij het netwerk? Alle hulp wordt zeer gewaardeerd. <\/P>

Vind meer berichten getagd met

Accepted answers

Melinda Morang

Hello Heather.

My best guess would be a problem with the weekday or day of week you're using for your analysis and its relationship with the valid days and dates for the original GTFS dataset.

In the tutorial, in the "Examine your input data" section, there's some discussion of the best way to examine your GTFS data's calendar.txt and calendar_dates.txt files to determine the valid days and dates. When you set the start time for your analysis, you need to pick something that works for your analysis.

Let me know if a review of that part of the tutorial doesn't help you find the problem, and we can take it from there.

All comments

HeatherShearer55

Sorry, I should have been more specific. I used BBB to calculate high frequency stops and then created service areas around these just using a generic weekday time. Will definitely look more into the stops file to see why the PT evaluator is not returning (markedly) different results for after hours etc.

Melinda Morang

I'm happy that you're happy, although I don't quite understand how you solved your problem. The BetterBusBuffers toolbox is intended to solve a different problem than the transit-enabled network datasets described in the Pro tutorial.

I think you need to take a look at the weekday fields and date ranges in calendar.txt and the specific dates available in calendar_dates.txt to determine a) whether or not you can use a generic weekday at all and b) what specific dates are valid for your data.

The blank stop times should not be a problem if you use the option to interpolate them when running GTFS To Network Dataset Transit Sources. In other words, I don't think that's causing the described problem.

HeatherShearer55

My GTFS files were a bit odd (some times were like 25:01:02) but there were no blank stop times. The weird thing was that it worked for specific weekdays (the files were for a specific date range) but not for out of hours or weekends (gave the same result as, for example, 8am on a Wednesday). I just need to keep looking for why the issue is happening. In the end, I just used your BetterBusBuffers toolbox to calculate what I needed (for a generic workday). Thanks again.

HeatherShearer55

Thank you SO much. I will do that. Your tutorial was great and I will go through in greater detail. And thank you so much for replying, I find your tutorials and various toolboxes incredibly useful 🙂

Will let you know how I go.

Melinda Morang

Hello Heather.

My best guess would be a problem with the weekday or day of week you're using for your analysis and its relationship with the valid days and dates for the original GTFS dataset.

Let me know if a review of that part of the tutorial doesn't help you find the problem, and we can take it from there.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.