Overlapping Bus routs

There is actually a way to do what the original poster is describing. I recently created a network that solved this problem by creating a three dimensional multimodal network. An unpublished masters paper helped guide me (http://www.itc.nl/library/papers_2012/msc/upm/mahrous.pdf), but it's connectivity rules can be optimized greatly and in the end I only had . Attached is a screenshot I captured of my network which I edited in illustrator for some quick color and labeling.
[ATTACH=CONFIG]24913[/ATTACH]

Overview
What you have to do is to give each bus route a Z value that corresponds to it's bus route number (e.g. Bus Route 25 is 25 m above street level, which is 0m). This ensures that while the bus routes are in the same connectivity group, they will never intersect. You must also create a polyline features, "connectors" whose endpoints correspond with the bus stops, which are at 0m and spatially coincident to the street (walking network), and the bus route. To make sure that these connectors do not cross over each other, giving you the problem you now have, I messed with the geometry, in Python, of the pre-made bus network I was using to offset every route 5 meters to the East. This gives you connectors that radiate from a single bus stop to every route serviced at that location, thus modeling bus stops that service multiple routes. These connectors in themselves do not add to the total travel cost if you do not want them to. I was measuring cost in minutes and used these connectors to have a route specific, one-way cost of "waiting at the bus stop" when going from the street to the route. Since time used egressing a bus is negligible, I had the time cost as zero when the agent moved from the route to the street.

If you have a large network, as I did with 25 routes and over 9750 stops, knowledge of Python and how to modify the geometry of created features is needed for this to be feasible time wise. Doing this by hand would take a horribly long time. I would say that once all the attribute fields were set and ready it took me about 5 hours worth of scripting and debugging to get the final network components (one file for 3D connectors, 3D routes, 3D streets, and 3D stops). From there I just created the network data set in Arc Catalog.

An important note: When solving a network layer, you must choose the option to display the routes as straight lines. For whatever reason the analysis failed when ArcMap tried to display the individual routes on the path they took. My guess is an issue with the three dimensionality of the network.

Feel free to contact me with any questions or any issues with implementing Python in such an endeavor!

Jeremiah

NetworkModel2.jpg

All comments

what kind of error? what kind of evaluator are you using ?

sorry, just saw you started a new thread.

Thank you Jeremiah. You explained it very well. I'm able to do everything quite easily using model builder. I've built a dataset and it works for the most part, there are some funny routes but I think this is down to the data quality. I also made a dataset without doing it in 3D, just offset the routes, and it seems to work the same. Can I ask you to put up screenshots of your Time evaluators? I followed the tutorial but I get errors when I try and route using my evaluator for time

[LEFT]

Thanks for the help so far. So I offset my routes by using Editing and then Move and it allowed me to move them a specified distance. Now I have built a network of just bus routes, but my stops and connectors don't seem to be working. What connectivity policy should I have? I used the one in the paper you referenced as a guide. I'll attach an image of my problem. Also you'll see in the Connectors image that the Real Stop are connected in a linear fashion as opposed to radial, is this correct? Also, when building the Network Dataset, do I build the Z Elevation?
[ATTACH=CONFIG]26456[/ATTACH]
[ATTACH=CONFIG]26457[/ATTACH]

Conor,
Unfortunately, without being there and intimately involved with the project I can only be of limited help, but I will try to address some of your concerns. I also suggest utilizing the tool I built, which has instructions in the readme, which will construct the 3D network and only leave the network dataset build for you to worry about.

Connectors and Stops
Connectivity
Linear versus Radial
Z-values (Elevation)

Hopefully this clarifies some things, but again I suggest using the tool in my previous post to save a lot of time and hassle, if you are up against a deadline, and to experiment with the intricacies of building one from scratch later on with a small dataset, as suggested by Srirama.
[/LEFT]

NetworkDataset_Connectivity.jpg

NetworkDataset_Evaluators.jpg

NetworkDataset_Sources.jpg

I will start smaller but I need to do the whole city for a project so hopefully I can build up to that. I don't think I have to worry about flyovers or underpasses just yet. Thank you for your help

I will give you answer, if you give me points... 😄

I think you are taking too much to digest. To understand the logic, do not do the whole city. Just do two routes, on a cross-road like network. Start with it.

If you really want to continue with your complete city network ( which I do not propose you to do at this moment), then please use 'planarize' tool to cut your roads and routes with false connectors, and then use end-point connectivity. However, I have to caution you, that using planarize on whole network with overirde any grade separations (flyovers, underpass, over pas, ramps) that do not need to connect will also get connected. To avoid this behavior, you must unselect all your such grade separations before you hit 'planarize'.

again, start with a simple network and tackle the city later.

kind regards,

Does it have to be end-point connectivity? My stops are not at end points only but are all along each route and are snapped to the edge. Should I have them snapped to the vertices for Any Vertex connectivity? Also, do the connectors need an elevation attribute, and if so should it be zero? When I compare my connectors to yours and jeremiahs, they are connected differently to the stops. With your connectors all pseudo stops are connected to one real stop, while mine that is not the case, with real stops only connected to one pseudo stop which in turn is connected to other pseudo stops. See in the image below. Does this make a difference? Sorry for all of the questions but I have been working on this for so long and it is still not changing at the stops for me

EDIT: I keep getting this warning "Warning: No route from location "Graphic Pick 1" to location "Graphic Pick 2". Error: No solution found." When I put the start point and end point on different routes

[ATTACH=CONFIG]26491[/ATTACH]

Connectors.JPG

Conor,

1. make sure your routes are split at bus stops. use end-point connectivity
2. the solution is not difficult. I used a very simple logic: understand how network analyst works. Once you understand, just imagine raising each route to a unique height.
3. connect each stop to the route at its own height.
4. that is all about building the network.

Here I attach my very first model that I did for an Indian city in 2008. I did not even use python, it was a small excel macro. On Page 5-6 you will see the simple logical construction of the model.

pres36.7z.zip

Thanks for the help so far. So I offset my routes by using Editing and then Move and it allowed me to move them a specified distance. Now I have built a network of just bus routes, but my stops and connectors don't seem to be working. What connectivity policy should I have? I used the one in the paper you referenced as a guide. I'll attach an image of my problem. Also you'll see in the Connectors image that the Real Stop are connected in a linear fashion as opposed to radial, is this correct? Also, when building the Network Dataset, do I build the Z Elevation?
[ATTACH=CONFIG]26456[/ATTACH]
[ATTACH=CONFIG]26457[/ATTACH]

Connectors.JPG

Problem 1.JPG

Jeremiah,

Do the routes have to be offset? And if so, how do you offset them?

Conor,

Thanks for the excellent question as it is one that I find comes up often. Not offsetting is something I did not experiment with due to the time constraints of the original project I created the network for. I'm not sure if 3D Analyst could support a purely vertical edge; perhaps Ms. Morang could shed some light on this? My main purpose for offsetting, other than the fact that I was following a large part of Mahrous (2012) procedure, was to ensure the connector line features would slope out from the street level stop to the serviced bus route(s). Additionally, were you to create a 3D network and not offset the routes, and there was a stop that serviced multiple routes, you would have a connectivity nightmare ensuring that the spatially coincident edges serving as connectors between street and route did not allow crossovers. This offset was the simplest solution and allows for simple connectivity between minimal numbers of features. This also makes the design very accessible for those with little network analysis or GIS experience.

As for how I went about offsetting the routes, initially I used a small tool, see Copy Parallel below, but it resulted in little square "loops" on the corners of the new lines, both a lengthening and a distortion from the original line shape.
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/Copying_parallel_line_features/001t00000033000000/
However, when I made this program I found that iterating through each Point Object (vertex) in the Line Feature and editing the geometry directly by increasing the X coordinate by some uniform value was the most precise and expedient way of offsetting the routes. For example, If you had a vertex with an initial X attribute of 35000 ft from the projection origin and an initial Y attribute of 18500ft from the projection origin and put them through the offset portion of my script with an offset of 5 ft, the resultant X and Y attributes would be 35005ft and 18500 ft, respectively. ESRI's recent publication of Python Scripting for ArcGIS by Paul A. Zanderbergen (ISBN-13: 9781589482821) has an excellent chapter on modifying geometries through Python.

Let me know if that didn't address your question fully.

Happy to see my work being referenced here 🙂 . if you trace back the references you will find the first reference in a conceptual model from my 2008 work.

happy happy 🙂 🙂 , time for some beer.

regards,

Jeremiah,

Do the routes have to be offset? And if so, how do you offset them?

#Jeremiah: I have seen your pdf. Why for bus and stop haven't use subtype in connectivity? so you have 1 feature class bus and 1 feature class stop.

Domenico,
The PDF you reference is not my work. It is the work of a Master's candidate from the Netherlands named Reem Fawzy Mahrous. I agree that the connectivity policies in that PDF could have been simplified. At the time I began working on the research I had 1 year of GIS experience and my focus is actually public health and medical geography. Due to the time constraints of my senior thesis, I had to teach myself Network Analyst in the course of a month or two and was unaware of subtypes within connectivity policies. Thank you for bringing them to my attention; I'll be sure to read into it more and know they are a possible tool for the future.

On a separate note, I mentioned that I would work on a standalone tool that will allow my 3D network construction process to be repeated thus making hours of work into minutes of work, depending on computing resources and input file sizes. I have attached the program and the readme file (please read that first). Make sure both files are in the same directory or the help button, within the GUI, will not work. If anyone has any questions or feedback I would greatly appreciate it.

3DTransportationNetworkConstructor.zip

MelindaMorang

Hello everyone. I just wanted to let you know about a new prototype tool from Esri's Network Analyst team which allows you to add GTFS public transit data directly to a network dataset. You can use this network dataset with the Network Analyst tools to run time-aware analyses that incorporate the transit schedules.
You can download the toolset and instructions here:
http://www.arcgis.com/home/item.html?id=0fa52a75d9ba4abcad6b88bb6285fae1
Please do not hesitate to contact me at mmorang@esri.com with questions or comments about this toolset.

nicogis

In these days I am developing a tool in c#/arcobjects for data GTFS ( General Transit Feed Specification ) to multimodal Network Dataset for Network Analyst.

for stop bus the idea is use a custom network evaluator kind this one to add a wait time : http://www.arcgis.com/home/item.html?id=72ef24542857413c8981f2e196f1bb13

When I finished work I notification in this thread

#Jeremiah: I have seen your pdf. Why for bus and stop haven't use subtype in connectivity? so you have 1 feature class bus and 1 feature class stop.

MelindaMorang

Thanks for the kind words, Jeremiah. I'm glad to see that you were able to come up with a really nice solution for your project!

We here at Esri are working to develop a much more advanced and useful set of tools for public transit analysis. I am always interested in hearing from users working in this area to learn about their work, the types of analyses they want to perform, and the challenges they have with our current software. Feel free to send me a private message if you want to talk further about public transit analyses. You are also always welcome to contact me with complaints or suggestions about Network Analyst tools or documentation in general.

Thanks, and good luck with your transit projects!

Any time! Feel free to contact me if you have any other questions pertaining to this.

To be fair, the Network Analyst and 3D Analyst extensions are massive in both size and power and one of the best things about ArcGIS is that users can combine aspects of multiple extensions to create solutions that not even ESRI may have anticipated. So while the specialists are indeed quite qualified specialists, they cannot always have an answer and that is where the collective experiences in the forums come into play.

Make sure to give your feedback on the documentation provided for Network Analyst or anything pertaining to ArcGIS as ESRI can only make improvements with feedback from users. I know that Ms. Morang, a specialist in this thread, assisted me by soliciting my thoughts last fall on Network Analyst in order for my suggestions to be heard.

Keep up the good work specialists!

MohamedDarwish

Dear Jeremiah Nieves, you really made my day & i appreciate your support.
you have good skills for describing the solution.

HONESTLY, your answer is much better than ESRI specialists

:D
Best Regards

Thank U Jeremiah Nieves for your great post , i really appreciate that
also the research link was really helpful

could you please provide your python code or which tools to create the connector feature class automatically as i have more than 70 route with 1500 bus station

You're quite welcome. Unfortunately, since I was teaching myself Network Analyst from the ground up last fall, I did not implement a Python script until I had created a number of the features by hand. In addition, the script was essentially a kludge, a quick and dirty (yet functional) fix that used paths specific to my files. However, I have provided the (ugly) code below as it may help. Please note that the code is written for ArcGIS 10.0.

I will go ahead and give an overview of creating a connector outside of Python, to the best of my recollection, as I assume it can be replicated in model builder, although I find implementing iterations much easier in Python. I am giving serious contemplation to making a summer project of creating a custom tool that will take necessary input features, with the proper attribute fields, and create the spatial framework for the network. This would only leave the user the task of adding of travel costs to the features.

Overview of Connector Construction

It is assumed that the bus routes have been offset at this point, but not turned into 3D features yet. Your bus stops must have unique IDs; this is critical to being able to construct connectors.
Take your original bus stop feature and create a duplicate bus stop feature which I will refer to as "pseudo stops." The bus stops should be turned into a 3D feature (Feature to 3D By Attribute) with a z value of '0.' Make sure to Snap these stops to whatever is serving as the pedestrian paths in the network.
The pseudo stops are a bit trickier.
First, 'Snap' the pseudo stops to the nearest bus route. For this to work, your bus stop and bus route data should be accurate in their respective locations.
For each bus route, you are going to 'Select By Location' pseudo stops that intersect the given bus route, give each of those selected stops an ending elevation attribute equal to the given bus route's number, and export the selected pseudo stops as their own feature. I recommend putting the route number serviced somewhere in the name.
Once you have done this, you should have a feature of pseudo stops for each bus route. Give each of them an attribute that gives them a z value equal to that of the route served. Merge all of these features into one pseudo stop feature and use 'Feature to 3D By Attribute' using aforementioned z value of the route serviced.[/INDENT]
You should now have the set of real bus stops at z == 0 and the set of pseudo bus stops with z == route # serviced. In the end, this allows you to have single bus stops at ground level that service multiple routes.
Merge the two, psudeo and real, bus stop features.
Use the 'Points to Line Tool (Data Management)' to construct the connectors using the unique bus stop ID as the grouping field (meaning stop ID #23 creates a line between the real and pseudo stops with ID #23 and no others). This is in Line 113 of the code.

This, to the best of my 6 month old memory, will give you 3D connectors like you see in my previously posted picture. I'll work on a custom tool over the summer and update what I do or do not come up with. Below is the Python code in .py format.

3DNetworkKludge.py.zip

MohamedDarwish

Thank U Jeremiah Nieves for your great post , i really appreciate that
also the research link was really helpful

could you please provide your python code or which tools to create the connector feature class automatically as i have more than 70 route with 1500 bus station