Cam Monitor Plan System Fuel Flow Dto Structure

SystemFuelFlowDTO schema from Monitor Plan Management OpenAPI Specification

Type: object Properties: 15 Required: 15
GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

SystemFuelFlowDTO is a JSON Structure definition published by EPA — U.S. Environmental Protection Agency, describing 15 properties, of which 15 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

maximumFuelFlowRate systemFuelFlowUOMCode maximumFuelFlowRateSourceCode beginDate beginHour endDate endHour id monitoringSystemRecordId fuelCode systemTypeCode userId addDate updateDate active

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/epa/refs/heads/main/json-structure/cam-monitor-plan-system-fuel-flow-dto-structure.json",
  "name": "SystemFuelFlowDTO",
  "description": "SystemFuelFlowDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "maximumFuelFlowRate": {
      "type": "double",
      "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": {
      "type": "datetime",
      "description": "Date on which information became effective or activity started.",
      "example": "2010-08-01"
    },
    "beginHour": {
      "type": "double",
      "description": "Hour in which information became effective.",
      "example": 12
    },
    "endDate": {
      "type": "datetime",
      "description": "Last date in which information was effective.  This date will be null for active records.",
      "example": null
    },
    "endHour": {
      "type": "double",
      "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 Structure 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 json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure 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 Structure
curl "https://apis.io/api/v1/json-structures/cam-monitor-plan-system-fuel-flow-dto-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?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.