-
Notifications
You must be signed in to change notification settings - Fork 6
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
Docs overhaul for Transportation theme #14
Conversation
18ed7b2
to
86c5e22
Compare
Roads page is finally done. Travel modes is the last one up. |
16a28e4
to
49510fc
Compare
Most of the work is done on the `scoping-rules.mdx` page, but note that some stuff is either (a) commented out; or (b) inaccurate because of detects I found and documented while writing up this page. Here are some of the problems: - Lanes model: https://github.com/OvertureMaps/schema-wg/issues/148 - General issues: https://github.com/OvertureMaps/schema-wg/issues/147 - Environmental: OvertureMaps/schema-wg#146 - Flags: OvertureMaps/schema-wg#144
1392e08
to
a902483
Compare
PR is 100% complete, all pages are ready for review. |
a902483
to
d6801d7
Compare
Having finished the combobulator updates, I'm planning to come back to this tomorrow or Friday, with a goal of having a shippable update by mid-week next week. In addition to Larry, Sanjib, and Ola's feedback on this PR, I have a list of update points and suggestions from Rob S. to work in.... |
The https://github.com/OvertureMaps/schema-wg/ repository seems to be set to private. |
Yes that's correct. Overture's still maturing as an organization and we are still working out how some of our process will work. I believe the plan is to change this at some point in the future as our process gets more formalized... |
This commit is based on a feedback email to me from [email protected]. Thanks Rob!
1e71ea1
to
e922733
Compare
This commit incorporates changes suggested or implied by Ola and Larry on the PR: #14.
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.
I have one question around implied restrictions that I think is particularly unclear with a proposed change depending on what restrictions are implied.
Also, we may want to as future work create guidelines around examples as there are at least 3 different ways we have represented coordinates, namely:
coordinates: [[0, 0], [1, 1]] #TODO get some real geometry
--OR--
coordinates:
- [-123.13174398677468, 49.28492173297815]
- [-123.13015725772073, 49.283923094445726]
--OR--
coordinates:
- - -123.12244656918179
- 49.280940587393815
- - -123.12562968007902
- 49.27884862879665
Its a minor point, but I did find it jarring for side-by-side examples that I think distract from the actual difference the examples are trying to illustrate.
This is something I think we should address as an overarching schema TF issue relating to docs quality and documentation strategy. I'll cut an issue. |
examples/transportation/docusaurus/turn-restriction-01-source.yaml
Outdated
Show resolved
Hide resolved
examples/transportation/docusaurus/access-restriction-04-axle-limit.yaml
Show resolved
Hide resolved
This commit incorporates changes suggested or implied by Ola, Larry, and Sanjib on the PR: #14.
b6af8fb
to
0731c60
Compare
This commit incorporates changes suggested or implied by Ola, Larry, and Sanjib on the PR: #14.
0731c60
to
48a2a89
Compare
Merging it. Woooooo! 🎉 |
Description
This PR updates the theme-level Transportation documentation in the Docusaurus website to be more complete, more detailed, while hopefully telling a more approachable story.
using
,recognized
, ormode
/modeNot
to use in a given circumstance.The overall transportation theme index page is also updated with new text, and treated as more of an introduction linking out to sub-pages for detailed explanations.
Testing
#links
) and out-of-website links to OSM to the best of my ability.Callouts