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.

Week 7: Website Assignment

In less than 10 hours, I’ll be on a plane to Israel! Hence the need to finish this assignment before Monday. Don’t worry, it won’t be all fun and weddings. I’ll record the trip to use in Geostories! How’s that for dedication?

For my two published ArcMaps, I chose LA County 2006 data for hospitals and parks and uploaded them to Whippet.

 

Hospitals below:

Parks!
I added toggle layers for hospitals and parks. Only blub was the parks don’t show up too well since they’re the green color. Changed the map to SATELLITE and that helped a lot. The small bug is the toggle for parks doesn’t seem to work 100%.

The latest assignment can be viewed here!

Thanks and see you in a two weeks!

 

Week 4: Group Proposal Update

With feedback from E.Y. Ventures, GeoStories has decided to change/add the following:

1) We will focus more of our efforts into website functionality, and add design features later as time permits. As a result, new wireframes were created.

Front page:

Brief description and instructional video. Will add a ‘sign in’ feature to have a GeoStories account to create/edit stories. To be Added: Navigation bar with ‘Sign In’, ‘Start Your Story’, ‘Search/Story Library’, ‘Contact Us’.

Input Page: Here is where our clients will build/edit their stories after signing in. The ‘Sign In’ page will require users to use their Gmail accounts to use their Picasa accounts where their personal pictures and videos are stored.

The Input Page will ask for information such as Place/Address, Time, Media Upload (Pictures/Video) and finally Chapter Text. Option to add as many ‘Chapters’ as the story permits (denoted by carrots on either side). Concerns: Converting Place/Address information to latlong, geocoding pictures/video.

Story Page View: Prototype story view after client has input a minimum of 3 Chapters. To be Added: Once you click on a chapter, icon on map will appear with info window pop up with media and chapter text with option for multiple pages/related media. As you move through the chapters, map will move (possible line linkage between icons/nodes) to next icon with new info window.

2) Still researching: Use of Picasa and Youtube API’s. Lat/Long conversion, Infowindow with text/media and mapping movement between icon/nodes. Will look into other potential API sources and how to further simplify our design.

3) Will start building forms (input page) and test story building functionality.

Week 3: Group

Proposal Topic and Discussion (same from last post): GeoStories is a Los Angeles-based consortium of Urban Studies and Culturomic experts working with clients to create interactive, experiential mapping solutions using web-GIS technologies. In particular, GeoStories specializes in combining narrative and cartographic practices to create engaging, consumer-facing digital map interfaces.

For their newest client, UrbanStudies206B, GeoStories looks to create a “StoryEngine” that would allow users to create their own multimedia, narrative-driven maps. The StoryEngine site—whose motto is, “Tell Your Story, One Place At a Time”—would in essence be an interface that prompts a user to input information and media that would then be used to almost immediately generate a personalized, digital map narrative.

Wireframes

1) This will be our awesome website frame:

2) Imagine above cool frame in the following wiresketches:

Functionalities: The interface would utilize a function asking the user to input a minimum of 5 locations, each with written descriptions (stories), and with the option of attaching media such as images/video. Once finished, and the user hits the “Mapify” button, a digital map incorporating the user’s designated locations, descriptions, and media would automatically be generated in nifty info windows. The map could then be easily edited, shared or downloaded.

API’s:

Google Earth (https://developers.google.com/earth/)

Google Maps (https://developers.google.com/maps/)

Historical Maps API? Youtube? Picasa?

Milestones – By Week 6: Full wireframe sketches of website. Want to have identified all API’s (specifically, historical map API’s). Figure out how to use the old vintage book image as a frame for website. By Finals: Fully functional website with a sample stories.

Concerns: 1) getting historical map API’s 2) learning enough web GIS to create this website 3) creating a working interface where users can input information we can convert (i.e. address —> lat/long coordinates) 4) storage space for user pictures/videos or would requiring picasa/youtube accounts take care of this?

Week 3: Website Assignment

Ongoing website assignment updated with current metro route info. As shown above, you can click on a bus # to generate the route name, as well as the map route with purple bus icons. For Uyen’s proposed metro stops, routes 33 and 733 run along Venice Blvd. While this may compete with the proposed metro stop, there is a definite lack of metro routes along the rest of the proposed metro route (ex. Pico Blvd & Bundy Dr.). The proposed metro stop will address this need and increase access to transportation to the area. The full website can be found here.

Week 2: Group Proposal

 

GeoStories is a Los Angeles-based consortium of Urban Studies and Culturomic experts working with clients to create interactive, experiential mapping solutions using web-GIS technologies. In particular, GeoStories specializes in combining narrative and cartographic practices to create engaging, consumer-facing digital map interfaces. GeoStories is led by:

Andrew Pogany — Chief Experience Officer (CEO):

As CEO, Pogany leads business development and account management, and is thus responsible for determining the best ways to effectively address each client’s particular goals. Pogany works closely with GIS technologists as well as the SST to create immersive, interactive, and sustainable digital mapping solutions.

Uyen Ngo — Senior Story Teller (SST):

As SST, Ngo is responsible for collecting, curating, and managing the materials necessary to create personal stories to share with the world. As such, she works closely with clients as well as individuals to determine the required content and to ensure that content’s quality and security.

——-

For their newest client, UrbanStudies206B, GeoStories looks to create a “StoryEngine” that would allow users to create their own multimedia, narrative-driven maps. The StoryEngine site—whose motto is, “Tell Your Story, One Place At a Time”—would in essence be an interface that prompts a user to input information and media that would then be used to almost immediately generate a personalized, digital map narrative. For example, the interface would utilize a function asking the user to input a minimum of 5 locations, each with written descriptions (stories), and with the option of attaching media such as images/video. Once finished, and the user hits the “Mapify” button, a digital map incorporating the user’s designated locations, descriptions, and media would automatically be generated. The map could then be easily shared or downloaded.

Week 2: Website Assignment

Above is a further detailed map of my 5 proposed metro stop. In this post, clicking and zooming in on each metro stop highlight such amenities as grocery stores, restaurants, goods & services and bus stops. Clicking on the various colored amenities or the bus stop tacks will bring up a pop up window further describing the point of interest. The red line connecting the 5 metro stops indicates the proposed route. In this post, the map is not centered. If you click on the fullscreen version below, the map should be properly centered.

fullscreen version: http://www.yohman.com/students/2012/uyen/week2/namespace.html

New coding formats the interactive metro stop with a new header and brief summary and legend at the bottom of the map.