Database of Nightside, High-latitude Ionosphere Meso-scale Flow Characteristics

This database is a compilation of nightside, high-latitude ionosphere meso-scale flow characteristics built on those used in Gabrielse et al. [2018] (https://doi.org/10.1029/2018JA025440). It is the most complete version. If you would like to use the database, please contact Christine Gabrielse (cga...

Full description

Bibliographic Details
Main Authors: Gabrielse, Christine, Nishimura, Toshi, Lyons, Larry, Gallardo-Lacourt, Bea, Deng, Yue, Pinto, Victor, Donovan, Eric
Format: Dataset
Language:unknown
Published: 2019
Subjects:
Online Access:https://zenodo.org/record/2539829
https://doi.org/10.5281/zenodo.2539829
Description
Summary:This database is a compilation of nightside, high-latitude ionosphere meso-scale flow characteristics built on those used in Gabrielse et al. [2018] (https://doi.org/10.1029/2018JA025440). It is the most complete version. If you would like to use the database, please contact Christine Gabrielse (cgabrielse@ucla.edu, cgabrielse@gmail.com, and/or christine.gabrielse@aero.org). Depending on how the results are used, the main authors request co-authorship on publications that utilize this database. The methodology and selection criteria can be found in Gabrielse et al. [2018] (https://doi.org/10.1029/2018JA025440). The following list describes the columns in each data file labeled, ***_FLOW-DATA-PCvsAO_YYYY.txt The first three letters (RNK or SAS) designate the station used (Rankin Inlet or Saskatoon). Files named ***_FLOW-DATA-PCvsAO_poleward_YYYY.txt are for poleward-directed flows. Each text file is for a different year (YYYY). AO=Auroral Oval for Rankin Inlet; equatorward of the auroral oval for Saskatoon (not used) PC=Polar Cap for Rankin Inlet; Auroral Oval for Saskatoon (Note: the data files for RNK and SAS have the same format, so the PC designator means flows above the pertinent boundary (polar cap boundary for RNK, auroral oval equatorward boundary at SAS) and the AO designator means flows below the pertinent boundary.) time [YYYYMMDDhhmmss] flagAO [-1=flow could not be observed. 0=flow could be observed, but was not. 1=flow was observed] flagPC [-1=flow could not be observed. 0=flow could be observed, but was not. 1=flow was observed] FWHMavg_AO [degrees] FWHMkmavg_AO=[km] longtestranges=[ignore] Velmaxavg_AO=[m/s, actual average of max V in each range gate used] VelmaxFITavg_AO=[m/s, determined from the Gaussian fits] FWHMavg_PC=[degrees] FWHMkmavg_PC=[km] Velmaxavg_PC=[m/s, actual average of max V in each range gate used] VelmaxFITavg_PC=[m/s, determined from the Gaussian fits] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; For the bearings/orientation, see the orientation text files. The following four variables ...