johntigue / idots_data Goto Github PK

See,
https://github.com/JohnTigue/outbreak_time_series_data/wiki/IDOTS-Library-API

https://github.com/ebov/space-time

Ideally the physical structure is just for organizing packaging. The full tree should be enumerable a la HATEAOS style. That is there should be essentially a collection indexing mechanism (read: directory listing). These are static files, JSON. If TableGroups can point to other TableGroups then that is what should be done. Otherwise, handcrafted JSON.....

• http://gamapserver.who.int/gareports/Default.aspx?ReportNo=2
• data via http://www.who.int/influenza/gisrs_laboratory/flunet/en/

https://github.com/JohnTigue/outbreak_time_series_data/blob/master/disease/disease_by_infectious_agent/viral_infectious_disease/Ebola_hemorrhagic_fever/who.by_county.2016_03_20.csv-metadata.json

That must just be a mistake, for example:

Indicator,Country,Date,value
"Cumulative number of confirmed, probable and suspected Ebola deaths",Guinea,2015-03-10,2170.0

Why would there be non-integer value? 2170.5 people died?

the dist/ directory now has Swagger-UI of project's API.

This was generated according to instructions in Swagger: How to Create an API Documentation:

• npm install swagger-ui
• cp node_modules/swagger-ui
• gulp-yaml to translate the project's Swagger spec from YAML to JSON
• tweak dist/swagger-ui/index.html to load the just generated JSON for viewing

There has to be a better way of doing this.