Whitehouse, Milton Keynes

Whitehouse is a civil parish that covers a large new development area on the western flank of Milton Keynes, As the first tier of Local Government, the parish council is responsible for the people, living and working in this area of Milton Keynes.

Whitehouse
Whitehouse
Mapping © OpenStreetMap
Whitehouse
Location within Buckinghamshire
Population[lower-alpha 1]
OS grid referenceSP813378
Civil parish
  • Whitehouse
Unitary authority
Ceremonial county
Region
CountryEngland
Sovereign stateUnited Kingdom
Post townMILTON KEYNES
Postcode districtMK8 [lower-alpha 2]
Dialling code01908
PoliceThames Valley
FireBuckinghamshire
AmbulanceSouth Central
UK Parliament

As of January 2019, it is bounded by Calverton Lane (prospectively, the Monks Way (H3) extension) to the north, Watling Street (V4) to the east, Dansteed Way (H4) to the south, and a hedgerow line[lower-alpha 3] with Calverton to the west.[1] The district covers 228 hectares (560 acres) (including open space) and is projected to have 4,400 homes and 6.5 hectares (16 acres) of employment land.[2]

Origins

The (greenfield) land it occupies was previously part of Calverton, a rural parish outside the Milton Keynes urban area. In 2004, the Government decided on the further expansion of Milton Keynes and accordingly designated land on the eastern and western flanks for this purpose.[3] Along with the adjacent parish of Fairfields (and Broughton, Milton Keynes on the eastern flank), this is the part of the implementation of that decision.

Etymolology

The district is (to be) built on land that was originally Whitehouse Farm (and other farms).[4]

Electoral ward (Borough)


Footnotes

  1. The parish did not exist at the time of the 2011 census. Its small population was included in the census for Calverton.
  2. May be changed as development expands. This is the postcode for the adjacent parish of Abbey Hill
  3. May be replaced by an extension of Tattenhoe Street (V2)
gollark: Okay, sure, you can ignore that for Go itself, if we had Go-with-an-alternate-compiler-but-identical-language-bits it would be irrelevant.
gollark: I can't easily come up with a *ton* of examples of this, but stuff like generics being special-cased in for three types (because guess what, you *do* actually need them), certain basic operations returning either one or two values depending on how you interact with them, quirks of nil/closed channel operations, the standard library secretly having a `recover` mechanism and using it like exceptions a bit, multiple return values which are not first-class at all and which are used as a horrible, horrible way to do error handling, and all of go assembly, are just inconsistent and odd.
gollark: And inconsistent.
gollark: But... Google is hiring some of the smartest programmers around, can they *not* make a language which is not this, well, stupid? Dumbed-down?
gollark: It has some very nice things for the cloud-thing/CLI tool/server usecase; the runtime is pretty good and for all garbage collection's flaws manual memory management is annoying, and the standard library is pretty extensive.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.