Timeline for Address entry as a single textarea [duplicate]
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2014 at 10:48 | history | closed |
Matt Obee JonW♦ |
Duplicate of Combining all the address fields into one? | |
| S Nov 5, 2014 at 8:56 | history | suggested | Crissov |
add address tag
|
|
| Nov 5, 2014 at 8:22 | review | Close votes | |||
| Nov 5, 2014 at 10:48 | |||||
| Nov 5, 2014 at 8:05 | review | Suggested edits | |||
| S Nov 5, 2014 at 8:56 | |||||
| Nov 5, 2014 at 7:15 | comment | added | phresnel | @Crissov: When I search for "address parsing algorithm patent", I find a number of patent applications and papers. A lot of what might be in use may also not be known as specificall "address parsing", but be matters of AI; evolutionary algorithms and neuronal nets are two things I imagine. These are also in use in written language recognititon in general. I think regarding address parsing, that address correction is the smaller problem, compared to handwriting detection. They could just compare what they parsed against huge datasets. And if a letter is not automatically decipherable -> humans. | |
| Nov 4, 2014 at 23:50 | comment | added | MonkeyZeus | @Crissov There are many things that people with higher power simply don't want to grant access to. You gotta know somebody to get the good stuff. | |
| Nov 4, 2014 at 22:10 | comment | added | Crissov | @MonkeyZeus But do they? I’m not aware of any address parser being sold by a postal or parcel delivery service, but I haven’t looked intensely either. | |
| Nov 4, 2014 at 21:30 | answer | added | AKS | timeline score: 7 | |
| Nov 4, 2014 at 20:40 | comment | added | MonkeyZeus | @Crissov Knowledge is powerful, and valuable. The shipping companies would simply say "Pay up" | |
| Nov 4, 2014 at 20:09 | comment | added | Crissov | @phresnel One wonders why such experience would not have resulted in reliable algorithms for address parsing being made available to the public, implemented in standard libraries. | |
| Nov 4, 2014 at 17:58 | answer | added | R.. GitHub STOP HELPING ICE | timeline score: 4 | |
| Nov 4, 2014 at 16:22 | comment | added | phresnel | Believe it or not, but after selling a big part of private ballast on a popular selling platform, I came to realise that a lot of ppl are not even capable of writing their address correctly. Some write their name all-uppercase, just to write the remainder of the address all lower-case. Some flip the order of City and Street, some skip the Postal Code. And allmost noone gets their hyphens correctly. That being said: You can trust your shipping companies to account for user errors correctly, because they often have decades of experience on this. | |
| Nov 4, 2014 at 15:39 | vote | accept | Steve Claridge | ||
| Nov 4, 2014 at 14:40 | history | tweeted | twitter.com/#!/StackUX/status/529644246735679488 | ||
| Nov 4, 2014 at 14:27 | answer | added | peterchen | timeline score: 17 | |
| Nov 4, 2014 at 14:07 | answer | added | Brian Muenzenmeyer | timeline score: 3 | |
| Nov 4, 2014 at 13:46 | comment | added | Steve Claridge | Thanks Jon, I have no such restrictions on the server-side, in fact, if I did make it separate fields then I'd end up joining them into one field in the DB anyway. | |
| Nov 4, 2014 at 13:44 | comment | added | JonW♦ | A lot of them are the way they are because of back-end restictions - they need to parse the correct elements of the addresses into the correct fields in the database. As a result that does impact the UX side of things. | |
| Nov 4, 2014 at 13:38 | history | asked | Steve Claridge | CC BY-SA 3.0 |