-
Notifications
You must be signed in to change notification settings - Fork 12
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
route overview (main.ipynb) #35
Comments
When refactoring the code to reproduce the graphs, I noticed that the query Elevation Profile (stage) uses is:
However, in our case we do not have a column called id in our database. I was wondering if it is possible to know what the column id stored previously |
i think it was the first column. but don't use those queries (the old code converts sequel queries into python - which is dumb). read the values direcly from route_model_df (it's much cleaner).
|
Okay, and for the graphs is there anything I can compare it to? Should it look similar to the output of the previous code? |
It should look similar to the output of the previous code. Totally your call though!
On Oct 22, 2024, at 2:28 PM, Raiyan Aaijaz ***@***.***> wrote:
Okay, and for the graphs is there anything I can compare it to? Should it look similar to the output of the previous code?
—
Reply to this email directly, view it on GitHub<#35 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWXZTPFN2NMTPMRUMPYBTN3Z42KMZAVCNFSM6AAAAABQEZAWUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZHE3DOMJUGE>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Planning on completing the issue by 10/27/2024 |
You should be able to setup route_model table in a postgresql database by running route_model.py (you will have to create database manually tho). Then using functions in db_fetch.py you should be able to load data to memory. Then simply refactor the code to reproduce the following three graphs.
Distance (Stage)
Elevation Profile (Stage)
Elevation Profile (Total)
The text was updated successfully, but these errors were encountered: