Repository navigation
Python test - #109
Merged
Merged
Python test#109
Conversation
atualização para python
…dronizaao de endereco
…rias ou não pythonicas e exclusão dos arquivos .duckdb após finalização
camilagb
marked this pull request as ready for review
September 21, 2026 13:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Versão inicial do
geocodebrem Python, derivada de #100.Nessa versão, é utilizado o binding para python do
enderecobrpara padronizar os endereços, mantendo a compatibilidade exata com o pacote em R. Opolarsé utilizado para chamar as funções de padronização, por possuir paralelismo e consumir menos memória que opandas. A etapa de matching segue sendo feita noDuckDB.TO DOs
geocode_reverso()e dobusca_por_cep