readme and methods adjustment

[denarch22]

🛠️ Changes

The README file is adjusted, the code is adjusted to remove the raster and an adjustment is made to validate the response when uploading the items since the error was not evident.

📝 Associated issues

Ajuste en cargue y propiedades de las colecciones

[cazapatamar]

I uploaded a full collection with 4 items for loss and persistence (name: CAZMTest-15102024).

• The collection info in the STAC is correct.
• The TIFFs are converted to COG, uploaded to Azure, and attached to items as assets.

The only issue I found is that the properties (colors, classes, values) were not correctly created for each item. The collection you previously uploaded, @denarch22, LossPersistence, does have these properties. Is it necessary to make any changes to the collection.json file when uploading the collection?

In addition, the functions to validate and remove a collection are OK.

[erikasv]

Also remove the '>' I'm the changes description (it's explicitly said in the PR template

And change the associated issue link for the GitHub link (the goal of this link is to allow people outside zenhub to see how an issue was resolved)

[denarch22]

Subí una colección completa con 4 elementos para pérdida y persistencia (nombre: CAZMTest-15102024).

• La información de la colección en el STAC es correcta.
• Los TIFF se convierten en COG, se cargan en Azure y se adjuntan a los elementos como recursos.

El único problema que encontré es que las propiedades (colores, clases, valores) no se crearon correctamente para cada elemento. La colección que cargó anteriormente, , LossPersistence, tiene estas propiedades. ¿Es necesario realizar algún cambio en el archivo collection.json al cargar la colección?

Además, las funciones para validar y eliminar una colección son correctas.

yes camilo apart from the one in collection which is mandatory, it is necessary to add it to the items, like this:

[erikasv]

si camilo aparte del que esta en collection que es obligatorio, es necesario agregarlo en los items, asi:

@denarch22 the purpose of the collection spec is to simplify things for other researchers, so we need to keep the properties at the collection level, but internally those properties will be associated to each item, if each item has any other property it will be added to that specific item (or replace the one inherited from the collection). Also none of them are required in the spec.

Please add these clarifications in the spec.md file (that the properties in the collection level metadata will be associated to each item in the stac collection and that if the same property is set in the collection and in the item, the item will overwrite the collection one ). Keep this file in spanish

[cazapatamar]

Also, please add metadata.properties.colors to the specification of the collection in collection.md

[denarch22]

According to the last meeting, I made the adjustment so that the properties would remain within the collection with the extra fields option.

[cazapatamar]

Also, please add metadata.properties.colors to the specification of the collection in collection.md

Update: According to our last meeting, we realized it is not necessary to change collection.md

Erika is not available to re-review, but we all agreed on the last changes during the noon meeting

[ManuelStardust]

After testing everything works fine.