-
Notifications
You must be signed in to change notification settings - Fork 3
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
Generate a separate crossing node when generating the crossings #6
Comments
Heya! I recommend using the JOSM With that said, I envision that we'll want a souped-up import workflow at some point that enables greater automation. For example, if OSM data were read in immediately prior to starting the import, and supplied with the download, that node could be pre-created and shared by the street in the uploaded data by default. I'm going to close this for now, but feel free to open up a new issue related to on-the-fly data integration. It's technically out of scope for this project, but could serve as a starting point for an organizational repo. |
Yo! I'm pretty familiar with utilsplugin2. We use it for the sidewalks I was trying it along with the intersections the other night. Sadly it runs into an issue (maybe there is a way around it?) If you pick a single intersection, using i to select the intersecting roads and then Shift+i works no problem, adds a crossing node. But what I was trying to select all the intersections that were autogenerated, and then selecting all of their intersecting ways i. Then when you hit Shift+i, it does add the intersections as expected. Unfortunately it will also grab any power lines or areas that also intersect the roads and ways selected and adds intersections to them as well. Thus it would be superhelpful if the nodes were already there and I just joined them to the road + intersection. I don't think filters helped. Is there a way to not grab more than what we want? |
Hmm. Maybe if I use JOSM in expert mode using the overpass api I can get around this error. |
Provide an option to generate crossing nodes where the crossing intersects with the road. The node can just be a separate point.
Thus in JOSM the user can select these nodes and have them join to the segment if they are acceptable. They should have the tag
highway=crossing
This shouldn't be generated for a crossing if #5 is triggered.
The text was updated successfully, but these errors were encountered: