06 · Atmos — Convex Robótica

Atmos - Weather integration API.

Atmos is an API/platform designed to integrate weather stations from different manufacturers into the Convex ecosystem. Its purpose is to receive station data, normalize formats and make data available to platform products.

Role in the system

Environmental context in a common format.

Atmos integrates weather stations from different manufacturers, normalizes units, timestamps and station identification, and makes the data available via API to the Convex products — preserving quality indicators and gaps, never inventing missing measurements.

Modules

Ingestion, normalization, delivery.

The three steps between the reading taken in the field and the data consumed by the Convex products.

STATION

The reading of the installed point

Each station records the variables its sensors measure, at the location where it was installed.

  • Air temperature
  • Wind and gusts
  • Relative humidity
  • Precipitation
  • Pressure

NORMALIZATION

A common format

Units, timestamps and station identification are standardized without losing the origin of the reading.

  • Unit and scale
  • Reading timestamp
  • Station identification
  • Quality indicator

DELIVERY

Available through the API

The products query the same normalized context, with gaps flagged.

  • Latest reading
  • Historical series
  • Explicit periods without reading

Operational flow

From reading to operational context.

Temperature, wind, humidity, precipitation and pressure
  1. 01

    Sensors

    Temperature, wind, humidity, precipitation and pressure

  2. 02

    Ingestion

    Data received through each manufacturer integration

  3. 03

    Normalization

    Units, timestamps and identification standardized

  4. 04

    Context

    Availability via API to the Convex products

  5. 05

    Decision

    Planning and operational windows

API/platform for integrating weather stations from multiple manufacturers.

Station integration

Compatibility depends on manufacturer interfaces and integration validation. Ask about availability for your station; no manufacturer connectors are currently confirmed.

Data normalization

The proposed layer organizes units, timestamps, station identifiers and reading sources into a common format, preserving quality indicators and gaps without inventing missing measurements.

Data for Convex products

The goal is to expose normalized data through an API for Nexa M1, Nexa Vision and Niros as each integration becomes available.

Planned applications

Local data can support analysis, reports and planning in agriculture, livestock, robotics and research, according to reading coverage and frequency.

Reading the diagram

From station to operational context.

The drawing follows the path between measurement, normalization and querying by the products.

API/platform for integrating weather stations from multiple manufacturers.
01

Measured variables

What the installed station reports.

02

Normalization

Step that unifies units, time and identification.

03

Query

Use of the context by Convex products.

Where weather context helps.

Planned applications according to the coverage and reading frequency of each integrated station.

01

Agriculture

  • Operations planning
  • Application windows
  • Area environmental conditions
02

UAV and robotics

  • Mission planning
  • Flight conditions
  • Environmental context for analysis
03

Logistics and field operations

  • Planning based on weather conditions
04

Environmental monitoring

  • Condition logging when supported by the station

Ecosystem integration

The environmental data layer of the Convex architecture.

Atmos provides the weather context that supports Synapse Control planning, Nexa M1 analysis and Niros follow-up, according to the coverage and reading frequency of each station.

  • Data
  • Perception
  • Intelligence
  • Operations
  • Robotics

What the integration delivers.

01

Normalized data

Standardized readings with quality indicators and station origin.

02

API for the products

Availability to Nexa M1, Nexa Vision and Niros as each integration lands.

03

Preserved gaps

Periods without readings stay explicit — nothing is invented.

Limits and status

What Atmos claims.

Atmos integrates stations and normalizes what they measure. Nothing beyond that is stated without a connected station.

Integrable manufacturersPoint-to-point integration, per contractto be defined
VariablesThose measured by the station sensors
FrequencyDefined by the installed station
CoverageOnly areas with an integrated station
GapsPreserved, without interpolation

Frequently asked questions

What Atmos delivers — and what it does not.

Atmos exists to normalize weather data from third-party stations and make it available to the platform.

01Does Atmos collect its own weather data?
No. Atmos receives readings from stations already installed, standardizes units, timestamps and identification, and makes the data available to ecosystem products.
02Which station manufacturers are confirmed?
None as a closed list. Compatibility depends on each manufacturer's interfaces and on validating each integration.
03What happens when a measurement is missing?
Normalization keeps quality flags and gaps. Atmos does not invent a missing reading or interpolate what was not measured.
04Who consumes Atmos data?
Nexa M1, Nexa Vision and Niros, as each integration becomes available.
05Does Atmos issue alerts?
Atmos delivers normalized data through an API. Alerts, operational readings and decisions belong to the products that consume that data.

Operational decisions start from measured conditions, not estimates.