<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tree Disease on QField - Efficient field work built for QGIS</title><link>https://qfield.org/tags/tree-disease/</link><description>Recent content in Tree Disease on QField - Efficient field work built for QGIS</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://qfield.org/tags/tree-disease/feed.xml" rel="self" type="application/rss+xml"/><item><title>QField for Forest Health Monitoring</title><link>https://qfield.org/solutions/forest-health-monitoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://qfield.org/solutions/forest-health-monitoring/</guid><description>Record pest, disease, dieback, and tree-condition observations in the field with QField, QGIS, and QFieldCloud, fully offline.</description><content:encoded><![CDATA[<h2 id="field-workflows">Field workflows</h2>
<p>Forest health teams use QField to record and monitor tree condition:</p>
<ul>
<li>Pest and disease observations with species, symptom, and severity</li>
<li>Defoliation, dieback, and crown condition assessment</li>
<li>Tree mortality and deadwood recording</li>
<li>Affected-stand delineation as polygons</li>
<li>Photo documentation against individual trees and stands</li>
<li>Repeat monitoring at fixed locations to track change over time</li>
</ul>
<h2 id="built-for-repeat-monitoring">Built for repeat monitoring</h2>
<p>Forest health is a question of change over time. A single survey tells you what a stand looks like today, but the value comes from coming back and seeing what has shifted. QField stores each observation as a structured record with its location, attributes, photos, and capture time. On the next visit, the previous records load straight onto the device, and the live GPS position guides crews back to the same trees and stands. The result is a consistent time series rather than a pile of one-off surveys.</p>
<h2 id="one-workflow-with-qgis-and-qfieldcloud">One workflow with QGIS and QFieldCloud</h2>
<p>Set up the health-survey project in <a href="https://qgis.org" target="_blank" rel="noopener">QGIS</a>
 once, push it to every device through <a href="https://qfield.cloud" target="_blank" rel="noopener">QFieldCloud</a>
, and run conflict-safe sync at the end of each day. Crews work offline for as long as the survey takes, then sync when they next come into office connectivity.</p>
<h2 id="forestry-teams-using-qfield">Forestry teams using QField</h2>
<ul>
<li><a href="/success-stories/ghana-deforestation/">Young farmers reduce deforestation by 71% in Ghana</a>
, where community-based monitoring teams use QField in the Tano Offin Forest Reserve</li>
<li><a href="/success-stories/?filter=forestry">Browse all forestry success stories →</a>
</li>
</ul>
<p>Looking for the broader picture? See <a href="/solutions/forestry-and-silviculture/">QField for forestry and silviculture →</a>
.</p>
]]></content:encoded><category domain="categories">Environment, Agriculture &amp; Natural Resources</category><category domain="tags">forest health</category><category domain="tags">pest monitoring</category><category domain="tags">tree disease</category><category domain="tags">dieback</category><category domain="tags">defoliation</category><category domain="tags">crown condition</category><category domain="tags">tree mortality</category><category domain="tags">forest condition survey</category><category domain="tags">mobile GIS</category><category domain="tags">QGIS fieldwork</category><category domain="tags">offline forestry mapping</category><category domain="tags">forest health monitoring</category></item></channel></rss>