Two lots on the same street, 40 meters apart, can come back with different flood levels or elevations. That is usually the data working correctly, not a glitch. Here is what actually changes between two nearby points.
People screen two lots in the same subdivision and get different answers. The usual reaction is that something must be broken. Most of the time the difference is real, and understanding why makes both reports more useful.
Every line on a hazard report is measured at the exact coordinates you gave. That is the whole design. A barangay-level answer would be easier to produce and nearly useless, because hazard does not stop at a property line, and it does not spread evenly either.
So when two nearby lots differ, the first question is not "which one is wrong" but "what changed between those two points."
1. A hazard boundary runs between them. Mapped flood, landslide, and storm surge data are polygons, which means they have edges. If the edge of a mapped area falls between two lots, one is inside and one is outside. The edge is a modelled line, not a wall, so a lot just outside is not immune. It is simply outside the mapped area. How to read a flood hazard map covers what those levels mean.
2. The ground is genuinely different. Elevation and slope are read from terrain data at each point. Two lots 40 meters apart really can sit at different heights, and in flat neighbourhoods that difference is exactly what decides which one takes water first. That is the argument in elevation and slope.
3. Distances are measured from your pin. Distance to the nearest waterway, and distance to the nearest mapped active fault, are straight-line measurements from the coordinates. Move the pin, and both numbers move.
4. The pin was placed differently. This one is on us as users. A pin dropped on the road, on the roof, or at the subdivision entrance is a different point than one on the actual lot. If you are comparing two properties, place both pins with the same care, then use the method in comparing two lots.
It does not mean one lot is safe. Being outside a mapped polygon is the absence of a mapped hazard, not the presence of protection. Rare events, local drainage failures, and changes since the data was collected all live outside the map.
It does not mean the map is precise to the meter. National datasets are built at a scale that covers the whole country. They are excellent for screening and wrong tools for surveying a boundary. The distinction is laid out in hazard map vs. geotechnical survey.
It does mean the question is worth asking on site. If one lot reads lower or closer to a channel, go stand on both and look. Ground truth is cheap when you are already there.
A small difference between two nearby readings is usually terrain doing what terrain does. A large one is worth a trip.
Large differences almost always have a visible cause. One lot sits below a road embankment. A channel runs between them that is invisible on a listing photo. One has been filled and the other has not. A subdivision wall has changed where water goes. Every one of those is obvious within five minutes of standing there and impossible to see from a screen.
So the rule is simple: the report tells you where to look, and your feet tell you why.
Three practical habits follow from all of this:
The one thing not to do is average two readings into a general impression of an area. Hazard is a property of a place, not of a neighbourhood, and the whole reason to read at a point is that the point is what you are buying.
A screening reads public national datasets at a point. It cannot see the drainage installed last year, the wall that redirected runoff, or the fill that raised one lot above its neighbour. When two nearby readings differ, the report has done its job by telling you where to look. Confirming why is a site visit, and confirming what to build is a professional survey.
CheckHazard does not replace a professional geotechnical or engineering survey.