One of the use cases for the ADAPT Standard will be a data consumer requesting one or more formats of the same data (data frequency, geometry format, etc.) from a data producer. In the case where either party wants to transfer multiple variations, should there be provision to attach multiple spatial data files to one Operation?
Without adding a lot of complexity to the Operation to account for this case, the spatial files would need to contain the same columns in the same order. I.e., the producer could vary geometries or data frequency, but not the data attributes.
This leads to the question of how the consumer would be able to programmatically discern which file is which and whether we should add enumerated representations for data frequency, geometry type, etc that we can add to an attribute that wraps the file path.
Before adding all this complexity, we should assess how common this use case will be.
Agreement in 4 Oct 2023 meeting that this will not be supported. Data consumers should request the format they want if multiple levels of precision are supported.
One of the use cases for the ADAPT Standard will be a data consumer requesting one or more formats of the same data (data frequency, geometry format, etc.) from a data producer. In the case where either party wants to transfer multiple variations, should there be provision to attach multiple spatial data files to one Operation?
Without adding a lot of complexity to the Operation to account for this case, the spatial files would need to contain the same columns in the same order. I.e., the producer could vary geometries or data frequency, but not the data attributes.
This leads to the question of how the consumer would be able to programmatically discern which file is which and whether we should add enumerated representations for data frequency, geometry type, etc that we can add to an attribute that wraps the file path.
Before adding all this complexity, we should assess how common this use case will be.