<?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 Re: Preprocess Buffers Invalid Topology Error in Public Transit Questions</title>
    <link>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1063184#M117</link>
    <description>&lt;P&gt;Thanks Melinda. Well this was user error. I made an error in setting up my distance cost attribute (in miles) which was causing gigantic walksheds to be created. I also managed to "trim" my GTFS file to my area of interest based on selecting stops within the County and then querying out all my related GTFS records based on that selection. I look forward to the native tool in 2.9 Thanks again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Russ&lt;/P&gt;</description>
    <pubDate>Mon, 31 May 2021 00:44:13 GMT</pubDate>
    <dc:creator>RussellProvost1</dc:creator>
    <dc:date>2021-05-31T00:44:13Z</dc:date>
    <item>
      <title>Preprocess Buffers Invalid Topology Error</title>
      <link>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1062846#M115</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/101257"&gt;@MelindaMorang&lt;/a&gt;,&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good morning and happy Friday. I have a very large regional GTFS file that I obtained directly from Washington Metropolitan Area Transit Authority (WMATA). It is the same GTFS file that runs their &lt;A href="https://www.wmata.com/schedules/trip-planner/" target="_self"&gt;online trip planner&lt;/A&gt;. It combines all of the regional transit agencies into one large GTFS file.&lt;/P&gt;&lt;P&gt;I am attempting to create a transit coverage map for Montgomery County Maryland using the better bus buffers tool. This is actually a very important analyses as it is part of our &lt;A href="hhttps://montgomeryplanning.org/planning/transportation/transportation-monitoring/mobility-assessment-report/" target="_self"&gt;transportation monitoring efforts&lt;/A&gt;. After 3.5 days of processing the "Preprocess Buffers" tool ended with an "Invalid Topology" error (see below). Could this be an issue of having run the process in a map with Maryland State Plane, but the GTFS station locations being represented in Lat/Long? Could it be a function of a station being located outside the extend of my network (I downloaded and processed OSM data for the entire Washington/Baltimore DC region so most stations should be covered)? I only need transit information for inside Montgomery County, so I was thinking of ways to trim the GTFS file so that it only contains stops in Montgomery County. Any advice on this potential strategy? Thanks for your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step 1 - Preprocess Buffers&lt;BR /&gt;=====================&lt;BR /&gt;Parameters&lt;/P&gt;&lt;P&gt;Output directory C:\Users\Russell.Provost\OneDrive - The Maryland-National Capital Park and Planning Commission\Data\2020MAR\Transit\GTFSForBetterBusBuffers&lt;BR /&gt;Name for output geodatabase (created when the tool is run) BetterBussBuffers&lt;BR /&gt;SQL database of preprocessed GTFS data C:\Users\Russell.Provost\OneDrive - The Maryland-National Capital Park and Planning Commission\Data\2020MAR\Transit\GTFSForBetterBusBuffers\BetterBusBuffers.sql&lt;BR /&gt;Network dataset C:\Users\Russell.Provost\OneDrive - The Maryland-National Capital Park and Planning Commission\Data\2020MAR\Transit\GTFSForBetterBusBuffers\Network.gdb\Network\TransitNetwork_ND&lt;BR /&gt;Impedance attribute (Choose one that works for pedestrians.) Length (Units: Miles)&lt;BR /&gt;Buffer size (in the same units as your impedance attribute) 0.25&lt;BR /&gt;Network restrictions (Choose ones appropriate for pedestrians.)&lt;BR /&gt;Polygon trim (in meters) (Enter -1 for no trim.) 20&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;=====================&lt;BR /&gt;Messages&lt;/P&gt;&lt;P&gt;Start Time: Thursday, May 20, 2021 4:54:59 PM&lt;BR /&gt;Creating a feature class of GTFS stops...&lt;BR /&gt;Creating service areas around stops...&lt;BR /&gt;(This step will take a while for large networks.)&lt;BR /&gt;Reformatting polygons for further analysis...&lt;BR /&gt;(This step will take a while for large networks.)&lt;BR /&gt;Error post-processing polygons&lt;BR /&gt;Failed to create BetterBusBuffers polygons.&lt;BR /&gt;Traceback (most recent call last):&lt;BR /&gt;File "&amp;lt;string&amp;gt;", line 484, in execute&lt;BR /&gt;File "C:\Users\Russell.Provost\OneDrive - The Maryland-National Capital Park and Planning Commission\Data\2020MAR\Transit\Tools\BetterBusBuffers_0.14.0.0\BBB_Polygons_Step1.py", line 133, in runTool&lt;BR /&gt;arcpy.management.FeatureToPolygon(polygons, FlatPolys, clusTol, "", dummypoints)&lt;BR /&gt;File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 4057, in FeatureToPolygon&lt;BR /&gt;raise e&lt;BR /&gt;File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 4054, in FeatureToPolygon&lt;BR /&gt;retval = convertArcObjectToPythonObject(gp.FeatureToPolygon_management(*gp_fixargs((in_features, out_feature_class, cluster_tolerance, attributes, label_features), True)))&lt;BR /&gt;File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in &amp;lt;lambda&amp;gt;&lt;BR /&gt;return lambda *args: val(*gp_fixargs(args, True))&lt;BR /&gt;arcgisscripting.ExecuteError: ERROR 160196: Invalid Topology&lt;BR /&gt;Failed to execute (FeatureToPolygon).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Failed to execute (BBBPolygons_PreprocessBuffers).&lt;BR /&gt;Failed at Monday, May 24, 2021 7:47:48 AM (Elapsed Time: 86 hours 52 minutes 47 seconds)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 May 2021 14:00:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1062846#M115</guid>
      <dc:creator>RussellProvost1</dc:creator>
      <dc:date>2021-05-28T14:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: Preprocess Buffers Invalid Topology Error</title>
      <link>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1063164#M116</link>
      <description>&lt;P&gt;Hello Russell.&amp;nbsp; Unfortunately, the procedure used within BetterBusBuffers to parse the overlapping geometry of all the Service Area polygons sometimes has problems like this.&lt;/P&gt;&lt;P&gt;If you haven’t already, please take a look at this post: &lt;A href="https://community.esri.com/t5/arcgis-for-public-transit/invalid-topology-error-when-running-betterbusbuffers/m-p/1023915#M328" target="_blank"&gt;https://community.esri.com/t5/arcgis-for-public-transit/invalid-topology-error-when-running-betterbusbuffers/m-p/1023915#M328&lt;/A&gt;&lt;BR /&gt;I suspect the answer there may also help you out.&lt;/P&gt;&lt;P&gt;Other than tweaking those settings, I don't really have a good solution for you. You could definitely try to clip out the stops for only the area you care about, although I do not have any tools to help you do that easily.&lt;/P&gt;&lt;P&gt;The good news is that I am currently working on a ground-up rewrite of BetterBusBuffers that will be included as a core tool in the next release of ArcGIS Pro (2.9 - late 2021 or early 2022). The rewrite uses a different methodology for handling overlapping polygons (a rasterization and sampling approach) which will hopefully avoid these problems and make the final output less unwieldy. I know this doesn't help you out in the short term, but perhaps next time you have to do this task, you can use the improved version.&lt;/P&gt;</description>
      <pubDate>Sun, 30 May 2021 17:41:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1063164#M116</guid>
      <dc:creator>MelindaMorang</dc:creator>
      <dc:date>2021-05-30T17:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: Preprocess Buffers Invalid Topology Error</title>
      <link>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1063184#M117</link>
      <description>&lt;P&gt;Thanks Melinda. Well this was user error. I made an error in setting up my distance cost attribute (in miles) which was causing gigantic walksheds to be created. I also managed to "trim" my GTFS file to my area of interest based on selecting stops within the County and then querying out all my related GTFS records based on that selection. I look forward to the native tool in 2.9 Thanks again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Russ&lt;/P&gt;</description>
      <pubDate>Mon, 31 May 2021 00:44:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/public-transit-questions/preprocess-buffers-invalid-topology-error/m-p/1063184#M117</guid>
      <dc:creator>RussellProvost1</dc:creator>
      <dc:date>2021-05-31T00:44:13Z</dc:date>
    </item>
  </channel>
</rss>

