Independent environmental data lab

Environmental data, made inspectable.

Peta Cendekia is a collection of environmental web modules I built to explore how different public datasets can be queried, processed, mapped, and interpreted. Each module uses a different source or method, so this homepage shows the workflow and limitations instead of hiding them behind a generic “AI-powered” label.

8 environmental modules Traceable data sources Explicit limitations
Peta Cendekiamodule layer
ISRIC SoilGridssoil properties
Open-Meteoweather · marine · flood · air
iNaturalistspecies observations
GBIFbiodiversity occurrence
OBISmarine biodiversity
Stormglassmarine · bio
Nominatim / OSMplace search
Provider names indicate technical data provenance, not partnership or endorsement.

Project modules

Eight environmental questions. Different data pipelines.

The modules are not forced into one method. Soil properties, weather forecasts, biodiversity records, river discharge, marine conditions, and air quality each need different sources and different scientific boundaries.

SOIL01

Smart Soil Analysis

Queries modeled soil properties for a selected coordinate and turns the returned layers into an interpretable location profile.

Data sourceISRIC SoilGrids v2.0
coordinateSoilGridssoil profile
Open ↗
AGRO02

Agrometeorology Forecast

Combines location-based forecast variables with crop context and derives a project-specific crop-health index.

Data sourceOpen-Meteo Forecast API
location + cropOpen-Meteoindex + forecast
Open ↗
PEST03

Pest Distribution Map

Retrieves observational occurrence records by crop and location filters, then maps where target pests have been reported.

Data sourcesiNaturalist + GBIF
filtersoccurrence recordsmap
Open ↗
BIO04

Marine Species Occurrence Explorer

Explores marine species records by organism, location, date range, and activity context. It is an occurrence explorer, not an abundance prediction.

Configured sourcesOBIS + GBIF + iNaturalist
organismoccurrence recordsspatial exploration
Open ↗
WAVE05

Marine Weather Analysis

Explores modeled wave and ocean conditions for a selected location, including significant wave height, period, and sea-surface temperature.

Configured sourcesOpen-Meteo Marine + Stormglass
coordinatemarine modelsforecast
Open ↗
FLOW06

River Discharge & Flood Context

Visualizes modeled river discharge and ensemble statistics near a selected coordinate. It does not claim to be a local flood-depth or inundation model.

Data sourceOpen-Meteo Flood / GloFAS
coordinateGloFASdischarge statistics
Open ↗
OCEAN07

Marine Biogeochemistry

Displays modeled biological and oceanographic indicators such as chlorophyll, dissolved oxygen, nitrate, and phosphate.

Data sourceStormglass Bio API
coordinatebio-ocean datacomposition
Open ↗
AIR08

Air Quality Explorer

Retrieves modeled pollutant fields and forecasts for a selected coordinate and presents them as an interactive atmospheric profile.

Data sourceOpen-Meteo Air Quality / CAMS
coordinateCAMSPM2.5 · PM10 · O₃
Open ↗

Method transparency

See what happens between a click and a map.

Choose a module. The panel exposes the input, external data source, backend logic, displayed output, and the scientific boundary that should not be crossed when interpreting it.

Shared architecture

One web architecture, several scientific methods.

The modules share a Laravel application layer, but their scientific content comes from different providers. The website does not manufacture the underlying environmental observations or model fields.

From user request to environmental display

A location, organism, crop, or time filter is sent to a module-specific backend route. Laravel requests the appropriate external service, normalizes the response, applies module logic where needed, and sends the result to the interactive interface.

AI is downstream. Where AI summaries or advice are available, they interpret already-retrieved environmental data. They are not treated as the measurement source.
01
User inputcoordinate · crop · organism · date range
02
Laravel controllermodule-specific request and validation
03
External environmental APISoilGrids · Open-Meteo · GBIF · iNaturalist · OBIS · Stormglass
04
Module logicfilter · normalize · calculate · contextualize
05
Interactive outputmap · chart · profile · optional interpretation

Data provenance

The providers behind the modules.

These names describe where data or geocoding services come from. They do not imply sponsorship, partnership, validation, or institutional endorsement of this project.

ISRIC SoilGrids

Global modeled soil properties

Machine-learning soil-property maps at approximately 250 m, queried by coordinate through the SoilGrids service.

Modeled grid values are not a substitute for a local soil sample; REST availability may vary.

Open-Meteo

Forecast and environmental model access

Used through separate forecast, marine, flood, and air-quality endpoints depending on the module.

Resolution and source models differ by endpoint and location; model output is not a local instrument reading.

iNaturalist

Community biodiversity observations

Provides georeferenced observation records used in occurrence-oriented modules.

Observation density reflects sampling effort; no record does not mean biological absence.

GBIF

Global biodiversity occurrence records

Occurrence search is used to retrieve indexed species records for spatial exploration.

Observation density reflects sampling effort; no record does not mean biological absence.

OBIS

Marine biodiversity occurrence data

Configured as a marine occurrence source for organism-based spatial exploration.

Observation density reflects sampling effort; no record does not mean biological absence.

Stormglass

Marine and biogeochemical API

Configured for marine conditions and biological-oceanographic parameters used by marine modules.

Returned values may combine model/provider sources and should not be presented as laboratory measurements.

Nominatim / OpenStreetMap

Place search and reverse geocoding

Converts place names and coordinates so users can navigate environmental modules spatially.

Reverse geocoding returns the closest suitable mapped object, which may not always match the exact real-world address.

Project-side logic

Derived interpretation

Some modules calculate project-specific indices, filtering, summaries, or optional AI interpretations after the source data are retrieved.

Derived outputs should be distinguished from the original provider data and treated according to their validation status.

Provenance rule

Source ≠ endorsement

Provider and institution names are displayed to make the data chain inspectable.

No provider name or logo should be interpreted as sponsorship, partnership, or approval of Peta Cendekia.
Andifa Anugerah Putra Andifa Anugerah Putra

About this project

Andifa Anugerah Putra

I use Peta Cendekia as a public technical project: a place to build environmental-data modules, compare different data sources, and practice turning scientific information into interfaces that remain inspectable.

The modules are exploratory unless explicitly stated otherwise. They are intended for learning, analysis, and research-oriented prototyping. They do not replace field measurements, local monitoring networks, validated operational models, or professional decision-making.