This diagram shows multiple data paths for converting data from multiple sources through components in an Oracle Cloud Infrastructure region to usable location insights for data consumers.
A linear sequence of steps spans the diagram:
- Analyze, Predict & Measure
- Measure & Act
The following components apply to the entire Oracle Cloud Infrastructure region:
- Governance (Data Catalog)
- Security, Identity, and Access Management
The region is divided into functional layers that house physical or functional components:
- Data Sources layer: Data sources include Applications, Files, and Reference
Geo-data. Data can follow a number of paths:
- Data moves directly into batch processing in the Data Refinery layer using database tools provided by Oracle Autonomous Data Warehouse or using Oracle Cloud Infrastructure Data Integration for complex ETL scenarios. Data then moves into Geocoding, Enriching and then goes to ADW.
- Data moves into Spatial Data Loading in the Data Refinery layer using Oracle Spatial Studio. From there it goes to ADW.
- Data Refinery layer: Two blocks labeled Batch Processing (Autonomous DB Tools) and Batch Processing (Oracle Cloud Data Integration) handle input data from applications and files. Data from these blocks moves to a block labeled Geocoding, Enriching (Spatial Studio). Data from Reference Geo-data moves to a block labeled Spatial Data Loading (Spatial Studio).
- Data Persistence Platform layer: A block labeled Serving (ADW) handles input data from Geocoding, Enriching (Spatial Studio) and Data Loading (Spatial Studio).
- Access and Interpretation layer: Data moves to a block labeled Spatial Analysis and Visualization (Spatial Studio) and Low Code App Dev (APEX) and then on to data consumers and applications.