analytics-ufcg / dataset-zonaseleitorais

GNU General Public License v3.0
1 stars 0 forks source link

Geolocalização #2

Open danielfireman opened 6 years ago

danielfireman commented 6 years ago

Atualmente a base contém o endereço e o CEP (lembrando que existem probleamas aqui #1 ). Seria bacana se a gente conseguisse complementar e colocar as coordenadas GeoJSON.

danielfireman commented 6 years ago

TL;DR; Vou migrar o código para usar geocode.xyz ao invés do Google Maps API.

Comecei a realizar a geolocalização e realizei um post no twitter. As respostas apontaram alguns problemas e também algumas sugestões, as quais vou resumir aqui:

Problema

(a) No Scraping. Customer will not extract, export, or scrape Google Maps Content for use outside the Services. For example, Customer will not:(i) pre-fetch, cache, index, or store Google Maps Content for more than 30 days; (ii) bulk download geocodes; or (iii) copy business names, addresses, or user reviews.

(b) No Creating Content From Google Maps Content. Customer will not create content based on Google Maps Content, including tracing, digitizing, or creating other datasets based on Google Maps Content.

Sugestões

I'm already using Google's geocoding API, why should I switch to the OpenCage geocoder? Better terms and lower cost. Our terms of use make the OpenCage geocoder a more useable and flexible proposition than proprietary geocoders. We don't restrict what you can and can't do with the geocodes you get back, we don't stop you using geocodes for commercial purposes, and we don't try to force you into displaying geocodes on a particular type of map. Finally, you can store the results you receive from us as long as you