Narita Airport Terminal 2 Shuttle System

The Narita Airport Terminal 2 Shuttle System (成田空港第2ターミナルシャトルシステム, Narita Kūkō Dai-ni Tāminaru Shatoru Shisutemu) was an automated people mover used in Narita International Airport, Narita, Chiba Japan. The system operated between December 6, 1992 and 2013.

Narita Airport Terminal 2 Shuttle System
The Narita Airport Terminal 2 Shuttle System in March 2008 with a Malaysian airline aircraft at tha back
Overview
LocaleTerminal 2 of Narita International Airport, Narita, Japan
Transit typePeople mover
Number of lines1
Number of stations2
Operation
Began operation6 December 1992
Ended operation27 September 2013
Operator(s)Narita International Airport Corporation
Technical
System length279 m (915 ft)

History

The Shuttle System opened in 1992 with the opening of Terminal 2 of Narita International Airport, the international airport serving the Greater Tokyo Area. The shuttle linked the main building of the terminal and its satellite, 279 metres away. The whole ride took a minute, and was free of charge.

The system was made by Nippon Otis Elevator, a company specialising in elevators and escalators. It was technically (and legally) not a railway, but a horizontal elevator; cars were attached to a cable that moved them, like a funicular. The cars did not have wheels; instead, they floated on a 0.2-mm layer of compressed air. This was the first use of such a system to be used in an airport, as well as the first in Japan.

A new walkway between the main and satellite buildings had opened on September 27, 2013, whereafter the people mover ceased operations.[1] The space formerly used by the walkway was converted into moving walkways and shops.

gollark: They aren't that hard. You just use `server_name` in the `server` block.
gollark: Not specifically wordpress, no.
gollark: I would probably use nginx, because I'm used to it and it has nicer configuration:```nginxhttp { # whatever important configuration you have for all HTTP servers, `nginx.conf` probably ships with some # fallback in case someone visits with an unrecognized Host header server { listen 80 default_server; listen [::]:80 default_server; return 301 http://somedomain$request_uri; } server { listen 80; # you may (probably do) want HTTPS instead, in which case this bit is somewhat different - you need to deal with certs and stuff, and use port 443 - also you should probably add HTTP/2 listen [::]:80; # IPv6 server_name domain1.com; location / { proxy_pass http://backend1:8080/; } } server { listen 80; listen [::]:80; server_name domain2.com; location / { proxy_pass http://backend2:8080/; } }}```
gollark: The reverse-proxy solution is in my opinion the best one, although it would require some config.
gollark: I think LetsEncrypt may not be very happy with that, though.

See also

References
  1. "成田空港に新連絡通路が完成".



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