Upgrade GraphHopper to newest version #1
Conversation
This file contains 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
TheNewCivilian
force-pushed
the
master
branch
8 times, most recently
from
65dd661
to
5d8e84c
Compare
* These tests no longer seem to fail when we revert the corresponding fix (set precision in DijkstraBidirectionCH to 0) * There is still testStallOnDemandViaVirtuaNode_issue1574 which describes the problem in more detail anyway
I was not able to reproduce this old bug by reverting the corresponding change in QueryOverlayBuilder, so it's impossible to keep it reproducible like this -> simply removed it for now. The problem should be covered by our randomized tests (but I was not able to find a new example on the quick)
Github packages cleanup try
* heading_penalty parameter should be picked and properly merged for custom weighting too * remove shortest weighting * keep ShortestWeighting in jar * keep default constructor * fix imports * fix imports * comments from review * changelog --------- Co-authored-by: easbar <easbar.mail@posteo.net>
* Use a different action * Change the version
* use WebApplicationException * Set message for MultiException * Do not log server-side stack trace when ghResponse has errors * type=gpx seems to be only supported for GET; return XML content if there is an error * use different media type * add logging but to info and no stacktrace * log not twice. for POST we implicitly use MultiExceptionMapper --------- Co-authored-by: easbar <easbar.mail@posteo.net>
* heading_penalty parameter should be picked and properly merged for custom weighting too * remove shortest weighting * remove fastest weighting * merged remove_shortest * removed classes PriorityWeighting and ShortFastestWeighting * cleanup * removed CustomProfile class * remove old CustomProfile usage * Minor changes during review * review * handle wheelchair problem later * updated profiles.md * now no need for a third run with weighting=custom --------- Co-authored-by: easbar <easbar.mail@posteo.net>
* query weighting should use the turn times (not weights) given by the actual weighting * related: da748e6
* Improvement for bicycle speed for designated path with tracktype * Update core/src/main/java/com/graphhopper/routing/util/parsers/BikeCommonAverageSpeedParser.java Co-authored-by: Peter <graphhopper@gmx.de> * Remove a new test which passes without the improvement --------- Co-authored-by: Peter <graphhopper@gmx.de>
* initial commit * make configurable also per request * make tests passing: disable TC customization if no orientation EV * move turn cost provider into CustomWeighting and clean up * clean up * remove TODO NOW * use same name as in config: turn_costs; add path detail; increase min to +-25° * bug fix for alternative_route * fix: plus u_turn_costs * test fix * minor fixes * minor optimization * use 0 cost as default * minor fixes * test fix * remove checkTurnCostConfigForLM; better and possible to use double not Double * use conditional instead inheritance * private * for now do not include turn_costs path detail and add it later on to support indicated that only a single coordinate is affected * make left/right min-max symmetric * use separate, less tested custom model * fix min_left_angle config * additional xy_sharp values * easy to forget left_sharp config. ensure that left_sharp >= left (same for right) * use degrees for orientation * use more common north-based angle. still keep orientation as name. Later change calcOrientation and related to xAxisAngle * make consistent: use postfix _costs. rename max_angle to min_u_turn_angle and return u_turn_costs instead of infinity * simplify DefaultTurnCostProvider * comment * in test: differentiate between sharp and non-sharp * plural in java like in config * missing
* JSR-305 is currently 'dormant' https://jcp.org/en/jsr/detail?id=305
* upgrade to dropwizard 3.0.5 as older will be unsupported * Add hanging test * remove GH * fixed in 3.0.6? * Update Dropwizard to 3.0.8 * We need to close the client * see https://hc.apache.org/httpcomponents-client-5.3.x/migration-guide/preparation.html * Remove test --------- Co-authored-by: easbar <easbar.mail@posteo.net>
* Allow decimal speeds to be parsed * Corrected order of contributors and modified decimal test
* Add support for bike mtb:scale accessability * Only allow mtb:scale 0 or 1 and lower for trecking & racebikes, and support "+" and "-" values * Revert "Only allow mtb:scale 0 or 1 and lower for trecking & racebikes, and support "+" and "-" values" This reverts commit 4b6a117. * Revert "Add support for bike mtb:scale accessability" This reverts commit 2b75aa7. * Add support for mtb:scale as custom model * Move sac_scale handling for bicycles to bike custom models * Change comment in custom models to real EV name as dedected in review
* fix to be able to import and run as server on different machines * update CONTRIBUTORS.md
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.
No description provided.