The interactive FED-UP application provides a game-like interface that enables children to track their daily food intake as well as where they buy their food.

In 2003 the U.S. Surgeon General reported to a Congressional Subcommittee that “… the fact is that we have an epidemic of childhood obesity.”(1)  Children are eating too much, moving too little, and increasingly consuming a diet of unhealthy foods.  There are many factors that have contributed to this trend, including limited availability of healthy food in an urban environment such as Philadelphia.  Particularly at risk are kids in low-income neighborhoods where local stores often have high concentrations of foods with high-fructose corn syrup and little or no fruits or vegetables.

At the same time that children exercise less and eat worse, they consume more and more technology.  At the University of Pennsylvania School of Design, Professor Amy Hillier is seeking to learn more about the behaviors of these at-risk children, while taking advantage of their increasing technology savvy. Azavea is working with Prof. Hillier to build a prototype application for her FED-UP (Food and Exercise Diaries for Urban Places) project.  This project will take a select group of children and ask them about the “where, what, and with whom” of their everyday eating behaviors.

Building this application presented some new and interesting design challenges.  Historically, Azavea has not built many applications specifically targeted at young users.  We wanted to make something that would be fun and engaging while still getting the job done of collecting the needed information for the FED-UP project.  In user experience design there is often talk of “friction,” which refers to anything that impedes or slows down a user from doing what they want to do, when they want to do it.  With young users the need to build a “frictionless” application is even more important.  Anything that might slow down or distract them could mean they walk away entirely.  In general, reducing friction means focusing on simplicity, but it also means emphasizing what’s important, and playing down what’s not.

Each child participating in the FED-UP project selects the food items they ate and, from a dropdown list, selects where they bought it and with whom they were.

To meet this goal, the user interaction for the FED-UP prototype application takes the “where, what, who” concept literally, and turns each diary entry into a “1, 2, 3” step process that reads more like a sentence than a traditional user interface.  The application also leverages the fact that even young children are hyper-aware of their local environment and can easily navigate a map of their neighborhood.  Allowing kids to use their spatial awareness to find the places they go makes it easier for them than having to search through a long list of location names.

There is a lot of potential for extending this application.  In the future, we hope to make even better use of technology by adding features that would enable users with smart phones to look up food items with their camera or automatically detect their location with the phone’s GPS.

(1) http://www.surgeongeneral.gov/news/testimony/obesity07162003.htm

“Pretty excited” turned out to be an understatement. People loved that they could use Sajara’s geographic search feature to locate historic photos of their neighborhoods. We began receiving wonderful comments and stories from PhillyHistory.org users.

We loved hearing the stories but unfortunately did not have an easy way for users to share their comments with the larger PhillyHistory community. We decided to remedy the problem by adding a new feature to Sajara – a public commenting panel.

New Sajara commenting panel in use on PhillyHistory.org

Enabled on a collection basis, commenting provides a way for the public to share information or opinions about an image with other users via a comment page on the detail view for each photo.  After creating an account with PhillyHistory.org, users can leave comments about the image, respond to comments left by other users, or report abusive comments.  A user’s comment is associated with their user name, and each user name is linked to a public profile for that user.  While a user’s comments are shown by default on their user page, the user can also choose to display their favorite photos, bookmarked searches, and personal information such as a biography or website.  In addition, a user can also sign up to receive other users’ future comments via an RSS feed.

Actually implementing the commenting system turned out to be somewhat complicated.  There are a few different ways to organize comments, including a flat list that shows comments in the order they were entered and a nested tree that shows all the relationships between comments and responses to comments.  Getting it right means understanding your audience.  Our approach with the Sajara software organizes comments into single-tier threads so that users can see simple conversations but not get lost sorting through which ones relate to others.

Sajara commenting feature in the Japanese Gardens of the World sample application of the Sajara software

Commenting systems require quite a lot of ongoing management as well.  Some comments will need reviewing for various reasons, which, on a high volume site, can be an overwhelming task.  Included in the Sajara commenting system are a set of tools that allow the site’s administrators to easily review and handle all the site’s comments.

The public commenting feature is currently available on PhillyHistory.org and Japanese Gardens of the World, the Sajara sample application, and is an optional feature for future Sajara implementations.

Big Map search window in the new version of Sajara

Oh! … and by the way, have you seen the new ‘Big Map’ search window we implemented in PhillyHistory.org (also a new option in Sajara)?  The map view search page features a nearly full screen map with thumbnails of the images displayed along the bottom of the screen.  Flags on the map correspond with each thumbnail, indicating where the photo was taken.  All the original search filters (address, keyword, topics, dates, and more) are still available at the top of the map under the ‘Search By’ menu.

Check both new features out and let us know what you think!

The most powerful tools often begin with a desire to solve simple, everyday problems. At Harvard University, faculty, students, and researchers often found that finding maps and spatial data related to their studies of Africa was extremely difficult. The issue was not that the data didn’t exist. In fact, the Harvard Map Collection has an impressive collection of historical maps of Africa. Many researchers also develop detailed Africa datasets in the course of their work, while other important spatial data is scattered across other organizations. But these maps and datasets had to be tracked down individually, assuming the researcher was even aware of them at all.

View of AfricaMap’s 1959 Ethnographic Map Layer Including Airfields

But at Harvard University’s Center for Geographic Analysis, Professors Suzanne Blier and Peter Bol with Senior Analyst Ben Lewis saw beyond simply creating a common repository for these maps. They envisioned a solution that would bring many of these currently unconnected Africa datasets together in a single, easy-to-access web application that would promote collaboration and enable researchers to learn from other areas of study. By layering the maps on top of each other, a researcher could explore all of the data or knowledge captured in maps from various disciplines. Knowledge of an area of interest could be deepened by maps describing historical, environmental, social, linguistic, or economic data. And by creating a map of scholarly projects focused on Africa, users could discover the work of others with interest in common geographical areas, despite differences in their fields of study. The vision for the Harvard University Geospatial Infrastructure (HUG) platform was born.

Ben Lewis developed an innovative, highly scalable, spatial search and display architecture to address these ambitious goals. By utilizing open standards and protocols, the framework would interoperate in the future with other technical systems used by scholars in various disciplines. By committing to an open source toolset and codebase, the framework could be applied to other areas of the world and be shared with other organizations who could, if they wanted, use and extend the framework. With the vision in place, he approached Azavea and MetaCarta to build the application.

MetaCarta built the map tiling system, while Azavea was asked to flesh out the framework with searching capabilities and some advanced features that presented fascinating technical challenges for us. One of our goals was to enable researchers to search through millions of places (ranging from populated places to physical features) using a straightforward text search, like a Google search, and have the results highlighted on the map. That work began by building a gazetteer, which is a geographic dictionary or directory — like a yellow pages for geographic place names. The initial data source for the gazetteer was the GeoNames database, which is a free geographic database of over eight million geographical names. Users can add or edit place names online, as if it were Wikipedia for place names. GeoNames doesn’t just include populated places like cities or villages, it also includes features such as farms, streams, wells, and schools.

Detail from a historic map of Africa by cartographer Jodocus Hondius, circa 1612. “We were particularly struck by the beautiful juxtaposition of the old and new: seeing an image of a sea creature on the edge of a historical map, layered on top of a modern web map.” – Josh Marcus & Reed Lauber

After processing and filtering GeoNames into a geographical database, we added two ways to view the places on a map. We added a ‘Places’ tab where one can view places by type. Here a researcher can turn on any combination of hundreds of ‘place types’ and zoom to any area of the map, clicking on’ place features’ for information about these places. In addition we made it possible to turn on all ‘place types’ and view them along with the many other layers in the system. We also made it possible to combine place name searches with ‘place type’ queries.

But first we had to tackle a technical challenge: Africa is a huge continent and there are a lot of places to show. The gazetteer has over three hundred thousand populated places, and we needed to figure out how to efficiently display all of them on the map. We profiled two open source mapping servers, one called GeoServer and another called MapServer, for the speed of image generation, and ended up with a conundrum. We preferred GeoServer’s cartography, especially for showing overlapping areas of scholarly study. But we were able to cajole MapServer to generate a map layer of hundreds of thousands of points very quickly. In the end, while we knew it would be somewhat unorthodox to use two mapping servers in the same application, we decided to use both systems for what they were good at: GeoServer for general cartography and MapServer to show the points from the gazetteer. The technology tools were rounded out with PostGIS for storing and searching feature queries, ExtJS for user interface components, and Python to tie it all together.

Once the gazetteer and visualization were in place, we were able to leverage the power of Web Map Service (WMS), an open standard to make web requests for maps, to transform the text search into a search for the geographic points in all of the map layers. The result of a text search could include features from the gazetteer, but also other searchable layers as well, such as the layer of scholarly projects. We added functionality so that a user could search many layers at once, click on the map to “drill down” and return results about different types of features in a single interface, and a range of other tools including a “permalink” that would enable users to share a particular view of the maps and search results with other users or students. The database also includes the geographic extent of research projects that target the African continent.

Now that the first phase of the project is complete, an initial public release of AfricaMap is available online and Azavea will be working with Harvard’s Center for Geographic Analysis to expand this project to apply the same framework to the Boston Metropolitan area. Take a look at the application for yourself. We especially recommend taking a look at the historical maps. We were particularly struck by the beautiful juxtaposition of the old and new: seeing an image of a sea creature on the edge of a historical map, layered on top of a modern web map. Click here to see an early 17th century map from Jodocus Hondius, and view other historical maps in the ‘Map Layers’ tab.

Another interesting way to explore the application is to put yourself in the mindset of a researcher. Imagine you are interested in the economic development of Freetown, in Sierra Leone. The ‘About’ tab has some useful documentation regarding searches and turning off and on map layers. The very detailed basemap (Freetown 2.5k) provides a strong basis for all of your work. By comparing other basemaps (the American Sierra Leone 50k map from the 70s and the Russian 500k transportation map from the 80s) you can observe new development over time. From there, you can draw in whatever other maps that are relevant for your work — some examples would include soils, population, language areas, ethnographic regions, or turn on the projects layer and explore other scholarly projects that have focused on your area. Enjoy!