For the record, this is the lake gen11 is named after https://goo.gl/maps/qGDcVhrudoEJZou18
Still, the bigger point is: what purpose do such compound names serve? Early on the codenames were simpler, e.g. Katmai (Pentium III), Banias (Pentium M), Yonah (Core Solo/Duo). Specifically, what additional information is conveyed by the "Lake" categorization, where within the same broad product group (CPUs) some projects are called "Lake," and some others are "non-Lake?"
If there is actually some distinction (client/server/embedded perhaps?), wouldn't such a codename be self-defeating by revealing too much ("Something Lake" announced makes it obvious Intel is working on a client CPU)? And if it's meaningless then using two words when one would suffice seems redundant.
However, since the location names used under this policy are so obscure few people (including an Intel employee in a parallel comment) even realize they refer to actual places, the whole naming convention arguably makes little sense at this point.
Since there isn't even a single "lake" named after something that can actually be found in a lake or near it, such as an aquatic animal, and there are also products from the same category with unrelated codenames (East Beach, Basin Falls, Chief River, River Forest, Forest Crystal, etc.) [1] why not just keep the first noun only and make things simpler. It's not as if it would cause any further confusion at this point.
1. List of some recent Intel codenames (not for the faint-hearted): https://www.intel.com/content/www/us/en/design/products-and-...