FOR ARCHIVAL PURPOSES ONLY

The information in this wiki hasn't been maintained for a good while. Some of the projects described have since been deprecated.

In particular, the "Ushahidi Platform v3.x" section contains information that is often misleading. Many details about this version of Platform have changed since.

This website is an extraction of the original Ushahidi wiki into a static form. Because of that, functions like logging in, commenting or searching will not work.

For more documentation, please refer to https://docs.ushahidi.com

Versions Compared

Old Version 1

changes.mady.by.user Angela Oduor Lungati

Saved on

compared with

New Version Current

changes.mady.by.user Angela Oduor Lungati

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

-Aggregating reports by area, neighbourhood, region, use a geographic base layer, perhaps adding a heat map

-Simple bar charts would be effective

-For health research tracking the outbreak of a disease, knowing the frequency of reports and being able to export visualisations to PDF (to show decision-makers) would be useful. 

-Having a time slider to control the timeframe of the visualisations would be useful (although wouldn’t work on mobile)

-On the map, making the cluster marker into a pie chart (or maybe making it show a pie chart on hover) detailing the categories of reports in that cluster (e.g. www.fspmaps.com)

-Being able to know the severity level of different reports would be useful, either by marking each category with a severity level, or having unique categories for severity

-The ability to build your own visualisation report (e.g. “I want a bar chart showing X, and 2 pie charts showing X and Y”) would be a good way to let people have custom dashboards for their deployment. They could save the settings for their visualisation report and reload it when necessary, or switch to a different saved visualisation report.

-D3 could be used, also HighCharts. HighCharts has a tricky licence for for-profit companies, so would need to consider legs implications (will for-profit companies use V3, how does the licence work in this case)