Giter Site home page Giter Site logo

datasets's People

Contributors

alykhank avatar amsardesai avatar ankurmangal avatar axyjo avatar dsmccrac avatar jacktruong avatar jashp avatar jeffreyca avatar jeremyroman avatar jiabohou avatar jmccarth avatar jmtjendra avatar joekwan avatar kartiktalwar avatar kpaxman avatar kraigu avatar lkmorlan avatar mad-uw avatar mrandrewandrade avatar nathanv avatar opendata-uw avatar pavolc avatar sbobkin avatar sustainabilityuw avatar void-elf avatar zachomedia avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

datasets's Issues

Mega Issue for uPrint

  • Update Printers/Printers.csv/ setup cron job/script to update autoupdate branch
  • add columns to Printers.csv to support uPrint
  • create a new data store to support generic uPrint information for the whole fleet:
    • pricing
    • anything else?

Printers.csv columns will be:

  • Boolean: part of uPrint fleet
  • Building Location matching /buildings/list
  • Canonical Room Number
  • Colloquial location description
  • Service Hours if part of uPrint fleet
  • Available print-job types
  • Boolean: Available for use?
  • Anything else?

Reference: http://uprint.uwaterloo.ca/locations.html

Show former buildings

The buildings should show former UW buildings. This requires changing the API to add a boolean column which indicates whether or not the building is current.

Sanitize parking lot data

Transfer parking lot data from v1 and make it more readable and parseable.

Cases

  • Visitor parking is available evenings at 3:45pm
  • There is currently no evening or weekend parking available
  • Visitor parking is available all day/evening
  • Visitor parking is available evenings and weekends
  • Evening and weekend parking for visitors is available until 10:00 pm each night
  • Lot X is open and free from 4:30 pm Friday until 6:00 am Monday.
  • Visitor parking $2.00 per hour, daily maximum of $15.00 Evenings after 5:00 pm
  • Contractor permit parking only
  • Only between the hours of 6:00 am - 6:00 pm.
  • No overnight parking from 3:00 - 6:00 am

Response (needs work)

{
  "name" : "A",
  "latitude": 43.474847,
  "longitude" : -80.5446,
  "available_weekends" : true,
  "available_evenings" : true,
  "available_daytime" : true,
  "is_currently_open" : true,
  "current_visitor_cost" : 5,
  "type" : ["Faculty", "Staff", "Visitor", "Contractor"],
  "not_open" : [
    {
      "days" : ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"],
      "time_start" : "03:00",
      "time_end" : "06:00"
    }
  ],
  "note" : "Permits are sold to faculty and staff if space is available"
}

List of faculties

Would be great to assemble a list of all faculties (grad and undergrad)

/v2/codes/faculties.json

@nathanv can you help out with this?

Think we get the data from that UWaterloo Pedestrian App?

In Fall 2012, the University published an app (the name escapes me) that tracked pedestrian paths around campus. While static, I still think this would be a cool dataset (think heatmaps, Zombies vs. Humans uses, maximizing club advertisments, etc.)

Is UWaterloo willing to give that up? (Or do we already have it?)

examschedule.json should not include a "day" key

examschedule.json has both "day", which is the day of the week, and "date", which is a full ISO date. Since "day" can be easily calculated from "date", "day" should be deprecated and eventually removed.

Dates in holidays.csv should be in ISO format

Dates in holidays.csv are currently in a format like "Monday February 20" with the year stored in a separate column. This file should be just two columns: ISO date and name of holiday.

Subjects and departments are not the same thing

The DepartmentsList service is returning a large number of items which are not UW departments. Department codes and subject codes are mixed together. Departments are more properly known as units and faculties are groups. Subjects are owned by units, which are owned by groups. For example, the AFM subject code is owned by the ACC unit, which is owned by the ART group. There needs to be a service for all three of subjects, units, and groups.

List of shops/restaurants

Suppose I were to provide data for a list of shops, restaurants, and their opening times. Does Open Data concern itself with locations belonging to the university (e.g. food services locations), locations on campus (e.g. Tim Horton's), or locations near campus (e.g. campus plaza)?

examschedule.json should use array for "locations"

In examschedule.json, the key "location" should be deprecated. A key "locations" should be added containing an array of the locations.

Currently, "location" is a quasi comma-separated list of locations.

building_id is being cast to int

In the buildings endpoint, the building_id contains only numbers, not the letters that some ids have. This suggests that these are being cast to int.

Make "Course Schedule by Term" data available for older terms (Fall 2013 and earlier)

via email support:

"Can you say why "Course Schedule by Term" data for some older terms is not available?

I'm gathering class sizes for a collection of courses and am finding that no data is available for terms older that fall 2013 (1139).

The UW Registrar's page usually restricts listings to 4 terms worth of course schedule data:
http://www.adm.uwaterloo.ca/infocour/CIR/SA/under.html

The CS dept, however, has a similar page of course schedule data (for any UW
course) for over 10 years of terms. And the data looks like the UW Registrar pages. Their URL is https://cs.uwaterloo.ca/cscf/teaching/schedule/

Here's an example for course CHEM 123 in Winter 2013 (1131):
This URL
https://api.uwaterloo.ca/v2/terms/1131/CHEM/123/schedule.json?key=e4f2a20a4d95c0e0292aa5f14224ca83

returns

{
"meta":{
"requests":78,
"timestamp":1407528285,
"status":204,
"message":"No data returned",
"method_id":1193,
"method":{
}
},
"data":[

]
}

The CS dept course schedule page has this information:

https://info.uwaterloo.ca/cgi-bin/cgiwrap/infocour/salook.pl?sess=1131&level=under&subject=CHEM&cournum=123

just not in json format.
"

ExamSchedule/1149ExamSchedule.csv has extra blank columns

There is a known issue with extra columns in the csv. Some notes:

  • This issue ONLY affects the CSV and not the API.
  • Since we wanted to get the data out as fast as possible and since the API works as per usual, we are releasing the data with this known issue.
  • In the future, we endeavour to properly normalize the data in conjunction with the partners at the registrar.

edit 13:06 16-10-2014: for clarity

examschedule.json should use course codes as keys in "data"

In examschedule.json the "data" key contains an array of objects. It would be easier to get the information for a specific course if "data" was an object with the keys being the course codes and the values being the arrays of sections currently in the "sections" key.

alternate_building_names should have own file

There should be a separate file to store the data now in column alternate_building_names in Buildings.csv. The columns of this new file should be (building_id, alternative_name) and these should together form the primary key. Once this is done, alternate_building_names should be removed from Buildings.csv.

This creates a better relational structure and keeps the data in Buildings.csv objective.

Another possibility would be to have primary key (building_id, name) and another column to define the status of the name, such as colloquial or archaic.

WCMS site listings have html entites in JSON

JSON strings should not contain HTML entities. Preferred format: & or the \u (Unicode) representation.

Example:

"unit_short_name": "Mechanical & Mechatronics Engg",

should be either:

"unit_short_name": "Mechanical & Mechatronics Engg",

or

"unit_short_name": "Mechanical \u0026 Mechatronics Engg",

examschedule.json should use ISO time

In examschedule.json, "start_time" and "end_time" are in 12-hour time. I suggest that these keys be deprecated and new keys "time_start" and "time_end" be added showing the times in ISO 24 hour format.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.