-
-
Notifications
You must be signed in to change notification settings - Fork 474
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
Add support for node processing in second stage #2252
Conversation
0684645
to
a8ab3fc
Compare
flex-config/public-transport.lua
Outdated
-- Nodes tagged as public transport stops are imported into the 'stops' table, | ||
-- ways tagged as highway or railway or imported into the 'lines' table. The | ||
-- public transport routes themselves will be in the 'routes' table, but | ||
-- without any geomtry. As a "bonus" public transport stop area relations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
geomtry -> geometry
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
flex-config/public-transport.lua
Outdated
end | ||
|
||
function osm2pgsql.process_node(object) | ||
-- Wer are only interested in public transport stops here, and they are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wer -> We
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
This is completely analog to how way processing happens in the second stage. So from the select_relation_member() function in the Lua config file you can now also return a list of nodes that you request to process again. Note that this will only re-process the member nodes themselves, ways which have these nodes as members are not re-processed. Also there is no way to mark member nodes of ways, only member nodes of relations. So this will allow processing, say, stop positions in public transport route relations but not, say, barriers on roads. This change is now possible because we removed support for the old middle format which didn't allow storing the complete nodes (with tags).
a8ab3fc
to
3d52ea8
Compare
This is completely analog to how way processing happens in the second stage. So from the select_relation_member() function in the Lua config file you can now also return a list of nodes that you request to process again.
Note that this will only re-process the member nodes themselves, ways which have these nodes as members are not re-processed. Also there is no way to mark member nodes of ways, only member nodes of relations. So this will allow processing, say, stop positions in public transport route relations but not, say, barriers on roads.
This change is now possible because we removed support for the old middle format which didn't allow storing the complete nodes (with tags).