Homework 3 - Data extraction, conversion, and build a CSV file output.ZIP

Homework 3 - Data extraction, conversion, and build a CSV file output

As discussed in Homework 1 many ETL (extraction, transformation, and loading) problems parse data files wherein the data fields is separated by commas. This assignment is a continuation of that process - with an additional two steps. The first step is to convert the input file’s latitude and longitude from sexagesimal (base 60) degrees to decimal degrees. For example, the inputs are in the form: degrees, minutes and seconds, arcseconds and direction. The outputs are in the form: sign, degrees, and decimal fractions to represent the same value.

This assignment requires the data extraction, degree conversion, data formatting, and output. The file inputs are defined in the Inputs, as are the outputs.

The verification of the output data will be the plotting of the output file’s airport information in a Javascript enable web page.

1      Objectives
The objectives of this assignment are to demonstrate proficiency in file I/O, data structures, data transformation, and file output using C language resources.

1.1     Inputs
There are two basic inputs, the input file name, passed via the command line, and the input file data defined below.

1.1.1       Command Line arguments The input file name will be input as follows:

hw3Export filename.ext
In the event that the input file is not available or there is an error finding the file, an appropriate error message shall be displayed. Use the example below for guidance.
hw3Export ERROR: File “bogusFilename” not found.
1.1.2      Input File fields
The CSV input file contains the following fields. Please note these fields may vary in size, content, and validity of the data. Also note that some of the data formats are a melange of types. Specifically, note that both latitude and longitude contain numbers, punctuation, and text. Likewise, the FAA Site number contains digits, letters, and punctuation. (This assignment will treat all input data as character data.)

Table 1: Airports Data Fields

Field Title
Description
Size
FAA Site Number
Contains leading digits followed by a decimal point and short text
Leading digits followed by a decimal point and zero to two digits and a letter
Loc ID
The airport’s short name, i.e.

MCO for Orlando
4 characters
Airport Name
The airport’s full name, i.e.

Orlando International
~30 characters
Associated City
The nearest city
~25 characters
State
State
2 characters
Region
FAA Region
3 characters
ADO
Airline Dispatch Office
3 characters
Use
Public or Private
2 characters
Latitude
DD-MM-SS.MASDirection
Degrees, minutes, seconds,                milliarcseconds followed by either N or S.
Longitude
DD-MM-SS.MASDirection
Degrees, minutes, seconds, milliarcseconds followed by either E or W.
Airport Ownership
Public or Private
2 characters
Part 139
FAA Regulation
No data
NPIAS Service Level
National     Plan  Integrated

Airport Systems Descriptor
~10 characters
NPIAS Hub Type
Intentionally left blank
n/a
Airport Control Tower
Y/N
one character
Fuel
Fuel types available
up to 6 characters
Other Services
Collections of tag indicating INSTRuction, etc.
12 characters
Based Aircraft Total
Number of aircraft (may be blank)
Integer number
Total Operations
Takeoffs/Landings/etc (may be blank)
Integer number
2      Outputs
The outputs of the program will be populated Struct airPdata data. This data will be formatted so as to provide output as defined in the following sections.

2.1     Data Structure
The structure struct airPdata is described below. Please note the correlation with the data file’s Field Names refer to Table 1 on page 3 for more information. NB The Javascript APIs for plotting geographic data REQUIRES that longitude is before latitude.

typedef struct airPdata{

char *LocID;        //Airport’s ‘‘Short Name’’, ie MCO char *fieldName; //Airport Name char *city;                //Associated City float longitude; //Longitude float latitude; //Latitude

} airPdata;

2.2     File output
The file output for this assignment is stdout, aka the console. Make sure there is a headline that names each column. For example:

code,name,city,lat,lon

DAB,DAYTONA BEACH INTL,DAYTONA BEACH,29.1797,-81.0581

FLL,FORT LAUDERDALE/HOLLYWOOD INTL,FORT LAUDERDALE,26.0717,-80.1494

GNV,GAINESVILLE RGNL,GAINESVILLE,29.6900,-82.2717

JAX,JACKSONVILLE INTL,JACKSONVILLE,30.4939,-81.6878

EYW,KEY WEST INTL,KEY WEST,24.5561,-81.7594

LAL,LAKELAND LINDER RGNL,LAKELAND,27.9889,-82.0183

MLB,MELBOURNE INTL,MELBOURNE,28.1025,-80.6450

MIA,MIAMI INTL,MIAMI,25.7953,-80.2900

APF,NAPLES MUNI,NAPLES,26.1522,-81.7756

SGJ,NORTHEAST FLORIDA RGNL,ST AUGUSTINE,29.9592,-81.3397

ECP,NORTHWEST FLORIDA BEACHES INTL,PANAMA CITY,30.3581,-85.7956

OCF,OCALA INTL-JIM TAYLOR FIELD,OCALA,29.1717,-82.2239 MCO,ORLANDO INTL,ORLANDO,28.4292,-81.3089

Things to note:

Digital degrees are expressed as floating point numbers of varying digits of precision. This is an artifact of Javascript. In this exercise 4 digits to the right of the decimal point is sufficient.
The first line of the file identifies the field names. This is a material fact and will adversely impact the output of the data in the webpage. Capitalization and spelling matter - and must match the first line above.
The text shown above has been converted to uppercase as a piece of information to help debugging. String case conversion is not required for this exercise.
Once the output has been verified, redirect the stdout to a file named myTestAirports.csv. Move this file to the unpacked HW3 directory for testing. Yes, validation of the correct output will occur on a browser enabled PC. Make sure that all code, inputs, and outputs are built, tested, and the output file is exported from Eustis.

3      Processing
The primary goal is to provide programmatic access to the data from the input CSV file. This must be accomplished using standard C file IO techniques. Also note that it is vital to utilize the stuct airPdata for all data retrieval/extraction and conversion. Likewise, use of the stuct airPdata is required for the file output.

3.1     Reading the input
There are several approaches to read the input. Perhaps the most important consideration is reading the line in for each airport. Please note that there is one line per airport. Also note, that once the line is read into the input buffer it might be advantageous to parse the input buffer based on the comma delimiter.

There are several approaches possible. Make sure to test on Eustis as line termination characters/behaviors vary amongst operating systems.

Make sure that the output file is formatted with decimal degrees.

3.2     Processing the data structure
The data conversions for this assignment, specified below, require a certain degree of parsing and calculation. Initially reading the input is to your advantage to deal with all data elements as character data. And then process the latitude and longitude, hereinafter referred to as degrees. The degrees are expressed as sexagesimal (base 60) numbers. Their respective value is defined in the two tables below.

3.2.1       Latitude/Longitude Input
The latitude and longitude are both degrees, expressed as shown in the table below.

Table 2: Degrees

Placeholder
Name
Value
Decimal
DD
Degrees
180
0-180
MM
Minutes
0-59
value 60
SS.MAS
Seconds.MilliArcSeconds
0-59.0-9999
value 602
D
Direction
N,S,E,W
See Table 3
Table 3: Direction

Unit
Name
Decimal Sign
Latitude
N

S
+

-
Longitude
E

W
+

-
The conversion of the DDD-MM-SS.MASD string is shown in Table 2 above. The formula to convert a sexagesimal degree measurement to a digital degree measurement is shown below.

degreesdecimal =±DDD + MM/60+ SS.MAS/602

Note that the ± is derived from the information in Table 3 above.

3.2.2 Function float sexag2decimal(char *degreeString);

Description: Convert the sexagesimal input string of chars to a decimal degree based on the formula in Tables 2 and 3.

Special Cases: If a NULL pointer is passed to this function, simply return 0.0. Similarly, if the DD-MM-SS.MASD fields have invalid or out-of-range data, return

0.0.

Caveat: Even though the valid range of Degrees is from 0 to 180, the data files for the Continental US and Florida are from 0 to 99. Make sure that the conversion can handle all valid cases correctly.

Hint: Take care to make sure the values for each numeric component are within their valid ranges. Refer to Table 2 for the ranges.

Returns: A floating point representation of the calculated decimal degrees or 0.0 in the special cases mentioned above.

3.3     Testing
There will be two files provided for program testing. They are described below. The program’s output will be to stdout. Redirect the output to the test named myAirports.csv. This specifically named file can then be copied to the HW3 folder for testing with the webpage named plotFlorida.html in that folder.

The input file used in Homework 1 will be used as an additional testing file. Errors will induced for the degrees.

Table 4: Test Files

Filename
Description
FL-RAW-airports.csv
A list of the 25 public Florida airports, wherein all the data is formatted as defined in the Input Specfication.
FL-airports-PLOT.csv
All 25 airports’ data formatted as defined in the Output Specification.
 
Powered by