DSpace/Manakin Repository

Brazilian soil data for taxonomic classification.

Mostrar registro simples

dc.contributor.author Vaz, Glauber José
dc.contributor.author Silva Junior, Adalberto Francisco da
dc.contributor.author Silva Neto, Luis de França da
dc.coverage.spatial Pernambuco, Brazil, Rio Grande do Norte, Brazi
dc.date 2023-10-20
dc.date.accessioned 2023-09-19
dc.date.accessioned 2023-10-22T01:11:57Z
dc.date.available 2023-10-22T01:11:57Z
dc.identifier.uri https://doi.org/10.48432/PYKKA7
dc.identifier.uri https://www.redape.dados.embrapa.br/dataset.xhtml?amp;persistentId=doi:10.48432/PYKKA7
dc.description This dataset was designed to support the sharing of soil profile data in an interoperable file format and to facilitate the classification of soil profiles according to the Brazilian Soil Classification System (BSCS), the official taxonomic system in Brazil. However, it can also be used for various other applications. It is based on soil sheets generated by numerous soil scientists involved in the GeoTab Project, which aimed to organize soil data from the Brazilian coastal tablelands and update the classifications of the profiles. For each soil profile, there are two or three files. The original soil profile sheet and the corresponding JSON file with the soil profile data in a structured and interoperable format are provided. If the curated soil profile is updated from the original one, it is also provided.
dc.description Essa base de dados foi criada para apoiar o compartilhamento de dados de solos em um formato de arquivo interoperável e para facilitar a classificação de perfis de solo de acordo com o Sistema Brasileiro de Classificação de Solos (SiBCS), sistema taxonômico oficial no Brasil. Porém, a base de dados também pode ser usada para várias outras aplicações. Ela é baseada em fichas de solos geradas por inúmeros cientistas de solo envolvidos no projeto GeoTab, que visou à organização de dados de solos nos tabuleiros costeiros do Brasil e à atualização da classificação desses perfis. Para cada pefil de solo, há dois ou três arquivos. São fornecidos a ficha de perfil de solo original e o arquivo JSON correspondente com os dados do perfil de solo em um formato interoperável e estruturado. Se o perfil de solo curado tem alterações em relação ao original, um novo arquivo é fornecido.
dc.description.sponsorship Embrapa
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/json
dc.format application/rtf
dc.format application/rtf
dc.format application/json
dc.format text/markdown
dc.format text/markdown
dc.language Portuguese
dc.publisher Vaz, Glauber José
dc.subject Computer and Information Science
dc.subject Earth and Environmental Sciences
dc.title Brazilian soil data for taxonomic classification.
dc.type machine-readable-text
dc.type research data
dc.type texto legível por máquina
dc.type dados de pesquisa
dc.description.sponsorshipId 23.14.01.017.00.00


Arquivos deste item

Arquivos Tamanho Formato Visualização

Não existem arquivos associados a este item.

Este item aparece na(s) seguinte(s) coleção(s)

Mostrar registro simples