Nordbach
The Nordbach is a 1.7 kilometre long, left tributary of the Große Aue in East Westphalian Rödinghausen in the district of Herford in the German state of North Rhine-Westphalia
Nordbach | |
---|---|
Mündung des Nordbaches in die Große Aue | |
Location | |
State | North Rhine-Westphalia, Germany |
Physical characteristics | |
Source | |
• location | In Schwenningdorf |
• coordinates | 52°14′51″N 8°30′23″E |
• elevation | 120 m above sea level (NN) [1] |
Mouth | |
• location | In Schwenningdorf into the Große Aue |
• coordinates | 52°15′11″N 8°31′44″E |
• elevation | 91 m above sea level (NN) [1] |
Length | 1.7 km (1.1 mi) [2] |
Basin size | <10 km²[1] |
Basin features | |
Progression | Große Aue→ Weser→ North Sea |
Landmarks | Villages: Rödinghausen |
The Nordbach stream rises at a height of 120 m above sea level (NN) in Schwenningdorf. It discharges into the Große Aue, or Neuer Mühlenbach as it is known in its upper reaches, at a point 82.7 kilometres up the Aue from its mouth. Their confluence is at 91 m above NN and the stream descends a total of 29 metres.
Swimming pool
The Nordbach fed the first natural open-air pool in the parish of Rödinghausen. Its basin is used as a fish pond today.
gollark: I tested four different compression algorithms and brotli did fairly well; I would have used zstandard but the node bindings for it are awful, and brotli actually did do better on small inputs.
gollark: For example, it stores created/updated timestamps in a way which allows them to be looked up more quickly, makes it faster to look up the latest revision of stuff, allows me to do compression (I implemented brotli compression to reduce storage requirements a lot), and allows revisions to have data and represent stuff other than "the page content changed".
gollark: The new version *is* better, even if it involves something like 70 lines more code.
gollark: I've reworked minoteaur's design a bit again because productivity is BEES and happens to other people.```sqlCREATE TABLE pages ( id INTEGER PRIMARY KEY, name TEXT NOT NULL, updated INTEGER NOT NULL, content TEXT NOT NULL);``` I went from that small and thus uncool database thingy to this:```sqlCREATE TABLE versions ( vuuid TEXT PRIMARY KEY COLLATE BINARY, rawSize INTEGER NOT NULL, encoding TEXT, data BLOB NOT NULL);CREATE TABLE pages ( title TEXT PRIMARY KEY, created INTEGER NOT NULL, updated INTEGER NOT NULL, latestVersion TEXT NOT NULL REFERENCES versions(vuuid));CREATE TABLE revisions ( ruuid TEXT PRIMARY KEY COLLATE BINARY, page TEXT NOT NULL REFERENCES pages(title), timestamp INTEGER NOT NULL, type TEXT NOT NULL, data TEXT NOT NULL, -- JSON version TEXT NOT NULL REFERENCES versions(vuuid));CREATE INDEX revisions_page_ix ON revisions(page);```
gollark: Suspicious timing.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.