Version 13 (modified by Fran Boon, 14 years ago) ( diff )


Pakistan Developers

If you have skills in Python, JavaScript (jQuery, Ext &/or OpenLayers) or CSS then you're most welcome to help with code.

Getting Started

Open Tickets

Please feel free to go ahead and resolve any of these tickets

Open Tickets in Trac

Feature Requests


  • Fix Clustering: #498
  • Popup to add Location by placing cursor on Map: #487
  • Hierarchical Autocomplete for Locations
    • Needs to have the Province level made a dropdown as not many provinces (& only 2 which are affected)
  • Import Locations
  • Lock down L1-L3 Locations
  • De-duplication of existing locations: #482
  • Customised Popups for Incidents, Assessments & Requests
    • Hide fields which aren't so necessary to make the critical ones stand out
  • Fresh water source PoIs
    • Water FeatureClass is there in the Programme FeatureGroup, so can be added already although a nicer UI would be great
    • Could also have a custom map query which displays a Water layer for all Shelters which provide Water Services
  • Setup GeoServer & import GeoData into that for more advanced GIS: #497


See: BluePrintInventoryManagement

Shelter Registry

  • On the map, where it shows the shelter, it should show the comments as well, so that one could easily find the requisite facilities. These facilities should be searchable though.
  • Move School Reports to CR (they are Shelters) (-> PTressel)
    • When adding a Union Council from a School Report, would be nice to have the Parent pre-populated too
  • Link CR to RMS
    • We can use auto complete in the Shelter/Relief Camp text box, as the number of shelters would be large; or we can use Ajax to populate the combo box of shelters that are registered at a location, after the user chooses the location.
  • Provide Estimations of Requirements


Incident Reporting

  • .represent for irs_iimage.image as a thumbnail (like for gis_marker)
  • Provide normal users with a simplified set of options for Category
    • Full set of options provided to Editors who can thus refine the original classifications
    • need a simplified list & a mapping to which of the detailed list they should default to




  • Would be good to write a custom PDF writer for this format of report so we can consider getting people to enter data into DB directly.
    • split column headers
    • (dominic) A nice printable HTML works as good as custom PDF, but can be achieved sooner
  • PDF Importer?
  • Test the XForms controller with component resource to have OCRable forms to collect this info

Rotary Club

Rotary Club are training 750-1000 volunteers to collect data.

  1. We should be able to register volunteers, and assign them to geographic regions. This would help us query and know the number of people working in each geographic area.
  2. Volunteers belonging to a group (like geographic area) could then be sent messages via SMS service. So an interface to let us do that that would be great.
  3. When our volunteers go out, they would enter data about the status of inventory at their locations, and items required urgently. They would also be able to update the status of a shelter, in that they may setup a place as a shelter and provides its Lon/Lat, or they may remove a place as shelter for it may have been inundated too.
  4. We want to record damages to people/life, and property. Currently, we can record life losses in Incident Reporting, while property losses can be registered in Situation Reports & Assessments.
  5. We can also record loss to farm animal and cattle. There could be (a) field(s) to do that. Instead of going for a table of animal and then entering the number of lost animals, we could give an open text field.
  6. We want to see the Situations, Assessments, Schools and Flood Reports to be visible on the map as well. Can that be done?
  7. We would love to see an option where we could define a warehouse/shelter/school, where we could mention the inventory available there, and their count. This feature is available in Agasti. If provided, our volunteers would be able to trace themselves the items they need and where they are placed.
  8. Missing Persons:
  • When adding a new missing person, we would need to provide his hometown (from where he was lost) and the location of his residence. Like someone could be missing from a camp/shelter in Peshawar, while his residence would be in Swat.
  • When reporting a missing person, we should be able to provide his photo too. This should be optional.
  • An option should be there, like a status/flag, to tell if the person has been found. Additional information like “where from” would be an added plus, but not essential.
  1. When entering a shelter or inventory, we would like to identify the city/location where it is located. This is the first anchor of reference. Also, we should be allowed to (optionally) provide coordinates, or point the location on the map. That way, it should be visible on the map when someone takes a view of the map with shelter, inventory and incident overviews. This would be very helpful.
  2. Since I can see the situation and incidents are different in the system, “Situation” should also be available in the map overlays.


Want to be able to collect data on offline laptops & sync to base

  • This means that the schema for this module is pretty fixed as we can't update remote laptops
    • Extra data can be incoporated into comments fields for transferring to new optional fields centrally by-hand
    • Can still develop UI tweaks to ease data entry (just won't be visible to remote laptops): Labels/Help
    • Can still develop Reporting functionality
    • Can still develop other modules
  • Power may be an issue, so best to have printed copies of the Assessment Tool as well
  • Sync process should be tested thoroughly (even if kept to a very simple Data upload facility)


  • Outbound to alert teams (working with a local telco to get details)
  • SMS inbound for them to report incidents (separate to the general public whose reports we can pull from Ushahidi so can use the general shortcode)

After Action Notes

  • Move to deployment_settings control:
    • Locations Hierarchy
    • Languages (For Local Location Names & Language Bar)
    • Enable ACLs (e.g. DVI, Editor, MapAdmin)
  • Mapping
    • See if we can convert Mapping API to use a JS file in static which is merged with a bunch of JS vars written out in views
      • makes it faster to develop since no need to keep restarting server for module changes
      • makes it easier for OL devs to help out without needing to understand Python
      • May be hard due to so many different options available to us!
        • Break it up into snippets again...
    • Clustering
      • DRY instead of Copy/Paste
      • Cluster across Vector types (needed for changing filters without map-refresh anyway)
        • Major rewrite! Do at same time as porting to JS with vars? (along with the refreshing of Vector layers without full server reload)
  • Make Index pages (& a space inside rheaders of other pages) into Wikis so that Editors can edit online docs more easily
  • Embed Potlatch & Wikipedia pages so that edits of this kind of data can be done 'upstream' in common sources


Attachments (1)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.