Closed dabreegster closed 1 year ago
Will check locally now...
Looking good.
Seems to only be scheme level options and complexity + n. junctions, right?
In any case, good iteration and something we can build on.
Seems to only be scheme level options and complexity + n. junctions, right?
No, the schema describes one single intervention. Each is one of 4 cases, with different details based on the table in the guidance doc. Most of those details are just a complexity field.
I think the key thing is a taxonomy that includes the types of intervention:
Those can be within out existing top level classification of area/route/crossing interventions I think.
Those can be within out existing top level classification of area/route/crossing interventions I think.
Notice this JSON schema doesn't mention area/route/crossing/other. I'm trying to follow exactly the doc's system in this option.
Those can be within out existing top level classification of area/route/crossing interventions I think.
Notice this JSON schema doesn't mention area/route/crossing/other. I'm trying to follow exactly the doc's system in this option.
That's reasonable. Good to be faithful to what's in the guidance for reference.
31
Note the schema isn't written correctly yet; the editor shows an error
Value must validate against exactly one of the provided schemas. It currently validates against 4 of the schemas.
. I think it's because thecomplexity
field is used in all of the enum cases, so the schema can't understand which case we're in. Not worried about figuring out the right way to encode this yet; this is all just illustrative anyway.Also, I only added a few categories from the page. The details in each one are not terribly interesting... instead of making people pick complexity, we should ask more specific questions and auto-calculate complexity from it