This is a testing site only. See the live Public Lab site here »

Public Lab Wiki documentation


This is a revision from March 20, 2015 20:18. View all revisions
4 | 80 | | #9491

The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own!

Sign up using the form to the left, or visit the Google Group directly

How to contribute

We are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members!

Start by reading our contribution guidelines

Public Lab Software

Project Description Source Code
MapKnitter Assemble aerial images into maps. github:publiclab/mapknitter
Spectral Workbench Material analysis using DIY spectrometry. github:spectral-workbench
Leaflet.Illustrate Leaflet plugin built for MapKnitter. Enables text annotations on Leaflet maps. github:manleyjster/Leaflet.Illustrate
Leaflet.DistortableImage Leaflet plugin built for MapKnitter. Enables images to be distorted. github:publiclab/Leaflet.DistortableImage This very website! github:publiclab/plots2
Infragram Analyze plant health with infrared imagery. github:p-v-o-s/infragram-js
MapMill Upload and collaboratively rank large batches of aerial imagery. github:publiclab/mapmill

Public Lab is on Github at:

Google Summer of Code

Lots of development on Public Lab software happens as part of the GSoC program, supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program.

Read more at, and review recent GSoC proposals/projects at

Testing server

We have a plots2 testing server available for testing larger code changes and database migrations; please contact for details, and submit a public key for access. General testing procedure is as follows:

  • thoroughly test on local copy, with seeded database
  • get ssh access to

  • reimport db if needed (web@ can help with this)

  • create new git branch in /home/warren/sites/
  • pull in new changes
  • rake db:migrate etc if needed
  • run rake test
  • run ./restart from rails root dir
  • manually compare with
  • wash, rinse, repeat
  • check with web@ about deployment to production once you're ready!

Installation videos