Opened 11 years ago
Last modified 7 years ago
#2459 new enhancement
Speed up pagc_normalize_address
| Reported by: | robe | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | pagc_address_parser | Version: | master |
| Keywords: | Cc: |
Description
Currently the way that pagc_normalize_address wraps the standard_address function, using it is actually slower than the normalize_address, but of course produces superior results.
such as the below that normalize_address would otherwise screw up.
SELECT *
FROM geocode(pagc_normalize_address('1000 S. Fremont Ave.,
Bldg. A-11,
Alhambra, CA 91803'), 1)
This speed issue is already documented in http://postgis.net/docs/manual-dev/Pagc_Normalize_Address.html and work around for it.
It would be nice though to have both speed and elegance.
Change History (5)
comment:1 by , 10 years ago
| Priority: | medium → high |
|---|
comment:2 by , 10 years ago
| Priority: | high → medium |
|---|
comment:3 by , 9 years ago
| Milestone: | PostGIS 2.2.0 → PostGIS 2.3.0 |
|---|
comment:4 by , 8 years ago
| Milestone: | PostGIS 2.3.0 → PostGIS Future |
|---|
Note:
See TracTickets
for help on using tickets.
I probably won't get to this, but since its really a performance thing not new feature (I can hasz do after 6/30 right
)