Arorae Airport

Arorae Airport (IATA: AIS, ICAO: NGTR) is the airport serving Arorae, Kiribati. It is located in the north of the island, north of the village of Tamaroa.[1]

Arorae Airport
Summary
Airport typePublic
ServesArorae
LocationTamaroa
Elevation AMSL6 ft / 1.83 m
Coordinates2°36′58.54″S 176°48′7.56″E
Map
AIS
Location of the airport in Kiribati
Runways
Direction Length Surface
ft m
3,100 945

The airport is served by Air Kiribati from Tabiteuea North Airport, which is connected directly with the international airport at South Tarawa, but lands at Tamana too on its way from Arorae back to Tabiteuea North.

Airlines and destinations
AirlinesDestinations
Air Kiribati Tabiteuea North,[2] Tamana[3]

Air Kiribati connection with Tamana

Landing at Tamana is not a fuel stop: Since this is the only time in the week Tamana is served, passengers can get in or get out there. Thus, note that if one wants to fly from Tamana to Arorae, he cannot do anything else than make the big detour via Tabiteuea North (which lies much farther from Tamana than Arorae does), and wait a full week there, until the next flight to Arorae (because from Tabiteuea North, the plane continues its way to Bonriki International Airport).

Notes
  2. Only way back; way there is via Tamana.
  3. Only way there; way back is via Tabiteua North.



gollark: There 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: 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 and decompresses stuff at the right offset
gollark: I don't know what you mean "dofs", data offsets?
gollark: Well, this will of course be rustaceous.
gollark: So that makes sense.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.