Skip to content

Commit a68f5bd

Browse files
committed
Prepare 2.0.1 release
1 parent 2e6b3a1 commit a68f5bd

3 files changed

Lines changed: 20 additions & 9 deletions

File tree

LICENSE.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
BSD 3-Clause License
22

3-
Copyright (c) 2018, Johannes Schriewer
3+
Copyright (c) 2018-2019, Johannes Schriewer
44
All rights reserved.
55

66
Redistribution and use in source and binary forms, with or without

README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,17 @@ See `README.md` in the [repository](https://github.com/dunkelstern/osmgeocoder)
3131
- Restored compatability with older PostgreSQL DB versions (9.5+ if you do no use openaddresses.io)
3232
- Switched to `pipenv`
3333

34+
### v2.0.1
35+
36+
- Fix missing import for structured forward geocoding
37+
- Fix Copy and Paste error in forward geocoding SQL
38+
39+
If you're coming from `2.0.0`, re-run the finalize step to update the SQL functions:
40+
41+
```bash
42+
$ pipenv run bin/finalize_geocoder.py --db postgresql://geocoder:password@localhost/osmgeocoder
43+
```
44+
3445
## TODO
3546

3647
- Return Attribution in API and in webservices

setup.py

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,22 +6,22 @@
66

77
setup(
88
name='osmgeocoder',
9-
version='2.0.0',
9+
version='2.0.1',
1010
description='OpenStreetMap and OpenAddresses.io based geocoder',
1111
long_description='''
12-
Python implementation for a OSM / Openaddresses.io Geocoder.
12+
Python implementation for a OSM / Openaddresses.io Geocoder.
1313
14-
This geocoder is implemented in PostgreSQL DB functions as much as possible, there is a simple API and an example flask app included.
14+
This geocoder is implemented in PostgreSQL DB functions as much as possible, there is a simple API and an example flask app included.
1515
16-
You will need PostgreSQL 9.5+ (or 11.0+ for Openaddresses.io) with PostGIS installed as well as some disk space and data-files from OpenStreetMap and (optionally) OpenAddresses.io.
16+
You will need PostgreSQL 9.5+ (or 11.0+ for Openaddresses.io) with PostGIS installed as well as some disk space and data-files from OpenStreetMap and (optionally) OpenAddresses.io.
1717
18-
Data import will be done via [Omniscale's imposm3](https://github.com/omniscale/imposm3) and a supplied python script to import the openaddresses.io data.
18+
Data import will be done via [Omniscale's imposm3](https://github.com/omniscale/imposm3) and a supplied python script to import the openaddresses.io data.
1919
20-
Optionally you can use the [libpostal machine learning address classifier](https://github.com/openvenues/libpostal) to parse addresses supplied as input to the forward geocoder.
20+
Optionally you can use the [libpostal machine learning address classifier](https://github.com/openvenues/libpostal) to parse addresses supplied as input to the forward geocoder.
2121
22-
For formatting the addresses from the reverse geocoder the `worldwide.yml` from [OpenCageData address-formatting repository](https://github.com/OpenCageData/address-formatting) is used to format the address according to customs in the country that is been encoded.
22+
For formatting the addresses from the reverse geocoder the `worldwide.yml` from [OpenCageData address-formatting repository](https://github.com/OpenCageData/address-formatting) is used to format the address according to customs in the country that is been encoded.
2323
24-
See `README.md` in the [repository](https://github.com/dunkelstern/osmgeocoder) for more information.
24+
See `README.md` in the [repository](https://github.com/dunkelstern/osmgeocoder) for more information.
2525
''',
2626
long_description_content_type='text/markdown',
2727
url='https://github.com/dunkelstern/osmgeocoder',

0 commit comments

Comments
 (0)