Remove additionalProperty, nested within schema:spatialCoverage, from the list of unmappable properties for the EML strategy. We have defined unmappable properties as top-level properties that cannot be meaningfully mapped to the target metadata standard. In this case, the nested property doesn't meet this criteria.
The initial rationale behind allowing users to define nested properties as arguments to the main.convert method was to simplify this process. After some experience, it became evident that many nested properties meet this criteria within the EML metadata standard. Scaling this out to other metadata standards would create an overly complicated code base and likely more confusion than it's worth.
Remove
additionalProperty, nested withinschema:spatialCoverage, from the list of unmappable properties for the EML strategy. We have defined unmappable properties as top-level properties that cannot be meaningfully mapped to the target metadata standard. In this case, the nested property doesn't meet this criteria.The initial rationale behind allowing users to define nested properties as arguments to the
main.convertmethod was to simplify this process. After some experience, it became evident that many nested properties meet this criteria within the EML metadata standard. Scaling this out to other metadata standards would create an overly complicated code base and likely more confusion than it's worth.