MonitorSpanDTO

MonitorSpanDTO schema from Monitor Plan Management OpenAPI Specification

GovernmentEnvironmentalOpen DataAir QualityWater QualityHazardous WasteComplianceEmissions

Properties

Name Type Description
componentTypeCode string Code used to indicate the component type.
spanScaleCode string Code used to identify the span scale.
spanMethodCode string Code used to identify the method used to calculate MPC/MEC/MPF.
mecValue number The Maximum Expected Concentration (MEC) value reported in the SO2 and NOx span records.
mpcValue number The Maximum Potential Concentration (MPC) value reported in the high scale record for NOx, SO2, or CO2.
mpfValue number For parameter FLOW, report the Maximum Potential Flow (MPF) value for the monitoring location in (scfh) on a wet basis.
spanValue number The Span Value determined according to the requirements of Part 75 or (if applicable) 40 CFR Part 63, Subpart UUUUU.
fullScaleRange number Full scale range in units of daily calibration for SO2, NOx, CO2, O2, HCl, and flow rate, must be greater than or equal to the span value.
spanUnitsOfMeasureCode string Code used to identify the calibration units of measure.
scaleTransitionPoint number If a dual range analyzer is installed for NOx, SO2 or CO2 (see ANALYZER RANGE DATA), report the concentration value at which the DAHS switches from recording on the normal range to recording on the se
defaultHighRange number The default high range value must be 200 percent of the maximum potential concentration, only reported if the high scale record for the parameter.
flowSpanValue number The product of the MPF and a factor no less than 1.00 and no greater than 1.25. Flow rate span value in scfh.
flowFullScaleRange number The actual full-scale range value expressed in units of scfh for the parameter FLOW, must be greater than or equal to the flow rate span value
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. This value will be null for active records.
id string Unique identifier of a monitoring span record.
locationId string Unique identifier of a monitoring location record.
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-monitor-span-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-monitor-span-dto-schema.json",
  "title": "MonitorSpanDTO",
  "description": "MonitorSpanDTO schema from Monitor Plan Management OpenAPI Specification",
  "type": "object",
  "properties": {
    "componentTypeCode": {
      "type": "string",
      "description": "Code used to indicate the component type.",
      "example": "SO2"
    },
    "spanScaleCode": {
      "type": "string",
      "description": "Code used to identify the span scale.",
      "example": "H"
    },
    "spanMethodCode": {
      "type": "string",
      "description": "Code used to identify the method used to calculate MPC/MEC/MPF.",
      "example": "HD"
    },
    "mecValue": {
      "type": "number",
      "description": "The Maximum Expected Concentration (MEC) value reported in the SO2 and NOx span records.",
      "example": 156.9
    },
    "mpcValue": {
      "type": "number",
      "description": "The Maximum Potential Concentration (MPC) value reported in the high scale record for NOx, SO2, or CO2.",
      "example": 177.2
    },
    "mpfValue": {
      "type": "number",
      "description": "For parameter FLOW, report the Maximum Potential Flow (MPF) value for the monitoring location in (scfh) on a wet basis.",
      "example": 8563000
    },
    "spanValue": {
      "type": "number",
      "description": "The Span Value determined according to the requirements of Part 75 or (if applicable) 40 CFR Part 63, Subpart UUUUU.",
      "example": 200
    },
    "fullScaleRange": {
      "type": "number",
      "description": "Full scale range in units of daily calibration for SO2, NOx, CO2, O2, HCl, and flow rate, must be greater than or equal to the span value.",
      "example": 200
    },
    "spanUnitsOfMeasureCode": {
      "type": "string",
      "description": "Code used to identify the calibration units of measure.",
      "example": "PPM"
    },
    "scaleTransitionPoint": {
      "type": "number",
      "description": "If a dual range analyzer is installed for NOx, SO2 or CO2 (see ANALYZER RANGE DATA), report the concentration value at which the DAHS switches from recording on the normal range to recording on the secondary range (usually low to high). Report this value in both the low and high scale records. Scale transition point is not reported for FLOW, HCl, and Hg span.",
      "example": 200
    },
    "defaultHighRange": {
      "type": "number",
      "description": "The default high range value must be 200 percent of the maximum potential concentration, only reported if the high scale record for the parameter.",
      "example": null
    },
    "flowSpanValue": {
      "type": "number",
      "description": "The product of the MPF and a factor no less than 1.00 and no greater than 1.25. Flow rate span value in scfh.",
      "example": null
    },
    "flowFullScaleRange": {
      "type": "number",
      "description": "The actual full-scale range value expressed in units of scfh for the parameter FLOW, must be greater than or equal to the flow rate span value",
      "example": null
    },
    "beginDate": {
      "format": "date-time",
      "type": "string",
      "description": "Date on which information became effective or activity started.",
      "example": "2018-05-17"
    },
    "beginHour": {
      "type": "number",
      "description": "Hour in which information became effective.",
      "example": 14
    },
    "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.  This value will be null for active records.",
      "example": null
    },
    "id": {
      "type": "string",
      "description": "Unique identifier of a monitoring span record.",
      "example": "MRHODES16-A5DBB8DF4F1D4D3A95AD2553008EB554"
    },
    "locationId": {
      "type": "string",
      "description": "Unique identifier of a monitoring location record.",
      "example": "5770"
    },
    "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": "2009-02-20"
    },
    "active": {
      "type": "boolean",
      "description": "Flag for active monitor location record",
      "example": true
    }
  },
  "required": [
    "componentTypeCode",
    "spanScaleCode",
    "spanMethodCode",
    "mecValue",
    "mpcValue",
    "mpfValue",
    "spanValue",
    "fullScaleRange",
    "spanUnitsOfMeasureCode",
    "scaleTransitionPoint",
    "defaultHighRange",
    "flowSpanValue",
    "flowFullScaleRange",
    "beginDate",
    "beginHour",
    "endDate",
    "endHour",
    "id",
    "locationId",
    "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-monitor-span-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.