-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meaning of the FIRST THRU NODE header #33
Comments
It concurs with my understanding. I think those 'non-thru nodes' represent the center of residential/commercial blocks, while all other 'thru nodes' represent physical intersection of roads. |
Thanks, I appreciate the help |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in #29: There is a simple relationship between nodes and zones, that is, a zone is a node. You mention regarding the
FIRST THRU NODE
property:This suggests the following to me: If
FIRST THRU NODE = 1
, ignore the property, otherwise: The zones 1, ..., n are forbidden, which is to say that no traffic may pass through them. I would assume that this implies that no path of edges in any of the trips is allowed to touch any of the nodes 1,...,n.Now I looked at the
Anaheim
net file, which specifies theFIRST THRU NODE
to be 39, implying that no traffc may pass through nodes 1,...,38.The problem is that all trips in the corresponding [trip file](https://github.com/bstabler/TransportationNetworks/blob/would mean that any path has to contain nodes 1,..., 38.
I therefore think that the
FIRST THRU NODE
excludes nodes from being contained in a path except for the origin / destination of the path, hence theTHRU
name. So paths can contain forbidden nodes as long as they connect them.Is this a correct understanding of the
FIRST THRU NODE
entry?The text was updated successfully, but these errors were encountered: