feat: accept sac_scale=strolling

[koebi]

Pull Request Checklist

• 1. I have rebased the latest version of the main branch into my feature branch and all conflicts
  have been resolved.
• 2. I have added information about the change/addition to functionality to the CHANGELOG.md file under the
  [Unreleased] heading.
• 3. I have documented my code using JDocs tags.
• 4. I have removed unnecessary commented out code, imports and System.out.println statements.
• 5. I have written JUnit tests for any new methods/classes and ensured that they pass.
• 6. I have created API tests for any new functionality exposed to the API.
• 7. If changes/additions are made to the ors-config.json file, I have added these to the ors config documentation
  along with a short description of what it is for, and documented this in the Pull Request (below).
• 8. I have built graphs with my code of the Heidelberg.osm.gz file and run the api-tests with all test passing
• 9. I have referenced the Issue Number in the Pull Request (if the changes were from an issue).
• 10. For new features or changes involving building of graphs, I have tested on a larger dataset
  (at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
• 11. For new features or changes involving the graphbuilding process (i.e. changing encoders, updating the
  importer etc.), I have generated longer distance routes for the affected profiles with different options
  (avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
  points generated from the current live ORS.
  If there are differences then the reasoning for these MUST be documented in the pull request.
• 12. I have written in the Pull Request information about the changes made including their intended usage
  and why the change was needed.
• 13. For changes touching the API documentation, I have tested that the API playground renders correctly.

Fixes # .

Information about the changes

• Key functionality added:
• Reason for change:

Examples and reasons for differences between live ORS routes, and those generated from this pull request

Required changes to ors config (if applicable)

[aoles]

Awesome, thanks a lot for your prompt fix! ❤️

Please note that in case of a change which involves the parsing of OSM tags the corresponding documentation needs to be updated as well 🙈

Also, please consider the minor issue from the comment below.

Cheers! 🚀

[Copilot]

Pull Request Overview

This PR adds support for accepting the sac_scale=strolling tag in OpenStreetMap data for both pedestrian and hiking routing profiles. The SAC (Swiss Alpine Club) scale is used to classify the difficulty of hiking trails, and "strolling" represents the easiest level.

• Added "strolling" as an acceptable SAC scale value for both PedestrianFlagEncoder and HikingFlagEncoder
• Added test coverage for the new functionality in both encoder test classes
• Updated the CHANGELOG to document this feature addition

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
PedestrianFlagEncoder.java	Added "strolling" to the list of suitable SAC scales
HikingFlagEncoder.java	Added "strolling" to the list of suitable SAC scales
PedestrianFlagEncoderTest.java	Added test to verify "strolling" SAC scale is accepted
HikingFlagEncoderTest.java	Added test to verify "strolling" SAC scale is accepted
CHANGELOG.md	Documented the new feature addition

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[koebi]

Adressed both comments, one in the merge from main though^^ I think we can squash and rebase anyways :)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[aoles]

LGTM! 🚀