Peter Johnson

import all potentially useful fields from CSV in to model

3

imports some fields which are present in the CSV file but are not currently available on the model. after I pushed this PR I realised that https://github.com/pelias/openaddresses/pull/320 covers some of...

port download code to use the batch endpoint

7

this ~~draft~~ PR updates the OA downloader to use the `batch.openaddresses.io` endpoint. a few things worth mentioning: - the API and downloads require an authentication token - each 'file' is...

following on from https://github.com/pelias/openaddresses/pull/502 and mentioned in https://github.com/pelias/openaddresses/pull/502#issuecomment-1031441643 there is some additional work we can do for records containing concatenated unit numbers: - remove the unit number from the `name.default`...

Portuguese/Spanish street name normalization

1

Following on from https://github.com/pelias/openaddresses/pull/477 we could probably tackle some Portuguese/Spanish street prefix/suffix contractions. Mentioned in https://github.com/pelias/parser/issues/155#issuecomment-973143976 the `pt/countrywide` source of OpenAddresses contains contractions such as this (`R GODINHO DE FARIA`):...

s3 download option only available for download_all

2

The `download_all` downloader supports the `s3://` protocol but `download_filtered` does not. We should have symmetry between the two download methods. ref: https://github.com/pelias/openaddresses/pull/475

DRAFT PR to demonstrate a solution for https://github.com/pelias/pelias/issues/642

repeated street name

1

I'm on mobile so this is a screenshot sorry. It looks like some OA data has repetition of the street name, which we might be able to fix on import?...

DRAFT WIP This PR makes use of https://github.com/pelias/schema/pull/364 to remove the duplication of data between the `address_parts` fields and the `name.default` field. Related: https://github.com/pelias/openstreetmap/pull/488

housenumber with a '#' prefix

2

``` "housenumber": "#2708", ``` ``` { "type": "Feature", "geometry": { "type": "Point", "coordinates": [ -73.716908, 45.513926 ] }, "properties": { "id": "ca/qc/montreal:330808", "gid": "openaddresses:address:ca/qc/montreal:330808", "layer": "address", "source": "openaddresses", "source_id": "ca/qc/montreal:330808",...

remove HSTS feature codes?

1

Would it be appropriate to remove all data with the `HSTS` feature code? ie. https://pelias.github.io/compare/#/v1/place?ids=geonames%3Avenue%3A7874625 ``` HSTS | historical site | a place of historical importance ``` - https://www.geonames.org/export/codes.html