Update on the Final Project

Link to working website.

In the final project for Winds of Healthy Change we would like our users to be able to enter a zipcode of interest, which would zoom the map to that particular area and pull up proper AQI data.The AQI data would include available information on a variety of pollutants (TBD).  The user would be able to see the number from the AQI index as well as the color pertinent to that particular zipcode and refer to the legend to determine if it is safe or not to be outside and at what danger level the air is.  The  wind arrows will show on default and the size of the arrow will correspond to the wind strength.  The user can use the legend to get more information about the arrows.  The user has the ability to click anywhere on the map and a polygon for the clicked zipcode appears as well as any information available about the AQI.  Both the air quality, wind speed and direction data is in real-time which would allow the user to get more accurate information than otherwise available.  There will be a few toggleable layers, weather being one of them, and some that still need to be determined.  We have broadened our user base and now have information for users nationwide, although we anticipate our website will be more relevant to people who care about outdoor air quality such as parents, and to people who are more vulnerable to poor air quality..

Historical air quality data will also be available for the user to access, although that data availability only dates back to August 1st, 2009.This will be important if users wanted to look at patterns in air quality throughout certain years, season, or time periods.

Although we have had some progress in the development of our website the following things are still in progress:

  • Calling air quality parameters of choice both historical/real-time
  • Sizing buttons dynamically
  • Thinner wind direction icon(s)
  • Entering a custom zip code rather than clicking on the map

As our project is evolving with have encountered some new challenges but are still facing some old user interface annoyances.

  • User interface issues
    • Our team has come up with a variety of different ways to present the data (some involving a Navbar, some involving having different parts of the screen greyed out).  We’ve got the Navbar to work SOMEWHAT efficiently, but there’s still some problems with alignment and working with the container.  Another problem is that we’re unable to appropriately make the calls to grey out specific areas or provide pop-up boxes (as Yoh had proposed).  We’re working on this problem diligently.
  • Integrating Bootstrap seamlessly into our webpage
    • As I mentioned earlier, we’re trying to incorporate Bootstrap CSS into our webpage, because we enjoy the ease of design.  However, we’re finding it difficult to adjust some of the parameters according to what we’re looking for, however, we need to explore the “Customize” section in further detail.  If that doesn’t work, we will probably explore other CSS options.
  • Historical data – what metrics to choose from?
    • Another thing we’re trying to adjust is how to present the data (bar graphs) using Bootstrap on the page.  We still haven’t figured out how to make the specific call, and also, we haven’t identified which pollutants we’re going to be focusing on.  We’ll need to decide this soon before we move on.
  • Highlighting polygon with AQI color – call currently inefficient
    • The call to highlight the polygon with the AQI color is currently inefficient and redundant.  We need to think about another way to make the call, or we won’t incorporate this aspect.
  • Do not know how to call for pollutant of interest
    • We’re not sure how to make the call to get the same pollutant of interest, versus randomly getting different calls for each pollutant.  We’ll need to standardized this before proceeding.

Tulum Raiders Wk8 Update

1. Final Project Proposal

Purpose of our website:

The Tulum Neighborhood Portal has two functions:

1) A one-stop neighborhood resource map for the citizens of the city of Tulum.

2) A tool for the citizens to participate in city planning by identifying places they like or need improvement. Citizens can also suggests resources needed in the community.

Main functions:

1) Community resources: they are toggled by category, so viewers can turn them on or off at their viewing convenience.

2) Red/Green/Magic Wand: users can directly click the map to add three types of markers to “evaluate” their neighborhoods.

Red: Indicates an unsatisfactory area or asset that needs attention

Green: Indicates a positive asset in the community

Magic Wand: Indicates a non-existing, but desired asset

3) Twitter Widget: it does a live search and streams Tulum-related tweets. Citizens/public officials can advertise community events or announcements by including “Tulum” in their tweets to be listed in the widget. This allows them to reach Tulum- centered audience when tweeting about events happening in the city.

4) Picasa API: retrieve photos from Picasa album and show photos in slideshows. Pictures will be shown in the box below the title.

2. Updated wireframe and/or mockup/storyboards

<Top Page>

*Note: Only 2 maps will be created: 1) Neighborhood Resources, 2) Maps to include red/green lights, and magic wand.

<Red/Green/Magic Wand Function>

3. Current development status

  • Community resources, streets, bike pads, community districts are mapped.
  • Website design completed.
  • Picasa API: now working.
  • Community resource legend: now working
  • User guide: now working
  • Red/Green/Magic Wand: function to add a marker was created. Need to add a function to store the marker.

4. Challenges/issues

  • Tulum does not have address (except for a few landmark buildings or hotels). So users cannot type addresses in a “search box” to find places or get directions. Instead, we created neighborhood district boundaries. They are toggled by the name of the districts. Users can narrow down their search by clicking on these districts. Can we substitute the required direction function by this?

TESLA Update Week 8

Goals:

1.     Tiling-

We want to be able to have the polygons show… but we are also aware that tiling 6 years worth of EAZs could take DAYS.

Prep steps:

  • Need dominant land use data for each EAZ
  • Make sure each year’s data is attached (so that we can do a bar chart for kWh used over time)
  • Need to establish breaks/ “buckets”
  • Establish color scheme

Potential/ “Wishlist” for tiling:

  • General electricity use of LA City by EAZ (2010 data)
    • Potential hack= tile each electricity breakdown separately (ie 0-100,000kwh, 100,001-500,000 kwh, and 500,000-10,000,000 kwh) so that we can toggle the layers on/off. This requires a lot more tiling though .
    • Highest Break
    • % change (statistical analysis) per EAZ
    • Electricity use by census tract instead of EAZ (so it’s more aesthetically pleasing when zoomed out) à BUT, do we need to do highest break/% change/ land use tiled for each then????
    • Land use à tile each layer of land use (ie- commercial, residential, etc)

 

MAIN TILES WE NEED (minimum)

  • General energy use of LA City by EAZ (2010 data)
  • % change (statistical analysis) per EAZ

2.     Google Charts API

  • We want to have historical electricity use per EAZ as a bar chart
  • We want to use our radius that we created last time to create a pie chart of the dominant land use per EAZ within a specific radius (ie- for all the EAZs within 1 mile radius,  60% have a dominant land use of residential and 40% have a dominant land use of commercial) 

 3.     Reverse Geocoding

  • It would be nice to have our “click” on the map show an actual address or neighborhood (neighborhood might be above our pay grade)

 4.     New/old tab

  • Since it’s difficult (and by this we mean IMPOSSIBLE) to query info to show up/ disappear from ArcGIS, we are considering keeping the dots from our midterm  and having them in a separate tab from the arcGIS tiling layer tab. Our electricity breakdown would be the same divisions, but it just offers another way of looking at the map 

 

 

 

Wireframe/Sketch: Our website will closely resemble the midterm project…. the main change will be on user friendliness. We will have the basic functionalities as the “preset” map but then will also have an advanced options. Therefore, those that want to do a cursory glance of Los Angeles Electricity use will be able to do so without having to wade through a lot of other options.

 

Struggles: The color scheme for our tiling is a little bit tricky. We have tried a variety of options including….

Variation1: Too much green, doesn’t show electricity variation.

Variation 2: Too much beige

Variation X (we lost count): When zoomed in, this looks like the army’s new camo…. (obviously not ideal).

 

Stay tuned for our final tiling product and the decisions we make regarding colors!!!!

Week_8_Final_Proposal_HLS

A. Final Proposal Topic, Description and Functionalities

How safe is LA? New IT firm to re-present the city’s safety in a new light

We are pleased to announce Home.Land.Security., a new IT firm specializing in mapping the safety of San Francisco’s communities for the city’s most vulnerable people.

In February of this year, Trayvon Martin, a 16-year-old African American was shot and killed by George Zimmerman as he walked to his girlfriend’s house in Sanford, Florida. The killing, which appears to have been racially motivated, has triggered anger and sadness nationwide. It has also sparked controversy and attention to the safety of Black and Latino teenagers—especially after talk show host Geraldo Rivera suggested that Trayvon’s death was due to his wardrobe choice (a hooded sweatshirt) rather than his racist attacker. This project is a response to incidents like Trayvon’s death, and seeks to bring to light the larger systemic forces that make neighborhoods unsafe and unhealthy.

In recent years, there has been a growing recognition of the interrelationships between health, safety, and the built environment and the dire need to create safer spaces. Public health professionals have begun to think more holistically about health, questioning the social and spatial determinants of wellbeing. Planners too are thinking beyond their traditional domain, questioning how streets, housing, neighborhoods and cities may affect the health of their residents.

We believe that this growing attention to creating safe and healthy spaces is a positive development, but that it does not go far enough. It has failed to address the acute threats to the safety of queers, immigrants, people of color, women, low-income people, the homeless, people with disabilities, and other communities.

Home.Land.Security. seeks to fill this gap by visually representing unsafe, threatening and harmful spaces as experienced by the most vulnerable.

FUNCTIONALITIES (Note some of these features were added after the blog post deadline):

  1. Search Bar: The user can navigate the map by typing in an address or zip code.
  2. Officer Involved Shootings: The user will be able to toggle an officer involved shooting layer from 2000-2011, which will appear color coded by year. Each icon will have an info window that contains a description of the incident.
  3. Neighborhood Characterization: We compiled a layer of attributes including sums of demographics, crime counts and officer involved shooting counts to provide a characterization of each neighborhood. When the user clicks on a neighborhood (or searches for a neighborhood), a series of charts will pop up in the accordion style menu to show potential demographic and crime correlations with officer involved shootings

B. Updated Wireframe diagram

 

C. Current Development Status

  1. Here is the full site.
  2. In ArcMap we created an mxd layer with sums of demographic, crime and officer involved shooting data for each neighborhood in San Francisco, in preparation for making charts, using Google Charts API. We authored the layer in ArcGIS server and published the layer on our map
  3. We are cleaning up our code, removing the google places API and crimespotting API. We merged all of the OIS layers by year into one layer.
  4. We are adding a search bar for the user to search by location and modified the colors and layout of the site
  5. We began making demographic/crime statistics charts for each of the neighborhoods.

G. Challenges Issues

  • Making each neighborhood un-highlight whenever we click on another one
  • Formatting and presenting chart data
  • Presenting the most intuitive way to organize the buttons on the sidebar for our layers
  • Spiffing up the design
  • Figuring out why only 100-200 crimes show up from the crimespotting API when there should be 23,000

Home.Land.Security Weekly Update

We’ve been busy as ever here at Home.Land.Security…

Based on our Midterm feedback, and our own reflections about the site, we’ve decided to try to focus our project a bit more. For the midterm, we concentrated on getting up all of our data sources, layers, and API’s. We thought that the final result was pretty interesting, but that it lacked a clear and stimulating story.

For the final, we want to try to drill down a bit more to pull out some of the relationships between the different layers. In our presentation and feedback, we heard that the officer involved shootings layer really spoke to people. We also think that this layer is where we excel and distance ourselves from other sites. We do not want to be another crimespotting or healthy city site. Both already do their job quite well, probably better than we will be able to.

But no one else has mapped officer involved shootings. We think that the geography of these shootings is both stimulating and disturbing. For our final, we would like to explore the distribution of these shootings by neighborhood. Specifically, we’d like to use the data we’ve collected to explore the ways in which these shootings relate to neighborhood demographics. Are neighborhoods of color disproportionately targets of police violence? What other relationships might we be able to make visible to our users?

We’d like to use charts or infographics to create a visually captivating explication of these relationships. Based on Yoh’s advice, we’ve decided that it makes the most sense to put all of our data into ESRI layers. This week, we’ve concentrated on adding these layers to our site. See the results here.  We’ve added new layers to the demographic and officer involved shootings tabs.

Here’s the data sources we are relying on: (also see the sources tab).

We’re also working on getting some neighborhood boundaries up users can query and get stats on specific neighborhoods.

Next week we will be plunging into the work of aggregating these layers, and displaying the results in graphic form. Wish us luck!

Here’s the site!

GeoStories Week 8 Update

Here at GeoStories, we’ve taken the constructive feedback we’ve received from our peers and EY Ventures and are moving forward by addressing the following issues:

1. Creating a “Table of Contents” : A form that consists of buttons that represent the chapters a user has created in the “Story Board” section of the site. Yoh has courteously set us on the path towards creating the necessary function.

2. Navigation Buttons Within InfoWindows: Advancement in this area requires that Issue 1 first be resolved.

3. Saving the Story: The way to save individual stories so that they can be accessed, edited, and shared later apparently requires the use of Server-Side Scripting, which, we have been advised, is presently beyond our pay-grade. And so we search for a way to capture a story via its URL.

4. How-To: We want to create instructions on how to use the site.

5. Angling the Brand: Is their a unique way to position GeoStories so that it stands apart from its most obvious competitors (HistoryPin, TripLine); is it necessary to do so, or is the generic, stripped down nature of GeoStories an advantage?

Till next time…

Winds for a Healthy Change Update!

Winds Working Beta

After receiving comments back about our midterm Beta version of our website, we needed to focus the functionality of our website.  In going with the theme of a real-time map, we decided to focus on the AirNow Air Quality Index (AQI) data and present it in a useful manner since calling/organizing a data would be a challenge in itself.  Originally, we found that hourly observations go back to around July 2009, but this meant that there were ~20,000 individual data files.  To process such a large amount of data would be very difficult.  In addition, each file did not have a consistent set of data from each monitoring station; therefore making data organization even more of a challenge.

As of late last week, Yoh helped us discover that we could make calls to historical data.  With this knowledge, we won’t have to worry as much about data organization.  The goal with obtaining all of this data would be to build something similar to what Google Maps has for hourly traffic patterns.  but before getting to that, we would like to first backtrack and decide which variables to display.  AQI is calculated differently for each of five parameters– Ozone, CO, NO2, PM 2.5, and PM 10, so now we need to decide which parameter(s) to focus our efforts or whether we should allow the user to access them all.  Currently, we are doing some literature review and consulting air quality experts on campus to see if there is a justified way of aggregating the data to a single AQI number.

Further updates include:

  • Updating the “About Us” page, which we feel needs significant improvement in conjunction with our overall project, not only in design, but also layout.
  • Working on incorporating an accordion panel instead of our current tabs.  We are looking into this feature in order to provide a better user interface, but we are also exploring other options provided by Bootstrap.  They have some really pretty groovy layouts.
  • How to present our title.  We really enjoyed TESLA’s rotating gallery, and we’re thinking about incorporating something similar to that, or something more minimalistic.  This is more of an afterthought at this point, as we want to ensure that the majority of our functions are working and are appropriate to our overall goals.
  • Trying to create and incorporate a wind vector matrix.  This was a suggestion presented to us during the midterm, so we wanted to make sure we address it.  Instead of having one single arrow associated with the temperature sensor, we wanted to create a matrix of wind arrows that covers the entire area.  We believe this would provide more comprehensive wind information compared to the single arrow.  We currently have some issues displaying the icons.
  • Obtain real-time data from the AirNow API.  This was one of the largest drawbacks to our midterm, and thanks to Yoh, we were able to get it to work.  We have integrate that into our existing project, but we need to make additional tweaks where necessary.
  • Our user interface is one of the largest challenges we are facing.  As our site provides a wide variety of data, trying to keep the site easy and simple for users to peruse is proving difficult.  Our next steps are to look at various other sites to gain inspiration from their existing layouts, and then try to mimic and adapt our site accordingly.

Recent accomplishments:

  • Recently we were able to incorporate Yoh’s code into our existing prototype.  We are excited at having real-time data now, and we need to come up with a way to easily display the information for the user.  Some idea’s we’re having involve:
    • Search bar
    • Predefined areas (limits users’ ability to search)
  • We were able to code for the wind vector, but at this point, it does not seem to be working on our site.  We may need additional help on this.

Week 7 TESLA Update

Since our presentation to EY ventures, we have been working on preparing for our Final product. This week consisted of a lot of brainstorming and re-envisioning. We also presented our preliminary website to the Institute of the Environment and they were very pleased with our initial work.Their major requests are

  1. Include ArcGIS polygon layers
  2. Include building data (we are waiting for UC Davis to send us this data)
  3. Possibly include an energy buffer that sums use within a certain distance

Our midterm project focused on the “bells and whistles” to show off our coding ability. Now, we need to trim some of the features in order to focus on the main point: our data. The purpose of our project is to create an interactive map that displays electricity usage in Los Angeles. Therefore, some of our features might not be suited for this goal and they might actually distract the user. For example, the LEED buildings might not be an important layer to have (especially if there is no argument we can make regarding their importance).

We plan on meeting with Yoh and/or Ryan this week to discuss the ArcGIS tiling of our data. Since we have 6 years of data, we need to decide how we want to symbolize it. Our research affiliates at UC Davis are deciding the “category” breakdown for energy use. Once we know this we can create the final GIS shapefile and upload it to the server. We think it is best to tile it at two levels- one zoomed in to provide a detailed focus and one zoomed out to give an overall picture of electricity consumption in LA.

We will also receive the parcel data and building use data. Once we have this information we will be able do summary statistics to tell a more complete picture of electricity usage.

One of our biggest challenges will be to decide how we want the GIS layers to interact with everything else. Since these layers are static we are not sure how functionality of searches or toggles will work. We’re thinking that we might keep the Google Fusion Table layer as small dots in the centroid of each polygon shape so that there is a clickable function to show graphs and summations. Hopefully, discussing our options with EY will help provide some clarity and will spur more innovation.

Introducing… GeoStories !

We are pleased to announce the beta launch of GeoStories.com, a social story-mapping platform that enables users to create personal narratives around the places they’ve been and the experiences they’ve had there.



GeoStories is about connecting—and contextualizing—our many remarkable moments and memories. The site’s simple, streamlined interface allows users to pair their personal thoughts with meaningful images or videos pulled from the media site(s) of their preference (Picasa, Flickr, YouTube, Vimeo, etc.), almost instantly transforming the ubiquitous digital map into a personal memoir, descriptive genealogy, historical non-fiction, or lighthearted travel journal. The GeoStories Introductory Video gives a colorful and concise overview of the process. It should also be noted that much of the information included here is available at the GeoStories FAQ page.

    How It Works

You can begin creating your story chapters from the GeoStories Story Board.

Each geostory is built of chapters; each chapter represents a different location; and each location can be detailed with personal thoughts and narrative text, as well as imagery or video.

As each chapter is completed, you’ll see a numbered icon representing the chapter appear in the GeoStories map display. Clicking on the icon will reveal the full, multimedia description of your experience.


Once all the desired number of chapters has been written, and the user hits the I’m Done button, the map display zooms out to reveal all chapter icons, numbered and linked—a narrative constellation of your own making, ready to be explored and shared.

    The Team

GeoStories is a start-up funded by E.Y. Ventures and founded by Uyen Ngo and Andrew Pogany. As Chief Experience Officer, Ngo has dedicated her considerable expertise to the design and programming of the entire GeoStories site. She also created the awesome Introduction video. As Senior Story Teller, Pogany has contributed to the site’s concept and content.

    Key Functions

1. User-Generated Map: GeoStories is ultimately a tool by which users can quickly become authors of personalized, multimedia, map-based narratives. Fundamental to this function is the use of the Google Maps API, as well as the Google geocoder, which enables a non-specific location entered in the Address input to be almost instantly translated into latlong coordinates and mapped.

2. Media Upload: Popular online media management sites such as Flickr, YouTube, Picasa, and Vimeo provide image and video links for content owned by the user or deemed available for public use. Presently, GeoStories users must copy and paste the appropriate image or video link into the Pictures/Video input on the Story Board. They also have the option of including the embed codes of images and videos in the Description input.

3. Connecting The Dots: GeoStories does not present individual locations as separate entities of no (explicit) relation. Its Story Board interface allows for users to attach text and media to specific locations, and then connects those locations using numbered icons and lines, thereby guiding the reader to consider each location, or chapter, as part of a larger sustained narrative.

    Notable Challenges

1. Interface Design: Coding of the input page was moderately complex, especially when trying to figure out how to add imagery or video to the same pop-up window as the text included in the description box. Also, understanding how to connect map icons with a visible line required assistance.

    Future Improvements

1. Saving Drafts: The GeoStories team will be looking for a solution that will allow for the saving and editing of incomplete stories.

2. Library Upgrade: Every story, once completed and fully mapped, should automatically be saved to the GeoStories library. The GeoStories team will look to allow story authors to obtain links for each of their stories, or share directly through the social network of their choosing.

3. Additional APIs: GeoStories presently incorporates the Google Maps API. Future manifestations of the site will potentially incorporate the APIs of various online media management sites such as Flickr, YouTube, Picasa, and others to facilitate enhanced uploading capabilities. Additionally, GeoStories will look to potentially incorporate the APIs of relevant social networks, such as Facebook and Twitter, to enable sharing.

Winds for a Healthy Change Midterm

Introduction:

Our website.

Los Angeles County is known for its rich culture, diverse landscape, and most importantly, its beautiful weather.  Unfortunately, also well known to most Los Angelinos is the horribly pervasive air pollution, which adversely affects many children throughout the County.  Exposure to such horrible air is attributed through a confluence of factors, such as transportation to and from schools, outdoor physical activity, and a lack of knowledge regarding poor air quality days.  Chronic exposure to high particulate matter (PM), ozone, or smog can contribute to upper and lower respiratory problems, asthma, or worse, decreased lung capacity.

In order to address such gaps, it is with great pleasure that the WINDS FOR A HEALTHY CHANGE Inc. would like to unveil its new interactive mapping tool that aims to informs students, parents, and educators about current unhealthy air quality, in order to make better-informed decisions regarding their outdoor activities.  Our tool, currently in its beta phase, provides real-time information on a number of factors related to air quality such as: temperature, wind direction, wind speed and air quality indexes.  Each of these variables will be presented in an easily understandable format that empowers, educates, and informs our target groups.


Who We Aim to Please:

  • Students – Will be able to learn about alternative modes of transportation, such as bus routes, train lines, and subway stations using the Metro information incorporated into our map.  We believe having these features will encourage students to be more sustainable, and participate in reducing automobile emission exposure by riding public transportation.  Additionally, our interactive map provides information on a number of useful locations catering to students, such as libraries, parks, zoos, schools and bookstores.
  • Parents – Will also be provided with similar amenities as students, with the additional benefits of locations pertinent to the working parent, such as hospitals, universities, and taxi stands.  We hope that parents can use this tool to determine when it is safe for their children to play outside when they are not in school.
  • Educators – Educators are our main priority with regard to our working prototype, as children spend most of the high pollutant periods within schools.  Our hope is that educators can use our website to identify periods of poor air quality in order to adjust the students’ schedules to include outdoor physical activity when PM is lowest.


Through such informed decisions, we hope to aid in reducing the overall incidence and prevalence of respiratory issues among children within Los Angeles County.

Implementation:
The Winds for a Healthy Change Inc. will promote our website as a multi-faceted tool to schools within Los Angeles County.  Teachers will be able to use our website in order to make informed decisions about poor air quality days and whether to allow children to play in such conditions.  Teachers will also be able to use the website as an educational resource to teach students about issues of sustainability, environmental justice, and air pollution.  We hope students can bring this information home to their parents or guardians, and that they will refer to our website daily, when making informed decisions.

Your Website Can Do What?!
Winds for a Healthy Change Inc. has scoured the internet in order to provide the user the most up-to-date information and technology regarding air pollution and public health.  Whereas a multitude of websites have sporadic information on  a variety of weather and air quality tools, our website combines these features together in a map that is both user friendly and easy to understand.  A few of the features we’ve gathered are:

  • Temperature data – users have the ability to view the temperature and the weather description.
  • Wind data – users are able to see how strong the wind is as well as the wind direction.  There are three different wind strengths represented by different colored arrows and eight different arrows in which we classify wind direction.
  • Air quality data – users are able to see the concentration of particulate matter from a number of monitoring sources provided by the South Coast Air Quality Management District.
    • Buffers – Indicate the extent and deposition of affected areas.
  • Places – Generates specific points of interest or things we felt the users would benefit from knowing.  These icons typically identify points of interest or outdoor activity centers.
  • Real-time bus location data- users are able to see all the LA Metro Rapid bus lines and where they are in real time as well as their direction.  We felt this would be an excellent resource for users who want to partake in reducing overall air pollution by riding public transportation.
  • Demographic Data – Allows users the ability to see a variety of demographic information that may be useful to illustrate  environmental justice issues.

Who’s who?

  • Bryan –
    • Gathered background information for project/project vision
    • Function quality control/Troubleshooting
    • Layout vision/ User appeal
    • Requisition of data
  • Julia
    • Some CSS design work
    • Developer page
    • Some data requisition
  • Sharon
    • Coding map controls and features
    • Explored Google layers and experimental functions
  • Steven
    • Requisition and parsing of data, including original data from AirNow
    • CSS style coding for site layout
    • Google Fusion Tables


“Yeah, That’s Not Going to Work” Moments:

Real-time Air Quality Data – The main concern was obtaining access to real-time air quality data for Los Angeles County, particularly since air quality data is generally presented at a much larger scale.  After finding an appropriate API, it was also difficult to incorporate it into our existing map, even after following the directions, links, and appropriate coding for the code to work – it appeared as though the JSON code provided by the website was wrong.  In order to remediate this problem for the midterm, we obtained static data from a number of sources, incorporated them into fusion tables, visualized the data and applied buffers in order to show the extent.

User interface – Being able to come up with a layout that could easily apply to all three of our target groups was challenging.  Since we want to display a variety of specifically chosen variables for each user, we wanted to think of a way that we could easily provide a variety of variables, but still provide the users with multiple options. We decided to use a mix of tabular and drop-down options, where users could view their specifically designated map, but also have the ability to add additional features if necessary.

Little obtained data  –  Most of the features, functionalities, and data provided on our map were obtained from existing websites, sources, and data found online.  Whereas other groups may have obtained data sources, working with existing APIs that typically are not incorporated with one another proved challenging.

Combining APIs – A lot of the APIs and features we wanted to add were problematic in that they did not work well with the one another or inhibited specific functions.  Acknowledging, working, and understanding their properties in order to have them functional was difficult.

Styling/colors – We approached styling through a number of variations, such as with Bootstrap, styling sheets, and typical CSS.  In some cases, our styling sheet conflicted with our Bootstrap coding making it difficult to alter colors or variations.


Onward and Upwards!

  • Forecasted weather projections
  • Real-time air quality data
  • Different checkboxes for each user (student, parent, educator)
  • More sophisticated layout
  • Better UI
  • Search Bar
  • Zoom in and out function
  • Expanding to all of California

Wireframe: