Latest Contributions by MelindaMorang

Hello Scott.  I'm sorry for your trouble, but the good news is that there's an easy fix for you. For some reason, your street data did not end up with vertices at the locations where the StopsOnStreets intersect them: Without vertices at those locations, travelers cannot travel between the streets and the transit lines, hence why the transit lines are never being used. Vertices should be automatically created when you run the Connect Network Dataset Transit Sources To Streets tool. I will investigate further to see why this didn't happen. However, regardless of what happened in the first place, there is an easy way for you to fix your network. 1) If you made any changes to your network's configuration (I don't think you did...), run the Create Template From Network Dataset tool to preserve your network's configuration into a file. Skip this step if you didn't make any changes in that case you can just use the existing template that comes with the tutorial (the one you already used). 2)  Delete your network dataset. 3) Run the Integrate geoprocessing tool with the inputs configured as follows: The Integrate tool will create vertices at the intersections of the input feature classes. Setting the XY Tolerance to 0 ensures that your input features will not be moved at all. 4) Re-create your network dataset using the template. 5) Run Build Network to re-build your network. After this procedure, I was able to see the vertices in the expected location, and the network used the transit lines.   Assuming you're able to get up and running successfully and you have some time, could you tell me the following to help me investigate the cause of the original problem? What version of ArcGIS Pro are you using? Did you follow the tutorial steps exactly (using your own data), or did you deviate from that and do something else? Are you able to share your GTFS data with me so I can run some tests? ... View more

Hello @DavisTurner. First of all, you did the right thing in removing your GTFS data from the network dataset. BetterBusBuffers is about measuring access to public transit, not about measuring access to other facilities by public transit. Thus, you don't want your network dataset to model travelers taking public transit, you just want to model them walking.   Second, the size of your GTFS data is probably not the issue.  The Preprocess GTFS tool does the heavy lifting and reads in all the data from the different agencies. Once it's passed that point, constructing the Service Area polygon buffers becomes the difficult part. It will definitely take longer if you have more transit stops, but anyway, the slowness is in accounting for overlapping polygons and trying to "flatten" them.   Regarding your error: Are you getting this error on the "Step 1 – Preprocess Buffers" tool? That seems more likely, but please let me know if my assumption is incorrect.   This tool can often be finicky, and it's because it's doing some fairly complex geometric procedures to handle the overlapping polygons. Something strange is happening under the hood, and it's kind of impossible to know why. The only thing to do is to try again by altering some of the settings to change the geometry of the resulting polygons slightly and hoping that the geometry error will be avoided. Here are a few things you can try changing to see if it avoids the problem: Change the Polygon Trim setting to a different value. Update your impedance attribute slightly, like changing the assumed pedestrian walk speed by a small amount. Changing the Buffer Size from 20 minutes to some other number (I know, not ideal...) This last suggestion applies only if you are using ArcMap and not ArcGIS Pro: Calculate a Service Area Index on your network dataset. Basically, we introduced a newer, better algorithm for creating Service Area polygons which fixed a lot of weird geometry problems and made all-around better polygons. This is the default in ArcGIS Pro, but if you want to use it in ArcMap, you have to explicitly choose to calculate a Service Area Index in your network dataset settings. You just have to check on the check-box and run Build Network again.   Note: If you are not using ArcGIS Pro, I recommend switching to Pro anyway to get overall better functionality. The tool might take less time to run or at the very least be less likely to run out of memory.   Hope this helps! ... View more

Hello Seunghoon.  The GTFS specification only started to allow blank values for stop_lat and stop_lon fairly recently when it adopted support for platforms.txt.  The Add GTFS to a Network Dataset toolbox you are referring to is now deprecated and has not been updated since that change. That's why you're getting an error. In general, I do not recommend using the old Add GTFS to a Network Dataset toolbox anymore. Instead, you should use the newer, better tools available out-of-the box in ArcGIS Pro. Learn more here. However, switching to Pro will not actually solve this problem until ArcGIS Pro 2.8 is released (later this year). For now, you will need to manually update your GTFS data. Since the blank stop_lat and stop_lon rows probably represent non-geographic location_type values of 3 or 4, I suggest you just delete the rows. They will not be used in the analysis anyway. ... View more