Route Exchange Model - UxS Support

opengeospatial / ogcapi-routes

public repo for OGC API - Routes Standards Working Group

Other

10 stars 3 forks source link

Route Exchange Model - UxS Support #67

Open thanchevici opened 1 year ago

thanchevici commented 1 year ago

Hello everyone,

I took a stab to upload the route exchange model to get more support for UxS. In a nutshell I added contingency, and loiter, as well as refactored restrictions and attributes.

Let's discuss this next meeting. Route

attached is the EA file as well. route.zip

Best regards, Teodor

teohan commented 1 year ago

I think the concept of action needs to be flushed out a bit more. here is a different suggestion:

Route

{
   "title":"Task",
   "type":"object",
   "properties":{
      "name":{
         "title":"Name",
         "type":"string"
      },
      "description":{
         "title":"description",
         "type":"string"
      },
      "constraints":{
         "$ref":"file:///TaskConstraints.json"
      },
      "action":{
         "$ref":"file:///TaskAction.json"
      }
   },
   "required":[
      "description",
      "constraints",
      "action"
   ],
   "additionalProperties":false,
   "$id": "file:///Task.json"
}

{
    "title": "TaskConstraints",
    "type": "object",
    "properties": {},
    "$id": "file:///TaskConstraints.json"
}

{
    "title": "TaskAction",
    "type": "object",
    "properties": {},
    "$id": "file:///TaskAction.json"
}

teohan commented 1 year ago

Hi,

here is the last model and suggestion. route.zip Route Best regards, Teodor

cportele commented 1 year ago

Meeting 2022-12-13:

Attributes of route components: @cportele will investigate whether we can reduce the attributes to those that apply for (almost) all routes. Additional attributes can be added by anyone. Specific attributes could perhaps be required or specified by the relevant requirements class (e.g., weight restrictions).
Actions (maybe a better term than "task") are orthogonal to routing. It is already possible to connect actions (or other data) to waypoints. We will add informative text in 1.0 that actions can be associated with waypoints. This is future work when there is a agreed model for actions, normative text could be added in a future revision.

thanchevici commented 1 year ago

@cportele Attached is the model with following changes:

task is called action
UML is fixed (composition arrows are corrected)

Route

Model: route.zip

cportele commented 1 year ago

RouteOverview:

maxHeight and maxWeight can be added/specified by the respective conformance classes of the API.
duration is general and should be kept (as an optional attribute, see #35).

RouteSegment:

maxHeight, maxWeight and duration as above
For the other attributes (roadName, speedLimit): Maybe we should couple these to the modes. E.g., these are for motor vehicles?