Peter Johnson
Peter Johnson
Heya, I noticed today that the `geom:bbox` calculations for geometries crossing the antimeridian are incorrect. Eg. [Fiji](https://raw.githubusercontent.com/whosonfirst-data/whosonfirst-data-admin-fj/master/data/856/327/55/85632755.geojson) -> `"geom:bbox": "-180.0,-21.738659,180.0,-12.457111"` The [properties spec](https://github.com/whosonfirst/whosonfirst-properties/tree/main/properties/geom#bbox) says the format is `"minx, miny, maxx,...
heya, I was looking at the record for [Berlin](https://raw.githubusercontent.com/whosonfirst-data/whosonfirst-data-admin-de/master/data/101/909/779/101909779.geojson) today and noticed that the `wof:concordances` structure is missing some of the foreign keys found elsewhere in the file. I think...
_Note: Work in original comment was taken care of in #799. This issue should track issue outlined in second comment (below). - stepps00, 06/13/2017._ heya, I found some unusual looking...
Heya, We noticed that London Districts (wof:neighbourhood) don't have population estimates. eg. [Putney](https://spelunker.whosonfirst.org/id/85789965/), [Clapham](https://spelunker.whosonfirst.org/id/85861663/) Looking up one level in the hierarchy at London Boroughs (wof:borough) they also don't have population...
I noticed this issue today where [1175615707](https://raw.githubusercontent.com/whosonfirst-data/whosonfirst-data-admin-za/master/data/117/561/570/7/1175615707.geojson) (`"wof:placetype": "locality"`) has `"locality_id": 101928453` in the hierarchy. I was expecting the `locality_id` to be `1175615707` (equal to the ID of the feature)...
It seems that `libpostal` gets confused with airports, returning the label `suburb`: ```bash curl --get http://localhost:4400/parse \ --data-urlencode 'address=john f kennedy international airport' [{"label":"suburb","value":"john f kennedy international airport"}] ``` However...
this PR is an experiment with splitting up the `name.*` fields in order to avoid the negative effects of field norms due to field length, reported in https://github.com/pelias/openstreetmap/issues/507 and better...
I'm curious as to what effect changing the `popularity:weight` for autocomplete from `1->2` would have for: - https://pelias.github.io/compare/#/v1/autocomplete?text=statue+of+liberty - https://pelias.github.io/compare/#/v1/autocomplete?text=statue+of+liberty+nyc seems it's been 7 years since we last touched this...
as mentioned in https://github.com/pelias/openaddresses/pull/504 the current deduplication behaviour considers all units at the same address to be duplicate, therefore 'squashing them' into a single response. this PR modifies this behaviour...