Closed cdflint closed 4 years ago
Thank you @cdflint, I will resolve the bugs.
It appears the export training data tool pushed out image chips without any accompanying labels. There were around 10 in my dateset without labels, removing those seems to have rectified the issue.
Part 1 - Data Preparation
In the step to export training data with arcpy using the Image Analyst extension.
The output directory is listed as
\Documents\PCNN\Only_nDSM
And the
class_value_field="None"
.When using the export training data geoprocessing tool in arcgis pro (v2.5.2) having no class value selected returns.
When selecting a class value for an integer representing the unique ROOFFORMS the tool exports the training data as expected with labels nested into their own unique folders in the labels directory.
Part 2 - Model Training
The path specified is not the same root path used to export the training data listed above. The new path is
Documents\PCNN\Only_nDSM\Data_AOI2
indicating that it is one folder deeper than the original output.When trying to pass the original root folder to the
prepare_data
function it returns.I brought the exported TIFF tiles into Pro and they appear valid single band rasters as used in the example still showing elevation as expected and still spatially correct. Same with the label masks they are in the correct spatially, appropriate cell size and binary (class_value and 0) rasters.
This environment is using arcgis v1.8.1 with all necessary deep learning modules and can train on Unet and PSPnet successfully. If there is some data manipulation that is needed in between the export and prepare_data function or specific parameter flags needed; that being outlined better would be fantastic.
It would also be very helpful if when new versions of the ArcGIS Python API drop to include full conda env requirements exported from the dev/test env's used.
conda env export > env.yml
orconda list -e > requirements.txt
Either of those methods would ensure that all packages needed could be acquired at their specific version to not cause breaking changes. Things like the latest libtiff version being used versus 4.0.10 would be easier to troubleshoot etc.
Platform (please complete the following information):