Week 8 Tutorial: Santa Fe Metro Stops

The Santa Fe Metro stops are an intelligent application of public policy. As we can now see from the map, the areas with higher levels of income, access to education and gender equality are all better served by public transportation. Granting greater mobility to populations in th areas that do not have the highest indices in the mentioned categories, may be a step towards better quality of life overall for the residents of Santa Fe. Finally, the search function allows residents to look at their specific points of interest most served by the proposed sites in relation to local amenities and existing metro stops. This is all possible by simply entering a zip code.

A full version of the map is available here.

Week 8: Late Homework Assignment

After many trials and tribulations, here’s assignment 8! Many thanks to Erin for the hand holding through the tutorials.

Newly added to the course assignment is census data and charts for age, gender, race. Check it out!

Challenges: shape layer/census data I created would not show despite having layers on it/visible on whippet. Ended up using tutorial census layer. Also did not have time to fix code so only one tract is highlighted at a time.

Week 8: GeoStories Home Stretch!

Back from Israel and ready to finish our GeoStories website for the final.

As a reminder, GeoStories is 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. 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.

Final Project goals/Wireframes:

After consultation with EY Ventures, the final product of GeoStories is looking to be more a prototype/envisioning tool of the different types (historical, adventurous, public health/urban planning tool, etc.) and capacities of stories users can create instead of previous visions of saving/editing/sharing stories on the GeoStories website. This is because finding a way around hosting a server/storage space for story content has not come to fruition. Final goals for the website Andrew stated in the last post are: 

1. Creating a “Table of Contents”: A second tab on the Story Board page, 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. The first tab will be where the user inputs content, then after they hit ‘Publish’, it will shift to the second tab, “Table of Contents” of the newly generated story. This story can be viewed as many times before the page is refreshed, as GeoStories has no current way to save stories. 

2. Navigation Buttons Within InfoWindows: Advancement in this area requires that Issue 1 first be resolved. We hope to emulate what is seen in Penguin Books, with navigation embedded within the info windows themselves which can move from chapter to chapter. http://wetellstories.co.uk/stories/week1/. An added bonus would be to figure out how to draw the red line between chapters really slowly.

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. It seems this option may not be feasible. This will be a bonus feature if we can figure it out.

4. How-To: We want to create instructions on how to use the site. Once we have our main StoryBoard page/function figured out, we’ll incorporate class suggestions in creating a tutorial for the user. A step-by-step guide to flesh out the introductory video.

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? I think GeoStories simplicity can stand on its own. 

6. Library: Instead of its initial intention in being a reservoir for user stories, I hope to make quick video demonstrations similar to the intro video on different types of stories users have the potential to create (old stories of their grandparents, present day vacations/trips, public health/urban planning teaching tools, etc.). I think if we do this, it will give GeoStories a uniqueness from similar engines such as TripLine and HyperCities.

Current Status: I was away last week and Andrew was in charge of moving forward. He has been working with EY Ventures on the programming and coding. We will regroup in class Wednesday and form a game plan of individual responsibilities to make sure we reach our final goals.

Challenges/Issues: It’s been a sharp learning curve for this 2-person team. A lot of the brainwork/coding was from Yoh. Because of the unique nature of our website, we weren’t able to always work off what we learned in class and had to rely on the genius of Yoh/Erin/Ryan. We’re very grateful for that, but wish we had more tools ourselves to do more of the foundational work.

Demographic charts

Most people between the ages of 16 and 65 have access to a car and can drive. Adolescents and many of the elderly, however, cannot drive, and therefore often depend on transit to make their way around town. In addition to illustrating the population density of all age groups within each census tract in Los Angeles County, the map allows a user to click anywhere on the map to see an age profile for the tract. The map uses 2010 Census data and shows the proportion of each census tract that is less than 5 years old, 5 to 17, 18 to 21, 22 to 29, 30 to 39, 40 to 49, 50 to 64, and age 65 and up. Those neighborhoods with more youth and more elderly have many residents who cannot drive because of their age, and would thus benefit from better transit access.

Here is an interactive window the the live map and a link to the full map:

Link to website.

I got everything to work but the website looks terrible. I plan to do some formatting soon. I want to get the arrow to stop bouncing, get the highlighted census tract to go away when you click a new one, and change the labels in the google graph so you can see the ages better.

 

Week 8: Website Assignment

The Proposed Mid City Bus Stops website just got a little bit more interesting. Now users can not only toggle amenity layers on and off, but they can also assess the areas they’re looking at based on selected demographics (from 2000 though, yikes…not enough time to produce nice updated shapefiles!!). In addition, users that have a better sense of where they want to look at can search addresses and zip codes. Fun times for everyone involved.

PS: The messy bus stop stuff from last time is gone. Perhaps I can work it out in the future.

Itching for more? Click HERE.

Week 8 Bus Map

Click on the image above or click here to access the full website.

A new function was added to our website. Now you can draw a chart to get the detail breakdown of population with age over 60. To create a chart, simply click on the map anywhere near the proposed bus stops. A chart will appear under the “chart” tab on the side display.

<Note: Move the cursor over the chart to see the full label.>

Scholz Week 8 Website Assignment

Scholz Website Week 8 Screenshot - Click to open full page in new tab

This week I added Google Charts functionality to the map.

Progress made this week includes…

  • Fixes to problems with week 7’s map:
  1. No big changes.
  • Added functionality:
  1. On clicking, Google Chart data for racial demographics appears in an infowindow.
  2. Dragging the bouncy marker around the map works to see the chart in different areas.
  3. The census block being shown in the chart is highlighted in the color which represents its largest racial demographic in the popup Google Chart (i.e. polygon will be same color as the largest slice of pie.)
  4. Added source links to Google Charts and Census 2000.
  • Possible improvements
  1. Building more layers on top has made the site slower every week. I think the abundance of US-scale arcGIS layers is the biggest culprit, but I wasted too much time on them to remove them now!
  2. Still ugly formatting. Vertical layout a result of using “narrow-screen” lab monitors, but causes wasted space on typical widescreen monitor. Scaling in and out makes the checks/radios too big for their britches.
  3. Legends for arcGIS layers.
  4. Making the Google Chart infowindows look better.