Skip to content
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

Crossings #19

Open
dabreegster opened this issue Mar 15, 2023 · 6 comments
Open

Crossings #19

dabreegster opened this issue Mar 15, 2023 · 6 comments

Comments

@dabreegster
Copy link
Collaborator

I'm thinking through https://github.com/acteng/schema/blob/main/schemas/crossings.json (plus the changes in Robin's current PR) so far.

Part of Brian's crossing scoring guide that I vaguely remember was "does this match the desire line of pedestrians"? A flagrant violation I remember spotting last time in Leeds is https://www.openstreetmap.org/way/34430463. Should we consider adding a boolean here to capture this? (Let's not yet worry about the question of how we fill it out for pre-existing crossings or plans submitted without this judgment.)

And also, can we define PCU?

@dabreegster
Copy link
Collaborator Author

For signalized crossings...

  • does somebody need to press a beg button manually? (https://www.openstreetmap.org/node/6339483802 is an example where the answer is yes -- and it's kind of annoying!)
  • is there a maximum time between pressing a beg button and getting the walk signal?
  • is the signal auto-activated by a sensor detecting people waiting?
  • once the signal is on, how long is the green man there?

@dabreegster
Copy link
Collaborator Author

It's hopefully always true, but does the crossing have appropriate ramp/slope in all places? Whether it's a kerb cut, or the crossing itself a raised bit of pavement.

@dabreegster
Copy link
Collaborator Author

(Possibly a good question for the inspections team -- when they audit in person or look at plans online, is there a checklist of things they look for? If there's anything written up somewhere, this can directly tell us if we're missing some details!)

@dabreegster
Copy link
Collaborator Author

Geometrically, what do we want to see for crossings? I remember an argument for encouraging just a point in ATIP, for simplicity. In OSM, we usually have line-strings. Width of the crossing also matters, from personal experience -- do we want min/max/average width as an attribute, or perhaps a more detailed polygon sometimes?

@Robinlovelace
Copy link
Contributor

All good questions. Some of this may be out of scope for the schema, which will be a balance between detail and ease-of-use, but all really interesting thoughts that I'm sure the inspections team will have some thoughts on.

@robinlovelace-ate
Copy link
Contributor

From Inspections team:

Four broad types:

-Grade separated

-Signalised (pegasus, puffin & toucan)

-Priority (zebra, school (?) and parallel)

-Uncontrolled (refuges, dropped kerbs, tactiles)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants