Not the New Year kind. Resolution, in the everyday sense, is how finely you can see something. And like trust, it's one of those ideas we handle constantly without ever thinking about it, until the moment the detail we needed turns out not to be there.
We choose our resolution all day long
Open a map and you're making a resolution decision before you've gone anywhere. Zoomed right out, New Zealand is a pair of islands and the drive from Christchurch to Timaru is a fingernail; zoom in and suddenly there are street names, one-way systems, the cafe you're actually looking for. The same trade-off runs through everything: the weekly forecast tells you whether to plan the fencing job while the hour-by-hour one tells you when to put the tools down, and your bank balance is the low resolution view of your finances while the transaction list is the high resolution one. Neither view is wrong, they answer different questions, and more detail isn't automatically better. Good resolution isn't maximum resolution. It's the level of detail that matches the question you're asking.
What resolution means in instrumentation
In measurement, resolution has a precise definition: the smallest change in a quantity that an instrument can detect or display. A bathroom scale reading to 0.1 kg has a resolution of 0.1 kg. A thermometer marked in whole degrees can't tell you about the half degree in between.
Here's the part that catches people out. Resolution is not accuracy. That bathroom scale might display your weight to a crisp 0.1 kg and still be 2 kg off. Accuracy is how close a reading is to the true value. Resolution is just how finely the instrument slices what it thinks it sees. An instrument can be confidently, precisely wrong to three decimal places. The extra digits don't make the number more true, they just make the error better dressed.
Which is why, in our world, resolution and verification belong in the same conversation. Resolution decides how much detail a meter reports. Verification, against a certified reference instrument, is what tells you whether that detail can be believed.
Where resolution shows up in flow metering
A flow meter isn't one resolution decision, it's several stacked on top of each other, and each one shapes what the data can and can't tell you.
The totaliser display. Every meter rounds somewhere. A totaliser that can only display whole cubic metres can't show you the 400 litres that trickled through overnight; the display simply has no digits for them. For a large municipal bulk main that might be fine. For a small take, a display limited to whole cubic metres might hide exactly the behaviour you care about.
The pulse output. Many meters pass their reading onward as pulses, with each pulse representing a fixed volume: one litre, ten litres, a hundred, a thousand. That pulse value is a resolution setting, and it's one of the most common things we find configured poorly in the field. Set it too coarse and low flows become invisible, the logged data turns into big blocky steps, and a verification comparison over a short test window becomes needlessly rough, because the meter only "speaks" once every thousand litres. Set it appropriately for the flow range and the data comes through smooth and low flow behaviour stays visible.
The logging interval. Resolution isn't only about volume, it's about time. A daily total and a 15-minute interval record can describe the same day and tell completely different stories. The daily total says 800 cubic metres. The 15-minute data says the pump short-cycled all morning, ran flat out through the afternoon restriction window, and something kept flowing at 2am when nothing should have been. This is exactly why water take reporting rules are built around 15-minute interval data rather than daily totals: the regulator has decided what resolution the question needs, and it's finer than a day.
The transmission chain. Every link after the meter has to preserve the resolution the meter provides. A high resolution meter feeding a logger through a coarse pulse setting, or a logger recording quarter-hourly data that only gets glanced at monthly, has had its resolution quietly thrown away somewhere along the line. The chain reports at the resolution of its coarsest link.
High resolution, wrong number
It bears repeating, because it's the most common confusion we meet: a reading of 1,234.567 cubic metres looks authoritative, and it can still be ten percent out. Resolution tells you nothing about drift, installation problems, or a sensor that's been slowly fouling for two seasons. Only a proper verification against a certified reference does that. The ideal is both: a meter and output configuration with resolution matched to the application, and a verification schedule that confirms the finely sliced number is also a true one.
Matching the detail to the question
So the reflective takeaway is the same one the map taught us. The right resolution is the one that answers your question. For a consent holder, the question is usually set by the consent: 15-minute intervals, reported daily, to a defined accuracy. For an industrial process, it might be much finer. For a quick gut-check on a season, coarser is fine. What matters is that the choice is made deliberately, in the meter configuration, the pulse value, and the logging setup, rather than inherited from whatever the defaults happened to be on install day.
NZ Flow Group has spent over a decade installing, configuring, and verifying flow meters across irrigation, municipal, and industrial networks, and a surprising amount of that work is simply getting the resolution right: the correct pulse value for the flow range, logging intervals that meet reporting obligations, and outputs that don't throw detail away. If you're not sure what level of detail your setup is actually capturing, it's an easy thing to check and often an easy thing to fix.