Brazilian Dams And Brumadinho Households
Database useful to analyze the tragic brazilian accident at Brumadinho
@kaggle.edumagalhaes_brazilian_dams_and_brumadinho_households
Database useful to analyze the tragic brazilian accident at Brumadinho
@kaggle.edumagalhaes_brazilian_dams_and_brumadinho_households
This data set relates to every Brazilian dam that holds some type of ore.
After Brumadinho's dam disruption on January 25 of 2019, I came up with the idea to help Brazilians to have a better and more clear view about the risks that we face when we live close to some dam like Brumadinho.
This database is an open data provided by Brazilian organs like ANM (National Agency of Mining) and IBGE (Brazilian Institute of Geography and Statistics).
ANM database has all the latest dams location, latitude, longitude, risk of disruption and risk of damage.
IBGE database has some households locations from the 2017 Brazilian census, which can be used to check how close a household is to a dam.
This database was cleaned and prepared previously with some of my colleagues at Cappra Data Science community. and at the DataScience4Industry community.
Would you like to contribute with a data4good analysis in this data set and help Brazilians to understand what risks can be around them and save lifes? I hope so... so join us in this good cause journey!
CREATE TABLE belohorizonte_meteorological_daliydata_from_2015until2_ab2a1d77 (
"weather_station" BIGINT,
"date" VARCHAR,
"hour" VARCHAR,
"preciptation" DOUBLE,
"max_temperature" DOUBLE,
"min_temperature" DOUBLE,
"insolacao" DOUBLE,
"evaporation" DOUBLE,
"average_temperature" DOUBLE,
"average_relative_humidity" DOUBLE,
"average_wind_speed" DOUBLE
);CREATE TABLE belohorizonte_meteorological_data_from_2015until2019 (
"weather_station" BIGINT,
"date" VARCHAR,
"hour" VARCHAR,
"dry_bulb_temperature" DOUBLE,
"wet_bulb_temperature" DOUBLE,
"relative_humidity" DOUBLE,
"atmospheric_pressure_inthe_station" DOUBLE,
"wind_direction" DOUBLE,
"wind_speed" DOUBLE,
"cloudiness" DOUBLE
);CREATE TABLE database_versao_latlongdecimal_fonteanm_23_01_2019 (
"nome_barragem_mineracao" VARCHAR,
"nome_do_empreendedor" VARCHAR,
"cpf_cnpj" VARCHAR,
"posicionamento" VARCHAR,
"uf" VARCHAR,
"municipio" VARCHAR,
"minerio_principal" VARCHAR,
"altura_atual_metros" VARCHAR,
"volume_atual_m3" VARCHAR,
"categoria_de_risco" VARCHAR,
"dano_potencial_associado" VARCHAR,
"classe" VARCHAR,
"inserida_na_pnsb" VARCHAR,
"latitude" DOUBLE,
"longitude" DOUBLE
);CREATE TABLE ibge_3109006_censo2017_brumadinho_domicilios (
"cod_uf" BIGINT,
"cod_municipio" BIGINT,
"cod_distrito" BIGINT,
"cod_subdistrito" BIGINT,
"situacao" BIGINT,
"nom_tipo_seglogr" VARCHAR,
"nom_titulo_seglogr" VARCHAR,
"nom_seglogr" VARCHAR,
"num_endereco" DOUBLE,
"dsc_modificador" VARCHAR,
"nom_comp_elem1" VARCHAR,
"val_comp_elem1" VARCHAR,
"nom_comp_elem2" VARCHAR,
"val_comp_elem2" VARCHAR,
"nom_comp_elem3" VARCHAR,
"val_comp_elem3" VARCHAR,
"nom_comp_elem4" VARCHAR,
"val_comp_elem4" VARCHAR,
"nom_comp_elem5" VARCHAR,
"val_comp_elem5" VARCHAR,
"latitude" DOUBLE,
"longitude" DOUBLE,
"altitude" DOUBLE,
"dsc_localidade" VARCHAR,
"cod_especie" BIGINT,
"cep" BIGINT
);CREATE TABLE ibge_3140159_censo2017_mariocampos_domicilios (
"cod_uf" BIGINT,
"cod_municipio" BIGINT,
"cod_distrito" BIGINT,
"cod_subdistrito" BIGINT,
"situacao" BIGINT,
"nom_tipo_seglogr" VARCHAR,
"nom_titulo_seglogr" VARCHAR,
"nom_seglogr" VARCHAR,
"num_endereco" DOUBLE,
"dsc_modificador" VARCHAR,
"nom_comp_elem1" VARCHAR,
"val_comp_elem1" VARCHAR,
"nom_comp_elem2" VARCHAR,
"val_comp_elem2" VARCHAR,
"nom_comp_elem3" VARCHAR,
"val_comp_elem3" VARCHAR,
"nom_comp_elem4" VARCHAR,
"val_comp_elem4" VARCHAR,
"nom_comp_elem5" VARCHAR,
"val_comp_elem5" VARCHAR,
"latitude" DOUBLE,
"longitude" DOUBLE,
"altitude" DOUBLE,
"dsc_localidade" VARCHAR,
"cod_especie" BIGINT,
"cep" BIGINT
);CREATE TABLE ibge_3152006_censo2017_pompeu_domicilios (
"cod_uf" BIGINT,
"cod_municipio" BIGINT,
"cod_distrito" BIGINT,
"cod_subdistrito" BIGINT,
"situacao" BIGINT,
"nom_tipo_seglogr" VARCHAR,
"nom_titulo_seglogr" VARCHAR,
"nom_seglogr" VARCHAR,
"num_endereco" DOUBLE,
"dsc_modificador" VARCHAR,
"nom_comp_elem1" VARCHAR,
"val_comp_elem1" VARCHAR,
"nom_comp_elem2" VARCHAR,
"val_comp_elem2" VARCHAR,
"nom_comp_elem3" VARCHAR,
"val_comp_elem3" VARCHAR,
"nom_comp_elem4" VARCHAR,
"val_comp_elem4" VARCHAR,
"nom_comp_elem5" VARCHAR,
"val_comp_elem5" VARCHAR,
"latitude" DOUBLE,
"longitude" DOUBLE,
"altitude" DOUBLE,
"dsc_localidade" VARCHAR,
"cod_especie" BIGINT,
"cep" BIGINT
);CREATE TABLE ibge_3162922_censo2017_sao_joaquimdasbicas_domicilios (
"cod_uf" BIGINT,
"cod_municipio" BIGINT,
"cod_distrito" BIGINT,
"cod_subdistrito" BIGINT,
"situacao" BIGINT,
"nom_tipo_seglogr" VARCHAR,
"nom_titulo_seglogr" VARCHAR,
"nom_seglogr" VARCHAR,
"num_endereco" DOUBLE,
"dsc_modificador" VARCHAR,
"nom_comp_elem1" VARCHAR,
"val_comp_elem1" VARCHAR,
"nom_comp_elem2" VARCHAR,
"val_comp_elem2" VARCHAR,
"nom_comp_elem3" VARCHAR,
"val_comp_elem3" VARCHAR,
"nom_comp_elem4" VARCHAR,
"val_comp_elem4" VARCHAR,
"nom_comp_elem5" VARCHAR,
"val_comp_elem5" VARCHAR,
"latitude" DOUBLE,
"longitude" DOUBLE,
"altitude" DOUBLE,
"dsc_localidade" VARCHAR,
"cod_especie" BIGINT,
"cep" BIGINT
);Anyone who has the link will be able to view this.