Join the user mailing list and let us know: http://groups.google.com/group/opentreemap-user
Or, try our Gitter channel:
For full installation instructions, see the Github wiki.
Alternatively, you can also use the otm-vagrant project to get started. While not recommended for production, otm-vagrant greatly simplifies getting a development environment for testing and contributing to OTM locally.
This project requires several environment variables, to provide API keys for several services.
ROLLBAR_SERVER_SIDE_ACCESS_TOKEN=....
GOOGLE_MAPS_KEY=...
ROLLBAR_SERVER_SIDE_ACCESS_TOKEN is a token for Rollbar.
GOOGLE_MAPS_KEY is a browser key for the Google Maps Javascript API, which can be obtained here.
This repository (ie, otm-core) is but one of a few separate repositories that together compose the OpenTreeMap project. Others include:
- otm-tiler - map tile server based on Windshaft
- otm-ecoservice - ecosystem benefits calculation service
- otm-ios - An OpenTreeMap client for iOS devices.
- otm-android - An OpenTreeMap client for Android devices.
The REST API that provides data for the native mobile apps is documented in api.md
OpenTreeMap has a long history. These repositories still exist, but are deprecated and no development is happening here moving forward.
- OpenTreeMap - Otherwise known as "OTM1", this is previous generation codebase of OpenTreeMap. It has been entirely superceded by this repository and the others listed above. However, there are some live tree map sites still running on the old OTM1 code, and so we have left it up for archival purposes.
This application includes code based on django-url-tools, Copyright (c) 2013 Monwara LLC.
Portions of OpenTreeMap are based upon work supported by the National Institute of Food and Agriculture, U.S. Department of Agriculture, under Agreement No. 2010-33610-20937, 2011-33610-30511, 2011-33610-30862 and 2012-33610-19997 of the Small Business Innovation Research Grants Program. Any opinions, findings, and conclusions, or recommendations expressed on the OpenTreeMap website are those of Azavea and do not necessarily reflect the view of the U.S. Department of Agriculture.