D8LooP - Practise Data Engineering

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

You've joined CropSense, an ag-tech company. Soil sensors report hourly — and go offline during storms, then send backlogs with overlapping timestamps. Agronomists need a clean hourly series per field, ignoring clearly bad readings without discarding everything when one sensor misbehaves.

your model must answer

01The current recommended irrigation duration for a given field, based on the latest clean hourly readings?
02An hourly moisture and temperature series for a field over the last week, with gaps filled only from reliable sensors?
03By field and season, total irrigation time, estimated water saved, and yield per hectare?

out of scopeForecasts · valve control · soil chemistry · disease models · imagery

This exercise’s brief could not be loaded.The guided questions and their model answers come from the review service. It looks like it is not reachable — start it with pnpm dev:api and reload.The canvas below still works, so you can model now and run the review once the service is up.

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

You built the model in the Studio. Now defend it.Fields, sensors, and missing readings

Design review

The reviewer reads your model.

Preparing your workspaceloading the brief, studio & canvas…

buyersellerlistingorder

SCENARIO

your model must answer

01The current recommended irrigation duration for a given field, based on the latest clean hourly readings?
02An hourly moisture and temperature series for a field over the last week, with gaps filled only from reliable sensors?
03By field and season, total irrigation time, estimated water saved, and yield per hectare?

out of scopeForecasts · valve control · soil chemistry · disease models · imagery

Build starts here

The brief becomes the left drawer. The canvas stays the build surface.Study is done above. Build the tables here, hit review to validate, then use follow-ups to defend the model.

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

Start with the data model, then layer system context

Use entities and relationships for the real ERD. Add notes, containers, or curated cloud shapes only when they sharpen the story you are architecting.

68%

You built the model in the Studio. Now defend it.Fields, sensors, and missing readings

Design review