A fork for the time-zone database?
A fork for the time-zone database?
Posted Oct 11, 2021 14:37 UTC (Mon) by smurf (subscriber, #17840)In reply to: A fork for the time-zone database? by farnz
Parent article: A fork for the time-zone database?
I truly don't get why y'all are going to such lengths. Offer a "how do you want to be addressed" field, a "which country / administration do you live in" (that wording should cover Taiwan, Palestine, or Transnistria) menu, and a "what should be on the address label of a package to you" multi-line field. All of which gotta be Unicode capable and not filter out random characters (no, Bobby Tables must not be prevented from causing havoc by filtering user input, thank you very much).
Then you can lean back in comfort and watch everybody else struggle with this nonsense.
Posted Oct 11, 2021 16:45 UTC (Mon)
by mpr22 (subscriber, #60784)
[Link]
aaaaa
don't talk to me about address formats
I deal with a pair of systems (and their constellation of client websites) that separate "house number or name" from "street", require both fields to be populated, and always present them HNON first
which is a piece of gibbering anglocentric stupidity (and doesn't even work everywhere in england)
but I'm not allowed to set it on fire
Posted Oct 11, 2021 23:09 UTC (Mon)
by sammythesnake (guest, #17693)
[Link] (10 responses)
I deliver for Amazon and every day I have to deliver to addresses that are missing the house number, or the street name, or it's there but spelled incorrectly, or doesn't exist, or have a postcode in a different city from the rest of the address...
All addresses should be either from the database in a canonical form, or behind a scary warning that if you change your address from that canonical form, your package may-or-may-not ever arrive.
Of course, once I get there, I'll still have to handle houses without the number/name anywhere to be seen with numbering orders that must be the product of a stroke* and so on, but let's at least let's solve this one problem that we so easily could, eh?
* Example from today. 10, 9, 3, 4, 7, 8, 5, 6. No house 1 or 2. I swear they get together to drink absinthe and dream up new ways to make no sense...
Posted Oct 12, 2021 0:22 UTC (Tue)
by mpr22 (subscriber, #60784)
[Link]
https://en.wikipedia.org/wiki/Address
The only internationally portable way to represent addresses, if you don't have the budget to throw piles of money at a company whose primary revenue stream is extracting capitalist rent from control of access to an address database, is as a series of freeform lines written in either Latin letters or the addressee's native script.
It should be noted that even the craziest house numberings usually have some kind of logic, though you may have to analyse its development diachronically rather than synchronically for it to become apparent.
Posted Oct 12, 2021 9:13 UTC (Tue)
by farnz (subscriber, #17727)
[Link] (3 responses)
Context is everything. If you're getting an address to hand over to a delivery agent, the address should come from a mapping database shared with the agent, so that what you get when you have an Amazon parcel to drop off is in a form usable to you - and that can mean that the address you have for me is a shipping point, not my home (e.g. a PO Box). If you're getting an address to share with the government for tax reasons, it should be in a form that the government is happy with.
And as the delivery company, or the government, you keep a database (either in-house, or bought in from a mapping provider) that contains all the addresses you want in a form that you're happy with. That way, you get a decent location for your parcel deliveries; downside is that your company has to maintain that database so that everyone's address is in it.
Free form addresses are fine if you're gathering something that the user will want to simply share with friends.
Posted Oct 12, 2021 11:51 UTC (Tue)
by nye (subscriber, #51576)
[Link] (2 responses)
That doesn't work in practice though, because the delivery is not done by some nebulous "company", but by a delivery person who has to drive a van around looking for the address on the package. The company hasn't individually looked over each address and checked that it's in the most accessible form; that would be impossible. A person knows their address; "normalising" it to something that conforms to a database created by a machine doesn't magically improve things by virtue of having it in some "consistent" format, because real addresses fundamentally aren't consistent.
My address technically looks like this:
Unfortunately "Some Street" isn't accessible by car so isn't on every satnav database, which frequently can't understand that concept. The street that it branches off is on all of those databases though, so after living here a while, we worked out that delivery drivers had a much higher success rate if we render our address as:
Systems which try to normalise this end up making the result categorically worse for us and for the people trying to deliver to us.
(Shout out to Kickstarter which requires me to double-confirm my address for every project I back, including having to pick a radio box to say that yes I really do want to use the address you made me re-enter again, and not your oddly mangled version that you describe as "more precise" but has two of the lines merged for no reason. Fuck you.)
Posted Oct 12, 2021 12:22 UTC (Tue)
by farnz (subscriber, #17727)
[Link] (1 responses)
Which is a failure of the database that's on offer - and really should be in delivery notes, not part of the address. So your address as stored in Amazon's systems should be "1 Some Street, Town, County, Postcode", with a note for the driver saying "Some Street is not accessible by car - go to 2 The Other Street, and then you can walk it".
The delivery notes, of course, are free-form.
Ideally, there would be routes to feed back the issue to the database owner, so that when you pick "1 Some Street" for your Amazon package, the resulting label and bar codes direct their in-van satnav to "2 The Other Street" and tell them to walk the rest of the way.
And Kickstarter have no excuse - when you first add your address to your account, they can ask you if you made a mistake, but after that they should be using the address on file as-is, not insisting on reconfirmation. While they may well be right that you're getting the address "wrong" (if it's a UK address, the correct form loses County nowadays, so it would be "1 Some Street, Town, Postcode"), they should only be asking you to correct it if it's actually causing problems.
Posted Oct 12, 2021 18:52 UTC (Tue)
by Wol (subscriber, #4433)
[Link]
Cheers,
Posted Oct 12, 2021 13:16 UTC (Tue)
by jezuch (subscriber, #52988)
[Link] (2 responses)
Posted Oct 12, 2021 14:01 UTC (Tue)
by excors (subscriber, #95769)
[Link]
Posted Oct 12, 2021 14:19 UTC (Tue)
by smurf (subscriber, #17840)
[Link]
Google's plus code isn't that much better.
The only location-encoding system that makes some kind of practical sense IMHO is Uber's H3. It just needs a reasonably pronounceable overlay.
Posted Oct 12, 2021 17:56 UTC (Tue)
by Wol (subscriber, #4433)
[Link]
Trouble is, the database isn't in a canonical form ... and all too often they assume that all you NEED is the postcode and the house number. So it's quite normal to have number, street, and the post town 20 miles away ... together with the post code that does uniquely identify the property you want - but it would be nice if the address actually included the town/village where said property was located ...
(Speaking as another guy who has spent the last god knows how many years driving a delivery van ...)
Cheers,
Posted Oct 23, 2021 14:38 UTC (Sat)
by nix (subscriber, #2304)
[Link]
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
1 Some Street
Town
County
Postcode
1 Some Street
The Other Street
Town
County
Postcode
A fork for the time-zone database?
A fork for the time-zone database?
Wol
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
A fork for the time-zone database?
Wol
A fork for the time-zone database?