Re:Usaddress – Python library for parsing unstructured addre...
by cfqycwz on Friday October 03, 2014 @09:33PM
(#8408487)
It is incredibly disappointing to me that this seemingly brand-new library is Python-2-only. Why are new libraries being written for a legacy version of the language?
Re:Usaddress – Python library for parsing unstructured addre...
by meowface on Saturday October 04, 2014 @02:50PM
(#8410196)
I'm a Python developer and I still only write in Python 2. I'll sometimes release projects and make them compatible with both Python 2 and 3, but for any personal or professional (non-open source) work I use Python 2.
Python 2 still has too much pull. Lots of smaller open source projects and third party libraries use 2, as do little snippets and examples all around the Internet. I've never found a case where a project I wanted to use, modify, or borrow from supported 3 but not 2, but the inverse is unfortunately still quite common.
I think Python 3 is a better language over all, but it's easier for me as a developer to keep using what I know will be supported and compatible.
Re:Usaddress – Python library for parsing unstructured addre...
by spaznode on Friday October 03, 2014 @06:29PM
(#8407994)
This is fucking awesome woooh!
(Not sarcasm, I guess I'll find out next week what getting crfsuite setup and adding training data is like. I hope not traumatizing but either way I have very good reasons to invest tons of time into project for job where we parse every craz-ily formatted address in U.S. postal region..like all the time re-parse over and over and over..all work and no play makes jack a dull boy)
Re:Usaddress – Python library for parsing unstructured addre...
by sytelus on Friday October 03, 2014 @09:21PM
(#8408462)
Not impressed at this stage. My rule based simple parser works actually better. I've filed some examples I expected to work with such a heavyweight approach as issue in repo:
Re:Usaddress – Python library for parsing unstructured addre...
by rdegges on Friday October 03, 2014 @08:52PM
(#8408410)
This looks great! One thing that I find a tad bit annoying, however, is that the output is a list of tuples -- would be nice to get a dictionary returned instead. I think that makes more intuitive sense, eg:
Re:Usaddress – Python library for parsing unstructured addre...
by cfqycwz on Friday October 03, 2014 @09:30PM
(#8408484)
I imagine a list of tuples is used to preserve the order of the street address--I agree it would probably make much more sense to use an OrderedDict instead.
Re:Usaddress – Python library for parsing unstructured addre...
by Semiapies on Friday October 03, 2014 @04:21PM
(#8407440)
It's a fantastic idea (and a hard problem to boldly tackle), though still very early in implementation. I filed an issue on mis-parsing of addresses without street type identifiers (St/Dr/Av/Ln/etc.)
Re:Usaddress – Python library for parsing unstructured addre...
by acbart on Friday October 03, 2014 @04:11PM
(#8407396)
It'd be nice to see some more examples that show how sophisticated it is. What are some weird inputs that it can figure out? Still, this is a pretty awesome idea - definitely can see how it'll be useful for me.
Re:Usaddress – Python library for parsing unstructured addre...
by Semiapies on Monday October 06, 2014 @02:02PM
(#8417194)
So far? Omit a "St." or "Ave. in an address, in a form I see all the time ("123 Main Somewhere NY, 10101") and it gets thoroughly confused. The author(s) are uninterested in fixing this, too - I don't think they care about "weird inputs" at all.
Python 2 still has too much pull. Lots of smaller open source projects and third party libraries use 2, as do little snippets and examples all around the Internet. I've never found a case where a project I wanted to use, modify, or borrow from supported 3 but not 2, but the inverse is unfortunately still quite common.
I think Python 3 is a better language over all, but it's easier for me as a developer to keep using what I know will be supported and compatible.
https://github.com/datamade/us-address-parser/issues/50
{"number": "121", "street": "Blah Street", ...}
Or some way to train a process that will be able to predict what category an entity falls into.