Week 3

Things to go over…

  • Office hours
    • Yoh:  Thursdays 3:00-5:00pm (by appointment.  Other times negotiable too. Sandbox, Math Sciences Building)
    • Erin: Wednesdays 1:00 – 3:00pm (fish bowl)
  • Review of Week 2 material
    • Common problems?
    • Biggest frustrations?  Let’s talk…
  • Badges of the week

Group Presentations

  • Introductions – show blog
  • Describe group project

 Dave’s Corner:  Objects, variables, arrays… confused?

Hands-on Coding Workshop

Group Time

  • Open group time

Assignments

  1. Codecademy:  CSS (due MONDAY)
    No badges this week :(, instead, finish the first three sections (out of 5) of the “CSS: Coding with style” lesson:

    Although you get no badges (unless you finish the entire section), you should upload a screenshot that demonstrates your completion of the first 3 sections.  You can find this section by clicking on your name in the top header section of the website:
  2. Web development (due MONDAY)
    Once again, your boss loved your second version of your bus stop project.  She now wants you to add an overlay of existing Metro bus stops so that you can compare the location of your stops, with existing metro stops.  Then, she wants you to make an argument on whether or not the existing Metro locations have an impact on your proposed route.
    *Coding Requirements: 

    1. Pick and choose the metro lines that are relevant to your proposed route.
    2. Use the Metro API to map those routes

    Submit your assignment by creating a blog entry, describe your project, add a screenshot, and hyperlink (<- please) it to your site.

    If your current web development is not in Los Angeles, check here to see if your area of interest has a public transit API you can use. If one’s not available, find another API that can help to support the case for your new transit stops that is available for your area.

  3. Group Assignment (due TUESDAY: 7pm)
    You have now established yourselves as a legitimate force in the web-mapping development world.  You have a solid proposal to build a new and innovative application, and have received venture start up funds from EY Ventures (Erin and Yoh) to build a prototype.  Making sure to take in the feedback you have received from your investors, rewrite your proposal, and put together a functional specification.  Your spec should include: 

    1. Revised proposal topic and description
    2. A list of functionalities the site will provide
    3. Wireframe diagram that describes each section of the site
    4. Sketches or diagrams that “storyboard” the prototype’s usage. Examples here.
    5. A list of all datasets that the project will use (specify the API URL if using web services)
    6. Milestones: What will be done by week 6, and what will be done by Finals week
    7. Concerns

8 thoughts on “Week 3

  1. Question question question… So I added KML layers for the red line and purple line (because for some odd reason, the Metro API doesn’t appear to have rail lines.. unless I’m missing something… I even looked for the rail line route numbers in the array… nothing) and I want to add the station stops as a KLM layer too. So I saved the station stops as kml layer but a) I can’t seem to adjust the size of them even when I adjust the size in google maps and more importantly, I can’t figure out how to order the klm layers so that the icon appears on top of the line. All my icons appear under the rail line layers! Any ideas? Thanks!

  2. I’m getting an error when I try to upload a JPEG of our group’s storyboard for this week’s assignment. The error reads:

    “Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 13200 bytes) in /home3/yohmanco/public_html/gis/wp-includes/media.php on line 253”.

    Yoh, is the website out of memory?

Leave a Reply