nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Open-source Forestry Toolkit for ArcGIS Pro – fieldwork, drone mapping, fire hotspots, and forest analysis

Ahmed_Seko

Hi everyone,

I’d like to share a small open-source project I’ve been working on called Forestry Toolkit, an ArcGIS Pro add-in built around practical forestry and fieldwork workflows.

I originally started it to simplify some of the repetitive GIS tasks I encounter in forestry work, and it gradually grew into a collection of tools inside ArcGIS Pro.

Some of the current features include:

Drone flight mission planning
Timber cruising Excel import
Tree and oil palm detection from orthophotos
Land clearing detection
Road/trail extraction
NASA FIRMS active fire hotspots
Biomass and carbon estimation
Slope classification
Riparian buffer checking
GPX export
Cruising summary reports

The add-in uses C#/.NET for the ArcGIS Pro interface and a Python backend running through ArcGIS Pro’s own Python environment for some raster and detection workflows.

Tree detection is still experimental and has not yet been fully validated against field ground truth, so I currently treat its results as a first-pass analysis rather than a final inventory count.

The project is open source under the MIT License, and I’m continuing to improve it based on practical use cases.

GitHub : https://github.com/Ahmedseko/forestry-toolkit

I’d really appreciate any feedback from the ArcGIS Pro / forestry / remote sensing community, especially suggestions around workflow design, ArcGIS Pro SDK implementation, or ideas that could make the toolkit more useful in real field operations.

Thanks!

Find more posts tagged with

Analysis

Desktop

Geoprocessing

SDK

Mapping

Spatial Analysis

Python

Raster

Extensions

Comments

GintautasKmieliauskas

Hi,

Thanks for sharing project.

I have few suggestions for you from developers side.

Localization. Your style of localization takes a lot of typing: language property, converter, converter parameter. Your Text property looks like that:



<Expander Header="{Binding IsHelpEnglish, Converter={StaticResource UiText}, ConverterParameter=LandClearingParams_Header}" Margin="0,0,0,8">

If you use some nuget package for wpf localization or your own localization developed on official WPF localization suggestions, your Text property could look like that:

<Expander Header="{lex:Loc Key=LandClearingParams_Header}" Margin="0,0,0,8">

Your application could have more than 2 languages. Each language content will be stored in separate resource file. Easy to change languages at runtime.

2. Main dockpanel. I suggest you instead of TabControl use ListBox with esri style Esri_ListBoxPanelIndicator. You will get ArcGIS Pro style tabs. Take a look to ArcGIS Pro SDK Community sample CustomCatalog. Each your tab content could be stored in different DataTemplate's with it own xaml, code-behind and viewmodel. It would be easier to read and manage code instead of one class per all tabs.

Ahmed_Seko

Hi Gintautas,

Thanks again for the detailed suggestions. I actually tried implementing both approaches to see how they would work in the project.

For the localization, your suggestion was very helpful. I simplified the current implementation using a small markup extension, which makes the XAML much cleaner and easier to maintain.

I also tried replacing the current TabControl with ListBox and Esri_ListBoxPanelIndicator, following the CustomCatalog sample. Unfortunately, it didn’t work very well with the current dockpane. With the number of sections I have, the tabs became too narrow and the overflow behavior produced some layout issues, including blank items instead of properly displaying the remaining tab names.

I experimented with the layout for a while, but couldn’t get a result that was better than the current TabControl, so for now I reverted that part. I may revisit it later if I find a cleaner way to handle the larger number of sections.

Really appreciate the suggestions though — trying them directly was useful and also gave me a better idea of where the current UI architecture could be improved.

GintautasKmieliauskas

My suggestion to use localization nuget or etc. is valid not only for xaml, but and for c# code too.

For example to display message you can do like that:



MessageBox.Show(FrameworkApplication.Current.MainWindow, Properties.Resources.YOUR_MESSAGE_ID, caption, MessageBoxButton.OK, MessageBoxImage.Information);

Code automatically takes selected language resources. Same resource files as for xaml.

Do you have screenshot with ListBox with Esri style implementation? I had some successful implementations (5 and more tabs). I will try to adopt your code with ListBox. If I succeed, I will send you solution.

Ahmed_Seko

Hi Gintautas,

Thanks, you’re right about the localization also being useful from C#.

For now I’ve kept the runtime language toggle I already use and simplified the XAML with a small markup extension, but I’ll also look further into using shared resources so the same strings can be accessed cleanly from both XAML and C#.

Regarding the ListBox, I actually implemented it with Esri_ListBoxPanelIndicator based on the CustomCatalog sample and tested it in ArcGIS Pro. It works correctly while the dockpane is wide enough, but once it becomes narrow and the ... overflow appears, the flyout shows blank rows instead of the hidden tab labels.

I also tried replacing the ItemsPanel with a WrapPanel, but the same overflow behavior remained. Since this dockpane currently has 8 tabs, I reverted it to the working TabControl for now.

I’d definitely appreciate seeing your approach, especially since you mentioned having working implementations with 5 or more tabs. I can also share a screenshot of the overflow issue and the implementation I tested.

Here is the implementation I tried:
https://github.com/Ahmedseko/forestry-toolkit/commit/4216c35

And the revert after testing:
https://github.com/Ahmedseko/forestry-toolkit/commit/650c450

Thanks again for taking the time to help with this.

Ahmed_Seko

Hi Gintautas,

Thanks a lot for checking this and for reporting the issue. Really appreciate it.

It’s actually good to know that the strange overflow behavior I was seeing with Esri_ListBoxPanelIndicator comes from the sample/style itself and not from something I broke in my implementation. That also explains why my WrapPanel attempt didn’t really help.

I’ll keep an eye on issue #69 and revisit the ListBox approach once there’s a fix or a better workaround. I still like the ArcGIS Pro-native look, so I’d definitely like to use it again if the overflow behavior gets sorted out.

For now I’ll stick with the current TabControl since it behaves reliably with all 8 tabs.

Thanks again for taking the time to dig into this. Really appreciate your help with the project.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.