Ropewalk Pumping Station
The Ropewalk pumping station was built on the Ropewalk in Nottingham in 1850.[1] It is a Grade II listed building.[2]
| Ropewalk pumping station | |
|---|---|
 Ropewalk pumping station | |
  Location within Nottinghamshire | |
| General information | |
| Architectural style | Gothic revival |
| Location | Ropewalk, Nottingham |
| Town or city | Nottingham |
| Country | England |
| Coordinates | 52.955135°N 1.161332°W |
| Completed | 1850 |
| Design and construction | |
| Engineer | Thomas Hawksley |
History
It was built by the Nottingham Waterworks Company in 1850 along with a reservoir on Park Row in Nottingham. It used a 60 hp (45 kW) Cornish Beam engine to pump from two 240 ft (73 m) deep wells.
The Ropewalk pumping station fell into disuse around 1880 when it was found that the water which it was supplying was contaminated by Nottingham General Cemetery. It supplied 960,000 imperial gallons (4,400,000 l; 1,150,000 US gal) of water per day, and analysis in 1873 showed that it contained 31.5 grains (2.04 g) of solid effluent per gallon.
The building was used as a garage from 1930.
gollark: ... no.
gollark: Thus bad.
gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
References
- Pevsner Architectural Guides, Nottingham. Elain Harwood. Yale University Press. ISBN 978-0-300-12666-2
- Historic England. "Details from listed building database (1254997)". National Heritage List for England. Retrieved 20 April 2015.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.