You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several implementations which all do slightly different things:
.copm_prep: applies to data returned by SDA
.formatParentMaterialString: applies to pedon objects
.formatcoParentMaterialString: applies to component objects
The strategies used by formatcoParentMaterialString and formatParentMaterialString are more or less the same, with the component version employing additional checks on the source data. Missing or inconsistent record IDs, sequence numbers, vertical order sequences, and "exists on" logic contribute to the complexity of the code.
There are likely some corner-cases not yet handled by these functions, see #83 for an example.
The .formatcoXXX() functions have been subsumed into `.formatXXX() for NASIS.
In this issue we are not going to address harmonizing the above parent material functions with the SDA function .copm_prep() that is used for SDA and SSURGO File Geodatabases.
A variety of new tools and derived values are available for geomorph and parent material in the NASIS and SDA derived results compared to when this issue was made in 2018. If there are any specific further needs, let's create a new issue.
There are several implementations which all do slightly different things:
.copm_prep
: applies to data returned by SDA.formatParentMaterialString
: applies to pedon objects.formatcoParentMaterialString
: applies to component objectsThe strategies used by
formatcoParentMaterialString
andformatParentMaterialString
are more or less the same, with the component version employing additional checks on the source data. Missing or inconsistent record IDs, sequence numbers, vertical order sequences, and "exists on" logic contribute to the complexity of the code.There are likely some corner-cases not yet handled by these functions, see #83 for an example.
Notes to myself for next time.
The text was updated successfully, but these errors were encountered: