# Talk:Highgate tube station

I removed:
The platforms at Highgate are the deepest below the surface on the London Underground, partly because the staion is near the top of Highgate Hill.

LU's Northern Line facts page says Hampstead, not Highgate, is the deepest. This is supported by CULG, which gives the drop of the lifts at Hampstead as 55.2m, and that of the lower escalators at Highgate as 21.03m. --rbrwr
I'd basically agree with you; the original statement was possibly made because the station is already in a deep (from the roadside) cutting and if you took the distance from the top of the upper escalator to the bottom of the lower escalator (the booking hall being in the middle) then the drop may be greater than that an Hampstead. --[[User:VampWillow|VampWillow]] 23:38, 1 Dec 2004 (UTC)

I removed:

and in the [[London Borough of Camden|borough of Haringey]]
as Camden and Haringey are different London Boroughs, so either the link target or the link text must be wrong. Anybody know which it is?. -- Chris j wood 14:15, 23 Feb 2005 (UTC)

It is obviously in the London Borough of Haringey because the infobox said so.Vincent60030 (talk) 15:51, 7 February 2015 (UTC)
@Vincent60030: Why "obviously"? The infobox is no more reliable then the article text - both are there because somebody typed in the information. Also, did you realise that you were responding to a thread that Chris j wood posted ten years ago? At that time, the article had no infobox; the immediately-preceding edit was this one. Things have moved on a lot since then. --Redrose64 (talk) 19:04, 7 February 2015 (UTC)
But, rather to my surprise, I'm still here. Although I don't think I've edited an article on a London tube station in a good few years. Thanks to Redrose64 for bringing this to my attention. I've checked using links from GeoHack (did we have GeoHack 10 years ago?) and confirmed that Highgate tube station is indeed in the London Borough of Haringey. So I've reinserted the, appropriately corrected, text I first removed 10 years ago, and added the appropriate citation (did we have citations 10 years ago?). Now all I have to do is try and get rid of the resulting feeling of getting old :-(. -- chris_j_wood (talk) 20:15, 8 February 2015 (UTC)
@Chris j wood: We certainly didn't have <ref>...</ref> (that didn't become available for another nine months, in November 2005), but other more complicated methods (FN1, FN2, FN3, FN4) existed. --Redrose64 (talk) 20:27, 8 February 2015 (UTC)
@Redrose64: Wow. I sometimes come across stuff I wrote back them and cringe at all the stuff I did wrong. Anyway, forgot to thank Vincent60030 for noticing this, and making sure it got sorted eventually. -- chris_j_wood (talk) 20:39, 8 February 2015 (UTC)
@Chris j wood: You're most welcome. Vincent60030 (talk) 10:40, 9 February 2015 (UTC)
Comment the amazing thing is that that error was introduced by Morwen whom I always thought of as a very safe pair of hands. Well done to Chris j wood for spotting it all that time back ... DBaK (talk) 07:39, 17 September 2015 (UTC)

Hello fellow Wikipedians,
I have just modified one external link on Highgate tube station. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

Added archive https://web.archive.org/web/20150212131957/http://www.islington.gov.uk/services/parks-environment/parks/islington_nature_reserves/Pages/parkland_walk.aspx to http://www.islington.gov.uk/services/parks-environment/parks/islington_nature_reserves/Pages/parkland_walk.aspx
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Y An editor has reviewed this edit and fixed any errors that were found.

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 19:02, 3 November 2017 (UTC)