pkkj/skyexplorer1

A powerful WebGIS for investigating air traffic data.

skyexplorer1's Issues

Move the TS reference files (.d.ts) to a single folder.

We should put this file in the same location...

Add the important messange to UK CAA data source

We should notify the user that the route might have stop.

Create the dest panel for Wikipedia data.

We need to create the destination panel for Wikipedia data.
It will display the operator in the route.

Hook up the new data source selector UI with "data source info dialog".

At least we should implement:

1. the tooltip for the data source.
2. the dialog discussing about the data source.

Update the T100 data to 2013 December

T100 data is still the priority of our system.

Create the UI and classes for Japanese Aviation Data

We will add this new data.

Localize the data availability matrix for different data sources

We need to support multiple data sources for airport data report page (Client)

Think the same problems as route report page..

Refactor the T100OriginPanel, move to common codes

Remove the T100 related features.
Move it to common code.
Then rename the class.

Resolve the problem of showing time series with only 1 month

We need to figure out how to display the time series if their is only one month in the new year (2014).

1. Disable the time series?
2. Just load the 2013 data?

Customize a dest panel for Taiwan's data

Create the dest panel for Taiwan data and customize the querySegment function.

T100 and T100 FF share the same dest panel 2: resolve the conflict

Description page for UK CAA data with availaiblity matrix

We should create an info page for UK CAA data.
User can see this information by clicking "About UK CAA Data".

Simple dest panel combo box could not update the destination in the map

Refactor the carrier table to resolve airline code conflict problem

As the list increase, we found that some codes are conflict. Currently, "JW" has conflict.

To resolve this problem, we might have to define new columns called "displayed code" and "real code".

display code is used for display.
real code is used for identify the airline.

Move the warning message of T100/T100FF to their data source class

We should not hard-code this message in destination panel. We should move them to data source class.

Setup the basic support for TW data

1. Provide the web service to fetch Taiwan data
2. Create a new data source class for Taiwan data.

Hook up the new data source UI with year selector. Only enable the src if it is available in selected year

Define the availability matrix for Korea data

Update the Korea data to the earliest year

Check the availability of Korea data. Update to the earliest year.

TS: Move the available airline provider to common code

The getAllAirlineInfo should be implemented in common codes.

Taiwan data: for intl data, we need to sum the inbound/outbound data

At least, we need to do some special calculation for Taipei Taoyuan - Kaohsiung, since the data is provided in intl table.

Update the airport info file

There are some mistakes in the current file in the server.

Define the availability matrix for Wikipedia data

We need to support multiple data sources for route data report page.

We need to support multiple data sources for route data.
We can define the availability matrix:

1. Pax data available?
2. Freight data available?
3. Airline data available?
4. Only domestic data? Only international data?

We also need to re-design the UI.

Airline content should consume the function in web service to query airline year availablity

Update the data Japan to the earliest year

Currently it's 2007. Make it as early as possible

Define the availability matrix, create the web page template

To simplified the description of "availability" of different data sources, we need to define a availability matrix.

For example: a "by-region" matrix for T100:
x:
US domestic route
International route
F-F route
y:
Time-lag:
Available airline:
Segment data:
Market data:
Airline?
Aircraft?
Month?
Passenger?
Freight?
Seat?
Departure?
Double-direction?

Hook up the new data source UI with available airline

1. User can select airline under combo box.
2. The list in the airline will be changed if the user change data source
3. If the airline changed, the origin information will be updated

Webservice: should be able to return the available airlines of specific data sources

This only returns the code of airlines. And we are able to map them to the cached data in cient

Airline view should only show the airlines with T100 data.

Localize the data source selector and related objects

We need to decide how to consume the localized values in different locale object.
We should pay attention to the order of initialization.

Move the calculation of route distance to origin panel

Now this code is in T100's destination panel. It should be in common panel.
It is not calculating the distance for other panels.

Data source selector: hook up the clicking event with launching data src info dialog.

Click the name of data source, then the data source info dialog will be shown

US T100 and US T100 FF data are sharing the same DestPanel

It might cause other issue. Maybe we should separate them? Or move the logic handling showing data source info dialog to the subclasses?

Origin panel should be able to launch the Airport statistics only for T100 data source

We should tell the user that the airport report is using T100 data.

Maybe we could have it working with TW CAA data.

Such dialog for UK data will be in next iteration...

Hook up the new data source UI with available data sources

1. User can select data source by check-box
2. If the user change data source or airline, the current data will be re-search

Generate the new base map for web service

Before the ship we should generate the new base map for web service.

1. Grey color for the city without "outbound data"..

The hint in origin airport text box doesn't work

Maybe it's a regression from recent update. We need to fix it. And find a way to patch the fix in server

Refactor T100 Dest Panel to "StandardDestPanel", and make T100DestPanel to be its subclass

Since Taiwan and T100 will share the same dest panel with different logic. We should create a new base class for these two data sources.

Change the implementation of carrier data in WebService

1. We can put the carrier data file under "serverdata" without manipulation.
2. Pythton generates individual "carrier availability" file for different data sources. (Be carefull for UK data). We also put these files under "serverdata".

Set up the display of destinations without data

We need this feature to display some external data sources, when we don't have the data.

Move T100 FF into an independent data source

Since T100 FF has special available time and different notes, it should be an independent data source.
We don't need to change the database. The web service could determine whether a record is T100 or T100 FF.
Then the client codes can handle it.

GetDestByOrigin() should support filtered by data source.

GetDestByOrigin() should be able to return data within required data sources.

Localize the airline/airport comment in the Excel file

We might need to localize the airport comment and airline comment in the Excel file.

Present the flight and freight statistics for Japan data

We have such data. We need to present them in the left-panel.

For the graph, we could create an option control with "Freight/Flight/Pax"

New UI for data source selector and airline filter for airport view

Create the new UI for data source selector.
The new UI should be collapsable.

We need to refactor the code handling airport table

Now we are using IATA code as the index of airports.
However, some airports don't have IATA code.
Therefore, we need to use the internal unique code to distinguish airports.

1. change the Python code, which generate the data. (the code should be compatible)
2. change the TypeScript code, change the definition of "Airport". We can still display IATA code and ICAO code.
3. change the C# code. Read the data from the airport file. Be able to query the airport from internal code.
4. For the airport without IATA, we should use ICAO in the map. Otherwise, maybe we don't need to display its code.

Expand the DataSourceInfo class and use it to describe all data sources

We should expand the DataSourceInfo class. It should support:

1. the available time period of data source
2. important notes for the destinations. multiple notes should be available. Such note will be displayed in dest bar
3. current country
4. short name and full name. Consume the value in localization classes.
5. the webpage URL to the description page.

And then all the data sources will have a sub class. We should create the page for T100 data, T100 FF data and CAA data

Hook up the Korea data with UI