Al
|
58b84d6244
|
[fix] deriving whitespace and state in normalized_place_name, adding all candidate languages to arguments
|
2016-05-05 13:20:53 -04:00 |
|
Al
|
03c837526c
|
[fix] raw OSM reverse geocoded components vs. versus normalized version
|
2016-05-05 13:04:57 -04:00 |
|
Al
|
c4c1f9e17b
|
[fix] import
|
2016-05-05 12:54:15 -04:00 |
|
Al
|
f59ee4a136
|
[fix] check the first phrase for components and bail if it matches something other than the specified tag
|
2016-05-05 12:46:01 -04:00 |
|
Al
|
cf0dcd849c
|
[fix] import
|
2016-05-05 12:30:42 -04:00 |
|
Al
|
bc6a34a3b6
|
[addresses] more thoroughly solving the addr:city='Harlem' issue
|
2016-05-05 12:30:04 -04:00 |
|
Al
|
4f0a142153
|
[addresses] Adding normalized_place_name, a method for separating compound fields like addr:city='New York NY' into simply 'New York', solving the compound phrase problem. Also solves the mislabeled place name problem, causing the system to ignore the user tag and fall back on reverse geocoded components in cases e.g. where addr:city='Harlem', which is a known neighborhood but not a city when reverse geocoded. A few other refactors for expanded address components
|
2016-05-05 12:18:33 -04:00 |
|
Al
|
92ffa42937
|
[addresses] wrapping up some of the functionality from OSM formatter to be used in on an arbitrary address component dictionary
|
2016-04-28 23:47:23 -04:00 |
|