Workflows begin with inputs that bring data into your analysis pipeline. Input blocks define where your data comes from and make it available for processing blocks downstream.
Input Block Types
Atlas provides six input blocks organized into Import and Integration categories:
- Dataset - References existing project datasets uploaded to your workspace
- Satellite Import - Imports satellite imagery from providers like Sentinel and Landsat
- API Import - Fetches data from external web services and APIs
- AOI Input - Defines interactive area of interest parameters for workflow users
- OpenStreetMap - Imports features from OpenStreetMap based on tags and location
- Overture Maps - Imports features from Overture Maps Foundation datasets
Adding Input Blocks
Open the Blocks panel and locate the Import or Integrations category. Drag an input block onto the canvas to begin building your workflow.
Drag datasets directly from the Layers Panel onto the workflow canvas. This automatically creates a Dataset block configured to reference that project data.
Input blocks always appear at the start of workflows since they provide the raw data for processing. Connect their output ports to processing blocks to begin transforming data.
Dataset Inputs
The Dataset block references data already uploaded to your project. This is the most common input method for workflows that process existing project data.
Click the Dataset block to open settings and select which project dataset to use. The block outputs all features and attributes from the selected dataset.
Dataset blocks update automatically when you modify the source data in your project. Changes propagate to all workflows using that dataset.
Satellite Imagery Inputs
The Satellite Import block fetches imagery from satellite providers. Configure the provider, date range, cloud coverage limits, and area of interest.
Satellite inputs work best when combined with AOI Input blocks. This lets workflow users specify custom locations when running the workflow.
The block outputs raster data that you can analyze with processing blocks like Calculate Raster Statistics or Raster Calculator.
API Inputs
The API Import block retrieves data from external web services. Configure the API endpoint URL and any required authentication or parameters.
API inputs enable workflows to fetch fresh data from external sources each time they run. This keeps analysis current without manual data updates.
The block parses JSON responses and converts geographic data to features you can process with other blocks.
Area of Interest Inputs
The AOI Input block creates interactive parameters where users draw or select geographic boundaries. This makes workflows flexible for different locations.
Configure whether users draw polygons, select from existing features, or upload boundary files. The block outputs the defined area as a polygon feature.
Connect AOI outputs to processing blocks that need location context like spatial filters, satellite imports, or intersection operations.
OpenStreetMap Integration
The OpenStreetMap block imports features based on location and OSM tags. Configure which feature types to import using tag filters like building, highway, or amenity.
Specify the search area using a connected AOI Input or by setting coordinates directly. The block fetches current OSM data and outputs features with their attributes.
OSM integration provides free access to global infrastructure, building, and points of interest data for your workflows.
Overture Maps Integration
The Overture Maps block imports curated geospatial data from the Overture Maps Foundation. Select feature themes like buildings, transportation, or places.
Configure the geographic area and any attribute filters to narrow results. The block outputs features with standardized schemas designed for analysis.
Overture data offers quality-controlled features derived from multiple sources including OSM and commercial providers.
Configuring Inputs
Click any input block to open its settings panel. Required parameters appear highlighted until you provide values.
Most input blocks need geographic bounds defined. Either connect an AOI Input block or specify coordinates in the settings.
Test input configurations with small areas first. This verifies settings work correctly before processing large volumes of data.
