Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

remove block_private and block_fords options#3076

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
karussell wants to merge6 commits intocar_road_access
base:car_road_access
Choose a base branch
Loading
fromremove_block_private_options

Conversation

@karussell
Copy link
Member

@karussellkarussell commentedOct 28, 2024
edited
Loading

Second try (#2780).

Now based on#3066.

  • fix TODO NOW
  • move a few things out of this PR like the consistency issue between xy_access & hgv. As well as the small order fix for OSMRoadAccessParser for multiple values separated by;. Also that we replaced OSMHgvParser with OSMRoadAccessParser.
  • do not change the custom model in RouteResourceLeipzigTest.java, instead just change the numbers (after confirming that only the intended custom model changes are sufficient to keep the numbers)

@karussellkarussell changed the titleremove block_private and block_fords optionremove block_private and block_fords optionsOct 28, 2024
Comment on lines 86 to 92
"90,-1,algorithm=" +DIJKSTRA_BI,
"104,-1,algorithm=" +ASTAR_BI,
"33133,1,ch.disable=true&algorithm=" +DIJKSTRA,
"22497,1,ch.disable=true&algorithm=" +ASTAR,
"15434,1,ch.disable=true&algorithm=" +DIJKSTRA_BI,
"10926,1,ch.disable=true&algorithm=" +ASTAR_BI
})
Copy link
MemberAuthor

@karussellkarussellOct 28, 2024
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The visited nodes would change with a custom profile that excludes "car_road_access == PRIVATE" too, becauseaccess=customers will be now excluded too. But in general this is more correct and we don't want to separate this from PRIVATE for now. So just change the numbers.

setEncodedValuesString("car_access, car_average_speed").
setProfiles(TestProfiles.accessAndSpeed("profile","car")).
setEncodedValuesString("car_access, car_average_speed, road_access").
setProfiles(carAccessAndPrivateAndSpeed("car")).
Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@easbar as the new default forcar_access is without the private exclusion, I would prefer to just adapt the numbers in the tests instead of creating a custom profile like I did here (preliminary) with the private exclusion. Does this make sense for you too?

…s and make xy_access&hgv encoded values more consistent to each other
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@karussell

[8]ページ先頭

©2009-2025 Movatter.jp