Routes 是否可以使用HERE路由向via航路点添加航路点ID？

我必须计算一些路线，让8个人坐一辆更大的车（小巴）去上班，下午带他们回家。是否可以向坐标添加ID属性？这将帮助我评估Java代码中的响应，而不是检查坐标（“originalLocation”vs“location”）

例如，像ID4711这样的东西在末尾，用分号分隔

• &via=47.774945410,12.103053452；4711
• &目的地=47.7720259654,12.09511552052；4712

类似于路由V7 API中的UserLabel:[API V7航路点描述]（）。那里的描述是：V8中的航路点：

string，{lat}，{lng}[；name={name}]

我正在这里使用或试验路由API V8。或者在我可以在主页上看到的多个远程通信API中有更多选项吗

我尝试了迁移指南（）中描述的一些方法，但都不起作用

（a） &via=47.7747679928991,12.322371484945947；name=3333

• 返回：

  无效的位置选项。。。。“name=3333”的位置末尾选项出现意外输入

（b） &via=47.82695713017682,12.295106144134037！name=3333

• 返回：

  无效航路点选项

（c） &via=47.82695713017682,12.295106144134037；4711

• 返回：

  地点或航路点选项规范“4711”无效

• …

  参数“via”的值无效

顺便说一句：我知道在API中

• “PlaceOptions”，该选项跟随由semikolon/“；”分隔的坐标；以及
• 用感叹号“！”分隔的“航路点选项”

---

PlaceOptions似乎是固定的指定参数，如course、sideOfStreetHint、stopDuration等，因此我认为WaypointOptions应该是一种选择。但是仍然没有运气。

你是对的，似乎

名称

选项已被删除，迁移指南没有反映这一点。期待着得到开发者支持的回应，也许有一个未记录的选项来标记航路点

根据最新版本（v8.20.1），这些是通过

参数
的所有可用选项：

    A location defining a via waypoint.

    A via waypoint is a location between origin and destination. The route will do a stop
    at the via waypoint.

    Multiple waypoints can also be specified using multiple via parameters like
    `via=...&via=...`, in which case the route will traverse these waypoints sequentially in
    the order specified in the request.

    ## Format

    Format: `Place[WaypointOptions]`

    * Place: `{lat},{lng}[PlaceOptions]`
    * PlaceOptions: `;option1=value1;option2=value2...`
    * WaypointOptions: `!option1=value1!option2=value2...`

    A waypoint consists of:

    * Exactly one place
    * Optional settings for the place
    * Optional settings for the waypoint itself

    Supported place options:

    * `course`: int, degrees clock-wise from north. Indicating desired direction at the place.
      E.g. `90` indicating `east`. Often combined with `radius` and/or `minCourseDistance`
    * `sideOfStreetHint`: `{lat},{lng}`. Indicating the side of the street that should be
      used. E.g. if the location is to the left of the street, the router will prefer using
      that side in case the street has dividers. E.g.
      `52.511496,13.304140;sideOfStreetHint=52.512149,13.304076` indicates that the `north`
      side of the street should be preferred. This option is required, if `matchSideOfStreet`
      is set to `always`.
    * `matchSideOfStreet`: enum `[always, onlyIfDivided]`. Specifies how the location set by
      `sideOfStreetHint` should be handled. Requires `sideOfStreetHint` to be specified as
      well.
      + `always` : Always prefer the given side of street.
      + `onlyIfDivided`: Only prefer using side of street set by `sideOfStreetHint` in case
        the street has dividers. This is the default behavior.
    * `nameHint`: string. Causes the router to look for the place with the most similar name.
      This can e.g. include things like: `North` being used to differentiate between
      interstates `I66 North` and `I66 South`, `Downtown Avenue` being used to correctly
      select a residental street.
    * `radius`: int, meters. Asks the router to consider all places within the given radius as
      potential candidates for route calculation. This can be either because it is not
      important which place is used, or because it is unknown. Radius more than 200meter are
      not supported.
    * `minCourseDistance`: int, meters. Asks the routing service to try find a route that avoids actions for
      the indicated distance. E.g. if the origin is determined by a moving vehicle, the user
      might not have time to react to early actions.

    Supported waypoint options:
    * `stopDuration`: desired duration for the stop, in seconds.
    * `passThrough`: boolean. Asks the router to avoid the following during route calculation:
      + Introducing a stop at the waypoint.
      + Splitting the route into sections.
      + Changing the direction of travel.

      Following scenarios are not supported for `passThrough` parameter:
      + Setting both `stopDuration` to a value greater than 0 and `passThrough=true`.
      + Setting `passThrough=true` for `origin` or `destination` of a route.
      The default value is `false`.

    Notes:

    * Non-structural reserved characters in options' values need to be properly percent-encoded.
      Please refer to the developers' guide for more details.

也就是说，我想您拥有标签的唯一方法就是在Java代码中为每个航路点分配一个标签。
谢谢您的回答。我担心这会使情况/解决方案恶化。是的，我也希望，在V.8中有一些我们不知道但这里的开发人员知道的未记录选项。：-）