Beacon has a new job. Every evening it must send a photo of each greenhouse bed back to mission control.
Comet queues up the first batch and taps send. The progress bar barely moves.
"The relay is slow tonight," she groans. "At this rate the tomatoes will be ripe before the photos arrive."
Wren studies one photo grid. "What do you notice? Half of this picture is the same white wall, square after square."
Nova hovers beside the screen. "Repeated data is a clue," she says. "Ask what you really need to send."
Comet stops tapping. "So we do not need a faster relay. We need smaller photos."
Wren nods. "Smaller, but still useful to the plant team."
Data compression can reduce the size of data that is stored or sent. Size here means the number of bits.
Fewer bits does not always mean less information. A shorter way of writing can keep every detail.
How much data shrinks depends on two things: how much repetition, or redundancy, the data has, and which compression algorithm is used.
A photo with large patches of the same color has lots of redundancy. A busy, speckled photo has less.
Lossless compression usually reduces the number of bits and still lets you rebuild the original exactly.
Lossy compression can greatly reduce the number of bits, usually more than lossless compression. But you can only rebuild an approximation of the original.
Here is an analogy, not a rule: think of a packed suitcase. Lossless is like folding everything neatly. Lossy is like leaving a few things behind.
| Statement | True or false? |
|---|---|
| Lossless compression lets you rebuild the original exactly. | ? |
| Lossy compression lets you rebuild the original exactly. | ? |
| Lossy compression usually shrinks data more than lossless compression. | ? |
| Data with lots of repetition is a good fit for compression. | ? |
| Compression always throws away some information. | ? |
Good thinking, developer. Tomorrow you will clean up the Beacon log.