SystemFuelFlowDTO

SystemFuelFlowDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name Type Description
maximumFuelFlowRate number Maximum fuel flow rate.
systemFuelFlowUOMCode string Code used to identify the fuel flow units of measure.
maximumFuelFlowRateSourceCode string Code used to identify the source of maximum fuel flow.
beginDate string Date on which information became effective or activity started.
beginHour number Hour in which information became effective.
endDate string Last date in which information was effective. This date will be null for active records.
endHour number Last hour in which information was effective or hour in which activity ended. This value will be null for active records.
id string Unique identifier of a system fuel flow record.
monitoringSystemRecordId string Unique identifier of a monitoring system record.
fuelCode string The type of fuel measured by the system.
systemTypeCode string Code used to identify the type (parameter) of the system.
userId string User account or source of data that added or updated record.
addDate string Date and time in which record was added.
updateDate string Date and time in which record was last updated.
active boolean Flag for active monitor location record
View JSON Schema on GitHub

JSON Schema

cam-monitor-plan-system-fuel-flow-dto-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/epa/refs/heads/main/json-schema/cam-monitor-plan-system-fuel-flow-dto-schema.json",
  "title": "SystemFuelFlowDTO",
  "description": "SystemFuelFlowDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "maximumFuelFlowRate": {
      "type": "number",
      "description": "Maximum fuel flow rate.",
      "example": 30667
    },
    "systemFuelFlowUOMCode": {
      "type": "string",
      "description": "Code used to identify the fuel flow units of measure.",
      "example": "HSCF"
    },
    "maximumFuelFlowRateSourceCode": {
      "type": "string",
      "description": "Code used to identify the source of maximum fuel flow.",
      "example": "URV"
    },
    "beginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which information became effective or activity started.",
      "example": "2010-08-01"
    },
    "beginHour": {
      "type": "number",
      "description": "Hour in which information became effective.",
      "example": 12
    },
    "endDate": {
      "format": "date-time",
      "type": "string",
      "description": "Last date in which information was effective.  This date will be null for active records.",
      "example": null
    },
    "endHour": {
      "type": "number",
      "description": "Last hour in which information was effective or hour in which activity ended. This value will be null for active records.",
      "example": null
    },
    "id": {
      "type": "string",
      "description": "Unique identifier of a system fuel flow record.",
      "example": "WS150071-0C5A8F50F7F24DB8B73E65C18C2063E3"
    },
    "monitoringSystemRecordId": {
      "type": "string",
      "description": "Unique identifier of a monitoring system record.",
      "example": "WS150071-1BCDEDC4D2944376ACA55FCABE9D60A1"
    },
    "fuelCode": {
      "type": "string",
      "description": "The type of fuel measured by the system.",
      "example": "PNG"
    },
    "systemTypeCode": {
      "type": "string",
      "description": "Code used to identify the type (parameter) of the system.",
      "example": "GAS"
    },
    "userId": {
      "type": "string",
      "description": "User account or source of data that added or updated record.",
      "example": "abcde"
    },
    "addDate": {
      "type": "string",
      "description": "Date and time in which record was added.",
      "example": "2009-02-20"
    },
    "updateDate": {
      "type": "string",
      "description": "Date and time in which record was last updated.",
      "example": "2010-09-01"
    },
    "active": {
      "type": "boolean",
      "description": "Flag for active monitor location record",
      "example": true
    }
  },
  "required": [
    "maximumFuelFlowRate",
    "systemFuelFlowUOMCode",
    "maximumFuelFlowRateSourceCode",
    "beginDate",
    "beginHour",
    "endDate",
    "endHour",
    "id",
    "monitoringSystemRecordId",
    "fuelCode",
    "systemTypeCode",
    "userId",
    "addDate",
    "updateDate",
    "active"
  ]
}

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/cam-monitor-plan-system-fuel-flow-dto"
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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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