mrfylke / hwb-standard

MQTT topic and payload specification for Sales Client Hardware Integration for Buses in Norway

https://hwb.developer.frammr.no/

Other

0 stars 0 forks source link

spec: Propose specification: Location #1

Closed mikaelbr closed 1 year ago

mikaelbr commented 1 year ago

Proposal: Location

Retrieve location data periodically.

Fixes #2

Context and known limitations

Specified as a subset of Ruter Location but with local MQTT (no specifying operator and vehicle). Mainly support for lat, lon, and date.

Has no configuration like interval or format.

Checklist

[x] Includes documentation file with description, topics, and examples.
[x] Includes JSON Schema
[x] Includes passing and failing tests.

Confirmed and verified by parties

[x] MT Buss
[ ] Consat
[x] Fara

mikaelbr commented 1 year ago

[x] Add fields about accuracy and ability to say something about quality (additional fields).
[x] Information on movement.

Check with Consat on complete Ruter location JSON Schema

mikaelbr commented 1 year ago

Add note on standard interval. 1 per sec.

Max once

mikaelbr commented 1 year ago

Information: Ruter has an unmerged breaking change in how to handle Location in what they call adt v3. To be future proof and match Ruter I've updated this proposal to match Ruters new Location specification.

Primary changes:

Added required fields traceId, messageNumber and eventTimestamp (see description in schema)
Removal of latitudeDirection and longitudeDirection
Change topic to /sensors/location

daniil-pastuhov commented 1 year ago

:thumbsup: (MtBus)

NilsAndreasT commented 1 year ago

MT-Buss approves.

mikaelbr commented 1 year ago

@Topguy comments?

Thorbear commented 1 year ago

Approved by Fara, with the new adt v3 changes.

mikaelbr commented 1 year ago

Considering it approved and doing separate flow with Consat for now.