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
Atm., metadata files are parsed via ArcGraphModel.IOs parsing functions. Yet, we use those that return ICvBase lists consisting of CvParams and CvParams that are already aggregated into CvContainers.
These aggregations hinder flat CvParam evaluation and overcomplicate the information extraction much more than necessary. Therefore, it may be best to use shortly implemented parsing functions that only return mere CvParams.
The text was updated successfully, but these errors were encountered:
This is now possible due to developments in ARCTokenization, but since this requires a huge re-write of the core API, i move this to the 2.0.0 milestone. This should be implemented on the v2 branch.
Atm., metadata files are parsed via ArcGraphModel.IOs parsing functions. Yet, we use those that return ICvBase lists consisting of CvParams and CvParams that are already aggregated into CvContainers.
These aggregations hinder flat CvParam evaluation and overcomplicate the information extraction much more than necessary. Therefore, it may be best to use shortly implemented parsing functions that only return mere CvParams.
The text was updated successfully, but these errors were encountered: