Al 4d14f80f0c [osm] using the new gazetteer methods to do more thorough checks on single house names (if there are no other components than the standalone venue name, make sure it contains venue words like {library, bar}, etc. and not street type words like {road, street}, etc. so we don't get training examples that are simply "Abbey/house Road/house" with no house number or street name). If the venue name equals the street name or house number, drop it. Same if the venue name equals one of the admin components and no house number or street is present. If the venue name is numeric, require both a house number and a street name.

2016-11-19 03:12:24 -05:00

..

__init__.py

[fix] __init__.py

2015-06-15 17:54:27 -04:00

admin_boundaries.py

[osm] only add label props if the name property is identical (counterexample, Nottinghamshire's label is listed as West Bridgford, which is really its admin_center)

2016-10-16 22:18:52 -04:00

components.py

[osm] removing place=district mapping globally (means city_district in Hungary) and mapping it specifically to state_district/city_district in the places where it's needed

2016-10-18 19:02:36 -04:00

definitions.py

[osm] Adding OSM file for places stored as nodes. Adding a general venue definition accessible from the geodata Python package. OSM definitions expand simple variables so can reuse/combine definitions in the bash script

2016-07-21 17:04:57 -04:00

extract.py

[fix] import

2016-10-05 03:23:34 -04:00

fetch_osm_address_data.sh

[osm] add boundary=postal_district to admin borders for Ireland

2016-10-05 15:26:16 -04:00

formatter.py

[osm] using the new gazetteer methods to do more thorough checks on single house names (if there are no other components than the standalone venue name, make sure it contains venue words like {library, bar}, etc. and not street type words like {road, street}, etc. so we don't get training examples that are simply "Abbey/house Road/house" with no house number or street name). If the venue name equals the street name or house number, drop it. Same if the venue name equals one of the admin components and no house number or street is present. If the venue name is numeric, require both a house number and a street name.

2016-11-19 03:12:24 -05:00

intersections.py

[intersections] no need to store lat/lon in intersections

2016-08-19 01:58:53 -04:00

osm_address_training_data.py

[fix] bracket

2016-10-05 14:27:24 -04:00