bchen10

I've compiled a brief overview of some of the tools/resources. I'm not entirely sure what you might be looking for, but I've listed some of the key features on each platform so you can figure out what your needs are.

##Breeze This one is probably my favortie out of the bunch, but the limitation is probably cost. Depending on the amount of users, cost will increase as you add users. Although I tried it for free and the interface is simple, there's a nice calendar view, and you can breakdown projects however you want (teams, tasks, goals..etc).

##Zube This one integrates well with github. This platform is like waffle on speed. Its free and open source and there are additional features like "burndown" where you can check analytics. Only con is that this tool seems like it's more project based and team based.

##Open Project This one costs money as well, but I thought the most useful tool on this platform was

bchen10

Title: Open Roads

##The issue Improving road network data is foundational for effective national, regional, and local infrastructures. They offer access to several important landmarks that include schools, clinics, and much more. The lack of quality road data for policy makers and government officials can be problematic when it comes to making big decisions about road development for a region.

What we did

We partnered with the World Bank to build a set of road analytic tools that allows the Philippine government to map roads, be able to maintain data on current networks, visualize project investment opportunities, and provide important road insights for decision makers.

bchen10

Hi Kai

Thanks for your feedback. We made additional revisions to the Editor based on your helpful notes. Some of the problems we were trying to tackle in this round include:

• Scaling the menu bar for future content
• Making sure the menu bar is evident to the user, but also collapsible and out of the way for users who are trying to edit the map.

You'll see below, we've combined the map overlay and basemap layer options into one menu bar. Combining the menus uses less map real estate and gives the user the ability to view more of the map.

We switched to a vertical panel because it's a common pattern to show menu options in the left-column (similar to sites like Amazon, ebay, Target, Zappos). Placing the menu where users are expected to go for information increases visability and usability.

bchen10

Hi Katrin,

Over the past few weeks we've made great progress in designing and implementing the data overview site. The deliverable below includes:

• New design of the overview landing page based (without country pages)
• Four interactive visualizations linked to current database.
• [ backend stuff ]
• [ backend stuff ]

Design

bchen10

Hi Kai,

We made some revisions based on the last round of feedback we received from you. You'll see below we made changes to the basemap layer menu and the map overlays so that we can better call out some of the main functionalities of the site.

We placed the overlay options at the top because they are the priority menu options that give users the choice to turn on/off the individual layers to road networks, projects, local gov.,...and etc.

For basemap layers, we created an exapndable thumbnail pane so users are able to preview the basemap layers that are available. This gives users the ability to quickly view other options in the case that DigitalGlobe or Planet Labs don't have satellite imagery available.

Olaf has filled me in on the discussion you're having about using other satellite and drone imagery, so I understand that is something we'll have to think further about. The mockups below are designed to scale as we make further decisions about satellite imagery.

bchen10

UX write-up

Over the course of the discovery and design phase we used different visualization methods to help us gain a better understanding of our users and the product workflow as a whole. We’ve created user profiles, workflow maps, and wireframes to help us build a better and more user-centric platform.

Defining our users

We started by sorting our users into different levels of engagement depending on what types of services they’re looking to receive. This step gave us a better understanding of the types of expectations and actions each user will face when on the platform.