Working Through the Zoo Myers Rainforest Conservation Project
I spent three weeks last year going through the Zoo Myers Rainforest Conservation Project Walkthrough from start to finish, and honestly it is not as smooth as the documentation makes it look. The basic idea is solid — it is a structured conservation tracking system designed for zoological institutions working on rainforest habitat preservation, species recovery, and field partnership coordination. But the execution has some rough edges that nobody really talks about. The system organizes conservation work into phases: baseline assessment, species target selection, habitat mapping, field partner alignment, and then ongoing monitoring with quarterly reporting. You enter each phase through a web portal, and each phase requires documentation before you can advance. That structure makes sense on paper. In practice, the transition requirements between phases are inconsistent — sometimes you can proceed with partial data, other times the system locks you out until you upload three separate documents that seem redundant. My main use case involved coordinating a multi-species recovery program across three partner sites in Central America. The portal lets you attach geospatial data, but the coordinate system handling is surprisingly limited. It defaults to WGS84 and will not accept UTM zones without manual conversion. I wasted about half a day converting legacy survey data because the system would silently reject the coordinates rather than show an error message. The workaround was to batch-convert everything to decimal degrees first using a quick Python script with pyproj, then paste the results in. Much faster than doing it manually in Excel.
Here is something most people miss: the quarterly reporting module generates summary tables automatically from your field data, but it only pulls records where the status field is explicitly set. If you forget to update individual animal records after a health check or relocation, those animals effectively disappear from the report. I learned this the hard way when our Q3 report showed a 40% drop in tracked individuals that turned out to be entirely due to stale status fields rather than actual mortality or escapes. Going forward I add a status audit step before every report submission — it takes ten minutes and saves you from looking incompetent in front of your board. The integration with external research partners is another area worth discussing. You can invite collaborators through the platform and share dataset access levels, but the permission model is coarse. It is basically full access or nothing at the partner level. There is no granular field-level restriction. If you are sharing sensitive species location data with multiple organizations, this becomes a real problem because you cannot easily withhold precise coordinates from general partners while giving them the broader habitat information they need. I ended up creating a shadow spreadsheet with approximate ranges and sharing that separately, which defeats some of the purpose of using the platform in the first place. The vendor is aware of this gap and has it on their roadmap, but there is no timeline yet. One more thing that will save you time: the data export function supports CSV and GeoJSON, but the CSV export omits any nested or multi-select fields entirely. If your project uses the species tags or the multi-category habitat classification system, those columns will be blank in your export. You need to use the GeoJSON export instead and convert it, or request a full dump through the support ticket system which generates a database-level backup. That process usually takes about two business days but gives you everything.
As for whether this is the right tool for your situation, it depends. If you are a mid-to-large zoo or aquarium with dedicated conservation staff and regular field partnerships, it is probably worth the learning curve. The documentation, while thin, improves once you get past the initial setup phase. If you are a small institution doing occasional conservation work with no dedicated staff, you will likely find the overhead exhausting relative to your output. In that case, a simple shared database or even a well-structured spreadsheet might serve you better until your program scales up. The platform does have one genuine strength that is easy to underestimate. The longitudinal tracking of individual animals across institutions is actually quite robust. If you transfer specimens between zoos or participate in cooperative breeding programs, the audit trail and movement history are clean and complete. That part works exactly as advertised. The field data collection and reporting side is the weaker half of the system, and it shows. I do not have a public download link for this since it is a specialized institutional platform requiring application and verification, but the main portal is accessible through the Zoo Myers conservation network. You apply as an institution, not an individual, and the approval process typically takes one to two weeks. If you are reading this because someone at your organization mentioned it, just forward this to the right person and tell them to watch out for the coordinate system issue and the status field trap before it costs them a report.
Get the Full Details
