GTFS error

167
5
01-23-2021 02:57 PM
OnelPerez
New Contributor II

Hi ¿How I can correct this error 

Tags (2)
0 Kudos
5 Replies
DanPatterson
MVP Notable Contributor

From Create and use a network dataset with public transit data—ArcGIS Pro | Documentation

about 3/4 the way down

The most likely build errors you may encounter are those indicating that StopConnectors features have an empty geometry. For example, a common message is SourceName: StopConnectors, ObjectID: 232, Geometry is empty. This typically occurs when one of the Stops features and its associated StopsOnStreets feature are spatially coincident because the StopsOnStreets feature did not successfully snap to a nearby street. Consequently, the connector line generated between the two has no length.


... sort of retired...
OnelPerez
New Contributor II

What do you advise me to correct the error with the empty geometries and this other SourceName: StopsOnStreets, ObjectID: 18053, Standalone user-defined junction is detected.

0 Kudos
MelindaMorang
Esri Regular Contributor

That build error indicates that the transit stop has not successfully connected to a street feature. There are a couple of likely reasons for this:

  1. The street dataset you're using does not cover the entire geographic area that your transit system covers, so there are some stops that cannot find a street to snap to.
  2. There are some transit stops in your GTFS data that are in the wrong geographic place. For example, you might have a few stray stops in the middle of the ocean or in Antarctica or something because the lat/lon coordinates are wrong.
  3. Your street data covers the correct geographic extent, but it is missing some smaller roads or sections where there are transit stops, so the stops cannot find anything to snap to within the search tolerance.
  4. The search distance you used when running the Connect Network Dataset Transit Sources To Streets tool was too small, and for some reason, your transit stops are offset significantly from the street centerlines. For this reason, they failed to snap to the streets.

I think you need to take a close look at both the locations of your transit stops and also your street data to determine which of the above cases is causing your problem. Once you've determined that, then you can figure out how to fix it.

If the problem is only for a few stops, and they're in an area where you don't expect them to be used for your analysis, then you can safely ignore the build errors. The rest of the network will continue to function. Otherwise, you will need to resolve the issue. You might need to edit the stop locations (or correct the original GTFS and start over), update your street data or use a different street dataset, or re-run Connect Network Dataset Transit Sources To Streets with a larger search tolerance.

OnelPerez
New Contributor II

How can We make a map similar to the one in the attached image? However, We need to make a map that shows the frequency of trips on public transport on the street's edge.

0 Kudos
MelindaMorang
Esri Regular Contributor

To map the frequency of public transit service, you can use the Count Trips on Lines tool in the BetterBusBuffers toolbox: http://esri.github.io/public-transit-tools/BetterBusBuffers.html

However, this tool will not map the frequency of bus service on the streets. The lines produced by the tool are simple straight lines connecting adjacent stops. I have not found a good way to match these lines to the underlying street features, unfortunately.

0 Kudos