normalize_address() confused by whitespace

[mikepease]

If there is a tab or newline at the beginning or end of an address string, normalize_address() incorrectly parses the address components.

select * from normalize_address('212 n 3rd ave, Minneapolis, mn 55401 ')

select * from normalize_address(' 212 n 3rd ave, Minneapolis, mn 55401')

Can your function start off by cleaning up whitespace on the input string? When I don't make sure to send input clean of whitespace, I get poor results.

Something like... trim(regexp_replace(' 212 n 3rd ave, Minneapolis, mn 55401', '\r|\n', ' ', 'g'))

e.g. select normalize_address(trim(raw_address))

[robe]

This works okay with pagc_normalize

Except instead of 3rd, it returns: 3

Debating if that is okay or not. I'll have to see how geocoder handles it. I don't think it will care.

e.g.

select (a).address, a.predirabbrev, a.streetname from pagc_normalize_address(' 212 n 3rd ave, Minneapolis, mn 55401') As a ;

Yields:

 address | predirabbrev | streetname
---------+--------------+------------
     212 | N            | 3