This PR comes out of the label extension discussion which occurred on April 22, 2022. The initial suggestion coming out of that discussion was that we would make the properties for the label extension apply at the asset level instead of the item level. After thinking this through I'm not sure that's the best solution. The solution proposed here would instead change the label:type property to label:types and would accept an array of enums allowing both raster and vector labels to be present as assets within this one item. This would make the upgrade from older versions to this version a trivial process.
This PR also adds a mention of the classification extension which should be used to provide the mapping of raster pixel values to human-readable class names.
This PR comes out of the label extension discussion which occurred on April 22, 2022. The initial suggestion coming out of that discussion was that we would make the properties for the label extension apply at the asset level instead of the item level. After thinking this through I'm not sure that's the best solution. The solution proposed here would instead change the
label:typeproperty tolabel:typesand would accept an array of enums allowing both raster and vector labels to be present as assets within this one item. This would make the upgrade from older versions to this version a trivial process.This PR also adds a mention of the classification extension which should be used to provide the mapping of raster pixel values to human-readable class names.