Add docs for pgRouting 4 #411
Merged
+857
−331
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nally equivilent to the legacy version with improved names
…cs are better than that draft file.
Owner
Author
|
I have done a full run through using the D.C. routing example and validated I was able to get to parity with the original docs outcomes. The new instructions for pgRouting 4.0 might have some lingering typos/bugs, but I think getting basic docs out sooner than later is more important than perfect in this case. I'll do more testing in the coming days/weeks, if anyone finds lingering issues feel free to open a new issue and reference this / #408. Thanks to @travishatiw for reporting! |
rustprooflabs
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add docs for pgRouting 4
Reported via #408.
Release Notes
This PR splits routing examples based on pgRouting version to support the substantial change in pgRouting 4.0. The legacy instructions remain in a new subsection under routing making a space for the pgRouting 4 version. PgRouting 4.0 is a major upgrade so I don't expect people will jump to upgrade immediately.
The new pgRouting 4 procedures achieve the same results but tables and column are renamed. Much of the naming in the legacy example was driven by defaults/expectations in the pgRouting functions (that no longer exist). The goal of the renaming is to bring more clarity into the steps and data, hopefully improving the usability of the resulting structures, and making them easier to follow.