Possible Bug? Untagged Biomes

[Trann]

When on EVA and taking surface samples (on Duna in this case), I get the biome as "Untagged".  I can toss these results and try again to get the same results.

So I planted a quick flag, tossed the results...

...and tried again and it works; I notice that the long description changed in the same location, too.

Any ideas?

[MrChumley]

My thinking is:  You might have been right on the boundary of 2 biomes?

You can do ALT+F12 in windows to bring up the cheat menu and click "show biomes".

[Cydonian Monk]

I noticed this too. The KSC monolith is an untagged biome for most science reports. The observatory added by the ResearchBodies mod is too. Maybe a bug, maybe an oversight. 

[Trann]

A very interesting theory.  Thanks.

The spot was in in the "northwest" corner of the map, in a crater (bottom flag).  As you can see from the zoom, it was a fair distance to the next biome border (about a full degree in map coordinates).

 

But the map may be imprecise with respect to the actual biome borders so I'm going to attempt another landing at the same location to see if I can re-find the "broken" region.

[Laie]

@TrannIn my experience, Scansat maps are 100% perfectly accurate. Small wonder, considering their data source. Does Scansat have a name for the biome, btw?

[Trann]

@Laie I had thought so, too, and this is how I do my biome selections.  Scansat maps are still showing each biome properly as I walk the mouse over them (I never saw "Untagged" once).  And I was able to reproduce the problem in another landing zone: when EVAed on the surface, the first sample taken was Untagged; discard and plant a temporary flag; remove the flag; now samples are properly tagged.  So it may not be location specific but an actual weird little bug.