-
Notifications
You must be signed in to change notification settings - Fork 13
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
check input coordinate reference systems, clarify output units in descriptions, and make all entry/exit calculations ellipsoidal #37
base: master
Are you sure you want to change the base?
Conversation
kufreu
commented
Jul 10, 2020
- Addresses issue Check input CRSs #35 by adding checks to see if inputs are in the same projected coordinate coordinate system and are not geographic
- Fixes issue OD Matrix miscalculates time cost if network CRS does not use linear units of meters #36 by making all entry method calculations ellipsoidal and removing the parameter to change the method
- Further clarifies units of inputs and outputs as was requested in issue Clarify time unit #17
…s() for all iso-area algorithms
…riginal data types of the input points and target points
… network algorithms in terms of cost strategy. Update language on maximum cost level.
@kufreu @josephholler thank you for the PRs concerning those issues! I just wanted to ask you to open one PR for each unique issue. This way it is way easier for me to review the associated commits and ensure it is all in the right place. For now just leave the PRs as they are and tell me when they are ready to be reviewed. |
I wondered about that: self-admittedly this is the first time I've tried submitting major changes to another person's GitHub repository. I have to move on to other projects as the summer winds down, though. The pull requests are pretty well organized by different commits: if there are a few changes you don't want, perhaps we could revert those individual commits before you merge? |
Don't worry - the PR is fine as it is. I am very happy to see contributions from other people here. I'll review the commits ASAP so that we can merge the changes. |
I'm trying to use QNEAT3 in QGIS for computing shortest path for my network, but the result is not accurate .I checked the graph and everything is fine but the problem is it didn't detect disconnected nodes! And it show a distance result for them(I need to find out which nodes were isolated) . does anyone have any idea? network after EQ.xlsx My data : 1- line which represent my street after earthquake which caused blocking some segment of the street (I checked the result with QGIS network tool and the results does not compatible to each other) |
@Sohaahm, it's better to ask a question like this as a new issue, or to look for the most related issue to reply to. This thread is for a pull request to modify the code base. |
@kufreu Thanks for this commit, especially regarding the units of outputs. I was always wondering what they were |