Closed sevko closed 9 years ago
Will simultaneously migrate the importer to pelias-model
.
If we decide to expose a coarse reverse-geocoding endpoint in the Pelias API we'll need to import polygons, so I'm hesitant about implementing this until that's settled. Putting on hold for now.
this issue was resolved some time ago
With the introduction of the new admin-lookup, which builds administrative hierarchies without querying elasticsearch Quattro types (as the old
hierarchy-lookup
did), we don't need to import polygons themselves, and should import their centroids as POIs instead. This'll involve ripping out significant chunks of the code and will result in a slimmer and much faster importer.