Output all waypoints as loc parameters, using empty string for missing #384
Conversation
|
This pull request primarily solves the following problem or use case: I want to send someone a link to OSRM, with end coordinates (destination), leaving the start coordinates empty. I want to leave the determination of the start coordinates to the recipient and user: He starts OSRM with my link and then selects the start coordinates himself. This functionality is also useful for operations control centers, for example, which can use it to transmit to the emergency vehicles an OSRM link with destination coordinates. Currently, I can pass several loc parameters to the OSRM frontend. But if the first loc parameter is empty, it is ignored and the next loc parameter that is not empty moves up. This means that the OSRM frontend will then fill the start coordinates with my end coordinates, which I don't want. Here is an example that does not work as desired without this pull request: |
|
Sound reasonable to me. |
What was changed:
Updated the code to output all waypoints as loc parameters.
For any missing waypoints, an empty string is used as the value.
Why:
This ensures that the output always includes the correct number of loc parameters, even if some waypoints are missing, improving compatibility and predictability for downstream consumers.