Swift Navigation · Schema

MsgOdometry

Message representing the x component of vehicle velocity in the user frame at the odometry reference point(s) specified by the user. The offset for the odometry reference point and the definition and origin of the user frame are defined through the device settings interface. There are 4 possible user-defined sources of this message which are labeled arbitrarily source 0 through 3., If using "processor time" time tags, the receiving end will expect either `MSG_GNSS_TIME_OFFSET` or `MSG_PPS_TIME` to sync incoming odometry data to GNSS time. Processor time shall roll over to zero after one week.

CompanyGNSSPrecise PositioningLocationCorrectionsRTKNTRIPRTCMAutomotiveGeospatialIoTRoboticsProtocols

Properties

Name Type Description
tow integer
velocity integer
flags integer
View JSON Schema on GitHub

JSON Schema

MsgOdometry.json Raw ↑
{
  "copyright": [
    "Copyright (C) 2019-2021 Swift Navigation Inc.",
    "Contact: https://support.swiftnav.com",
    "",
    "This source is subject to the license found in the file 'LICENSE' which must",
    "be distributed together with this source. All other rights reserved.",
    "",
    "THIS CODE AND INFORMATION IS PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND,",
    "EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED",
    "WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE."
  ],
  "$schema": "http://json-schema.org/draft-06/schema#",
  "$id": "#MsgOdometry",
  "title":"MsgOdometry",
  "description":"Message representing the x component of vehicle velocity in the user frame at the odometry reference point(s) specified by the user. The offset for the odometry reference point and the definition and origin of the user frame are defined through the device settings interface. There are 4 possible user-defined sources of this message which are labeled arbitrarily source 0 through 3.,\nIf using \"processor time\" time tags, the receiving end will expect either  `MSG_GNSS_TIME_OFFSET` or `MSG_PPS_TIME` to sync incoming odometry data to GNSS time.  Processor time shall roll over to zero after one week.\n",
  "type": "object",
  "properties": {
    "tow": {"type": "integer"},
    "velocity": {"type": "integer"},
    "flags": {"type": "integer"}
  },
  "required": [
    "tow",
    "velocity",
    "flags"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/MsgOdometry"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.