Rural Route not parsed correctly
See original GitHub issueThe address H E BROWN RR 3 BOX 9 CANTON OH 44730-9521
(grabbed from pp 51 of http://pe.usps.com/cpim/ftp/pubs/Pub28/pub28.pdf) doesn’t parse correctly
Address part | Tag |
---|---|
H | AddressNumber |
E | StreetNamePreDirectional |
BROWN | StreetName |
RR | StreetNamePostType |
3 | OccupancyIdentifier |
BOX | USPSBoxType |
9 | USPSBoxID |
CANTON | PlaceName |
OH | StateName |
44730-9521 | ZipCode |
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
USPS Headquarters delays rural route adjustments until after ...
As of today, we have successfully mapped over 97% of our rural routes in the ... No other routes are authorized to be...
Read more >Driving the Rural Delivery Route
Hi I've been working six days a week for over three years and I am totally burned out. I became a regular carrier...
Read more >Why Is My Address Not Valid and How to Verify It? - PostGrid
As a result of address parsing, it becomes easier to fill or correct the relevant data that may not be possible by using...
Read more >Handbook PO-603 - Rural Carrier Duties and Responsibilities
If a USPS-owned/leased vehicle is assigned to the route, you may be requested, but not required, to furnish a vehicle during emergency ...
Read more >RCA needs help with evaluated time. - Postal Employees
I am confused and ticked off that not working that less than 30 minutes ... that lunches are not included in to the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in v0.5.8.
New behavior:
Get the latest release via pip:
Thanks for doing this @jeancochrane!