Community Maps — Past, Present, and Future Developments

Community Maps, developed by Mapping for Change and UCL, is a mapping platform that allows many to map what interests them and be a part of the decision making process. From mapping dog fouling incidences in Poland to identifying grass roots climate action initiatives in the United Kingdom, Community Maps is helping people make a difference in their local areas. After 7 years of running on the same code base, it was decided that the platform needed to be rebuilt from the ground up, utilising current technologies, to ensure its robustness and continued longevity. This talk, given by two of Community Maps’ developers, will discuss the past, present and hopeful future development efforts of the platform and want to hear from potential end users, project partners, and developers (of all skill ranges) as to what you would want to see the new platform do.

Transcript

1. Community Maps - Past, Present, and Future Developments Patrick Rickles & Oliver Roick
2. Inception & Establishment
3. Initial and Continued Development
4. Programming Difficulties
5. Eco21.PL
6. Royal Docks Noise Mapping
7. UK Climate & Community Action Map
8. Rebuild & Redevelopment
9. Specifications
10. User permissions h"p://www.flickr.com/photos/ta"oodjay/2529709554  
11. Flexible data structure h"p://www.flickr.com/photos/projector/2845108679  
12. Reviews & Quality Control h"p://www.flickr.com/photos/sarahreido/3120877348  
13. Easy-to-use administration h"p://thingsorganizedneatly.tumblr.com/post/61224142560/submission-­‐tools-­‐i-­‐use-­‐for-­‐bookbinding  
14. Security h"p://www.flickr.com/photos/kenpower/4900658261  
15. The idea
16. ApplicaJons   System Design Public  API   Admin  +  AJAX  API   Backend   AuthorisaJon   Model   Web-­‐based     administraJon   Community  Maps   front-­‐end   EpiCollect   Client-­‐side   components   Server-­‐side   components  
17. Data Model Feature   ObservaJon   Project   Feature  type   View   Comment   ValidaJon  of   contribuJons   Access  to   contribuJons   Field   Usergroup   Can  edit   Can  read   Can  view   Admins   Contributors  
18. Current State Backend   AuthorisaJon   Model   Web-­‐based     administraJon   Community  Maps   front-­‐end   EpiCollect   Client-­‐side   components   Server-­‐side   components   ApplicaJons   Public  API   Admin  +  AJAX  API  
19. Current State
20. What’s next
21. New front-end
22. Public REST-ful API {      "project":  {          "id":  26,          "status":  0,            "name":  "Public  Project",            "description":  "Test  description"            "creator":  {              "id":  31,              "username":  "eric",                "first_name":  "Eric",                "last_name":  "Cantona",                "email":  "eric@cantona.fr"          },            "created_at":  "2014-­‐01-­‐14T14:05:51.349Z",            "isprivate":  false,          "everyonecontributes":  true,            "admins":  {              "id":  17,                "name":  "Administrators",                "users":  [                  {                        "id":  12                        "username":  "george",                          "first_name":  "George",                          "last_name":  "Best",                          "email":  "eric@best.uk"                  },  {                      "id":  11,                      "username":  "eric",                        "first_name":  "Eric",                        "last_name":  "Cantona",                        "email":  "eric@cantona.fr"                  }              ]  
23. Integration with platforms
24. Open Source
25. Future Prospects
26. Integration & Partnerships
27. Work in Progress