Blog

Target notes vs mapped features in a Phase 1 habitat survey

A misty grass field bordered by a wooden fence and a line of bare hedgerow trees.

A Phase 1 habitat survey produces two different kinds of record on the same map, and anyone digitizing field sheets for the first time usually mixes them up at some point. A mapped feature is a polygon, line, or point with a habitat code attached: A1.1.1 broadleaved semi-natural woodland, B2.1 unimproved neutral grassland, J2.1.2 species-poor intact hedge with trees. Together these cover the whole survey boundary without gaps. Every square metre of the site gets a code, even if that code is just amenity grassland nobody wanted to photograph.

A target note is something else. It's a numbered flag on the map pointing out to a written note, usually on the back of the field sheet or in a separate list, describing a feature the surveyor thought was worth recording but that doesn't fit neatly into the habitat polygon scheme. Maybe it's a single veteran oak standing inside a parcel of improved grassland, a culvert outfall, a patch of Japanese knotweed too small to draw at 1:10,000, or a badger sett entrance at the field boundary. The surveyor writes "TN14" on the map and a sentence in the notes, rather than carving out a polygon for something that's a point of interest, not a habitat parcel.

Why target notes exist separately from the habitat map

The JNCC Phase 1 methodology was built around hand-drawn maps at a fixed scale, and a lot of ecologically important things are too small or too specific to draw as a polygon at that scale. A single tree, a drainage ditch with water vole signs, a gap in a hedge used as a badger run: none of these are habitats in the classification sense. They're observations about a specific spot. Target notes keep that detail out of the polygon layer so the habitat map stays readable, while the written note carries whatever level of detail the surveyor recorded in the field.

Once it leaves the field sheet, that split carries straight into the GIS. Mapped features go into your habitat layer as polygons or lines with a HabCode field and whatever condition attributes your template carries. Target notes go in as a point layer, usually just a numbered marker tied back to a text field or a linked table: a pin in the ground and a sentence, not a parcel with an area.

Where this gets messy in the GIS

The practical headache is that target notes often describe exactly the kind of feature a client later asks you to map properly. A target note that says "mature oak, good bat roost potential" on survey one becomes the thing everyone wants delineated and buffered for the bat survey the following year. At that point you're not dealing with a target note anymore, you're building a new feature class for it. Same with invasive species patches, badger setts, or any protected species evidence that started life as a one-line annotation and later needs its own polygon layer with proper attributes for a planning submission.

That's the gap a lot of consultancies hit: the thing you need mapped across a whole site isn't woodland or grassland, it's whatever specific, client-defined feature showed up as a handful of target notes last season. There's no off-the-shelf classifier for veteran oaks with cavity features or knotweed stands along a riverbank, because it was never a standard habitat code to begin with.

If that's where you've landed, where a few target notes need turning into a full coverage layer over high-res imagery rather than another round of walked transects, Few-Shot Mapping is built for that step. You label a handful of examples from the feature the target notes already describe, and get back a mapped layer of every matching instance across the site.

Worth a look if your next deliverable starts with a pile of target notes and ends with a request for a proper layer.

Request early access

← Back to the blog