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
When a data source already has a logical unique horizon identifier, the fetchX() functions should use it instead of the default of calculating one with 1:nrow(spc@horizons)
When a data source already has a logical unique horizon identifier, the fetchX() functions should use it instead of the default of calculating one with
1:nrow(spc@horizons)
fetchNASIS_pedons():
hzidname(spc) <- 'phiid'
fetchNASISLabData():
hzidname(spc) <- 'phiid'
fetchPedonPC():
hzidname(spc) <- 'phiid'
fetchRaCA()$pedons:
hzidname(spc) <- 'phiid'
fetchNASIS_components():
hzidname(spc) <- 'chiid'
fetchKSSL():
hzidname(spc) <- "labsampnum"
fetchRaCA()$samples:
hzidname(spc) <- 'sample_id'
fetchNASISWebReport:
hzidname(spc) <- 'chkey'
fetchSDA_component:
hzidname(spc) <- 'chkey'
Any objections? Any ones I missed? I am thinking this standard will be handy with implementation of horizon setter changes in aqp
The text was updated successfully, but these errors were encountered: