search

CartoDB / data-services

CARTO internal geocoder PostgreSQL extension
25 stars 11 forks source link

iso codes don't georeference consistently #214

Closed ztephm closed 8 years ago

ztephm commented 8 years ago

Hi @iriberri can you help with this or please re-assign? Thanks!

S/B 8621784

Context

Dataset contains column of ISO3 codes. When importing and syncing same codes, sometimes they georeference, sometimes they fail.

Process

  1. Create hourly sync-table with type & content-guessing box checked from this GDrive file
  2. Create hourly sync-table with type & content-guessing box checked from this GDrive file too

    Expected result

They should both be automatically georeferenced the same way, since they contain the same ISO codes.

Current result

Here's first one:

success_1to10

Here's second one:

fail_1to11

Anything we can do to make sure they always georeference properly?

iriberri commented 8 years ago

Even though the CartoDB internal geocoder lives here, this issue is related with data guessing. I moved it to https://github.com/CartoDB/cartodb/issues/7386, let's talk there!