River Tiffey
The River Tiffey is a small river in Norfolk, England and a tributary of the River Yare. It rises near Hethel and passes through Wymondham before flowing generally north-eastwards passing through Kimberley, Carleton Forehoe, Wramplingham and Barford where the Tiffey joins the River Yare.
| Tiffey | |
|---|---|
 River Tiffey at Carleton Forehoe | |
  Location of the river mouth within Norfolk | |
| Location | |
| Country | England |
| Region | Norfolk |
| Physical characteristics | |
| Source | |
| • location | Ashwellthorpe |
| • coordinates | 52.5334°N 1.1409°E |
| • elevation | 55 m (180 ft) |
| Mouth | River Yare |
• location | Barford |
• coordinates | 52.6249°N 1.1361°E |
• elevation | 18 m (59 ft) |
| Length | 17.1 km (10.6 mi) |
| Basin features | |
| River system | River Yare |
| Tributaries | |
| • left | Bays River, Dyke Beck |
Further reading
- History Along the Tiffey (2007) by Anne & Adrian Hoare
gollark: It's less complex for everyone interacting with it, since they can just... use SQLite, which has bindings for everything, instead of "zimlib". And by "efficiency" do you mean "space efficiency" or "lookup efficiency"? Because, as I said, SQLite would probably only add a few bytes per directory entry row, which is not a significant increase.
gollark: SQLite's overhead is pretty low, and the majority of the filesize is from the binary blobs which would remain the same in each.
gollark: It's less complex for them as the code is already there and written with a nice API, and "less efficient" how? Slightly more space on headers?
gollark: You could easily store the directory entry bits as an SQLite table.
gollark: This is an excellent use case for SQLite, which would allow quick lookups in the metadata bit and not require coming up with a fiddly custom binary format.
External links
- Tiffey Valley circular walk
- Tiffey Trails Project
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.