<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Add GTFS to a Network Dataset version 0.5.0.0 released in Public Transit Questions</title>
    <link>https://community.esri.com/t5/public-transit-questions/add-gtfs-to-a-network-dataset-version-0-5-0-0/m-p/712693#M487</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello to those of you who are using the Add GTFS to a Network Dataset tool/code sample.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 0.5.0.0 has been released.&amp;nbsp; Download it here: &lt;A href="http://www.arcgis.com/home/item.html?id=0fa52a75d9ba4abcad6b88bb6285fae1"&gt;http://www.arcgis.com/home/item.html?id=0fa52a75d9ba4abcad6b88bb6285fae1&lt;/A&gt;.&amp;nbsp; Please remember to unregister the previous version of the transit evaluator before registering this one.&amp;nbsp; Also, always remember to unregister it before uninstalling ArcGIS, or else you might have problems with your registry getting confused.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This tool is now also available on GitHub if you want to play with the source code: &lt;A href="https://github.com/Esri/public-transit-tools"&gt;https://github.com/Esri/public-transit-tools&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I highly recommend that everyone using this tool upgrade immediately to version 0.5.0.0, as this update corrects a problem that caused incorrect results.&amp;nbsp; This problem was identified by a user of Add GTFS who ran a large number of OD Cost Matrix calculations.&amp;nbsp; She found that in a small number of cases (&amp;lt;0.1%), the results were incorrect.&amp;nbsp; I will attempt to explain the problem and the solution here for those who are interested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suppose you use the transit evaluator to calculate the travel time between Point A and Point B.&amp;nbsp; Traveler 0 starts at 10:00 AM, it takes him 1 hour to get to Point B.&amp;nbsp; Traveler 1 starts at 10:01 AM from the same location, and it takes 59 minutes.&amp;nbsp; Traveler 2 starts at 10:02 AM, it takes 58 minutes.&amp;nbsp; This makes sense.&amp;nbsp; All three travelers end up on the same bus, so they all reach Point B at the same time, even though they started at different times.&amp;nbsp; Traveler 0 just had to wait one minute longer than Traveler 1 and two minutes longer than Traveler 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem was that in a very small number of cases, Traveler 1 would miss the bus, and it would take, say, 2 hours to reach Point B:&lt;/P&gt;&lt;P&gt;10:00 – 1 hour&lt;/P&gt;&lt;P&gt;10:01 – 2 hours&lt;/P&gt;&lt;P&gt;10:02 – 58 minutes&lt;/P&gt;&lt;P&gt;This clearly does not make sense because Traveler 1 could just wait until 10:02 and reach Point B in 59 minutes instead of starting at 10:01 and taking two hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason for these anomalous results turned out to be a very deep down small rounding error, and version 0.5.0.0 corrects the problem by avoiding these rounding errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As always, please let me know if you find any problems, and let me know what you’re working on!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&amp;nbsp; Happy analysis!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Jan 2016 22:45:13 GMT</pubDate>
    <dc:creator>MelindaMorang</dc:creator>
    <dc:date>2016-01-20T22:45:13Z</dc:date>
    <item>
      <title>Add GTFS to a Network Dataset version 0.5.0.0 released</title>
      <link>https://community.esri.com/t5/public-transit-questions/add-gtfs-to-a-network-dataset-version-0-5-0-0/m-p/712693#M487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello to those of you who are using the Add GTFS to a Network Dataset tool/code sample.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version 0.5.0.0 has been released.&amp;nbsp; Download it here: &lt;A href="http://www.arcgis.com/home/item.html?id=0fa52a75d9ba4abcad6b88bb6285fae1"&gt;http://www.arcgis.com/home/item.html?id=0fa52a75d9ba4abcad6b88bb6285fae1&lt;/A&gt;.&amp;nbsp; Please remember to unregister the previous version of the transit evaluator before registering this one.&amp;nbsp; Also, always remember to unregister it before uninstalling ArcGIS, or else you might have problems with your registry getting confused.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This tool is now also available on GitHub if you want to play with the source code: &lt;A href="https://github.com/Esri/public-transit-tools"&gt;https://github.com/Esri/public-transit-tools&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I highly recommend that everyone using this tool upgrade immediately to version 0.5.0.0, as this update corrects a problem that caused incorrect results.&amp;nbsp; This problem was identified by a user of Add GTFS who ran a large number of OD Cost Matrix calculations.&amp;nbsp; She found that in a small number of cases (&amp;lt;0.1%), the results were incorrect.&amp;nbsp; I will attempt to explain the problem and the solution here for those who are interested.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suppose you use the transit evaluator to calculate the travel time between Point A and Point B.&amp;nbsp; Traveler 0 starts at 10:00 AM, it takes him 1 hour to get to Point B.&amp;nbsp; Traveler 1 starts at 10:01 AM from the same location, and it takes 59 minutes.&amp;nbsp; Traveler 2 starts at 10:02 AM, it takes 58 minutes.&amp;nbsp; This makes sense.&amp;nbsp; All three travelers end up on the same bus, so they all reach Point B at the same time, even though they started at different times.&amp;nbsp; Traveler 0 just had to wait one minute longer than Traveler 1 and two minutes longer than Traveler 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem was that in a very small number of cases, Traveler 1 would miss the bus, and it would take, say, 2 hours to reach Point B:&lt;/P&gt;&lt;P&gt;10:00 – 1 hour&lt;/P&gt;&lt;P&gt;10:01 – 2 hours&lt;/P&gt;&lt;P&gt;10:02 – 58 minutes&lt;/P&gt;&lt;P&gt;This clearly does not make sense because Traveler 1 could just wait until 10:02 and reach Point B in 59 minutes instead of starting at 10:01 and taking two hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason for these anomalous results turned out to be a very deep down small rounding error, and version 0.5.0.0 corrects the problem by avoiding these rounding errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As always, please let me know if you find any problems, and let me know what you’re working on!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&amp;nbsp; Happy analysis!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jan 2016 22:45:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/public-transit-questions/add-gtfs-to-a-network-dataset-version-0-5-0-0/m-p/712693#M487</guid>
      <dc:creator>MelindaMorang</dc:creator>
      <dc:date>2016-01-20T22:45:13Z</dc:date>
    </item>
  </channel>
</rss>

