151–160 of 233 posts
Earlier quoted context omitted.
Thomas' is not grammatically correct in any version of English that I know. It's not plural. There is no special rule for that. Both the street signs you mentioned are at least grammatically coherent
When a word ends with an s, the use of an apostrophe without another s is valid English. Thomas’ and Thomas’s are the same thing.
As far as I can tell, this isn't an issue with the specific database itself, but the standard they are required to record geographic data in, which the end of the article mentions as "BS 7666". https://www.agi.org.uk/wp-content/uploads/2020/11/BS7666Guid... # Standard data types used in BS 7666 CharacterString: a sequence of alphanumeric characters ... If I had to guess, alphanumeric is interpreted as [0-9a-z]. The s…
> Abbreviations and punctuation shall not be used unless they appear in the designated name, e.g. “Dr Newton’s Way”, and only single spaces shall be used.
Given that "alphanumeric" is vague, not defined, and prominently contradicted, I'd say it's quite clear that they can't really blame it on BS 7666.
The council probably have some horrible CSV-infested GIS workflow, and have decided to change reality to avoid the bugs.
Earlier quoted context omitted.
dropping and duplicating data is exactly the symptom you get from not sanitising aprostrophies in your data correctly.
Not at all. If I understand correctly, the failure to synchronize was a fundamental flaw in the the networking code and had nothing to do with the payloads inside the networking code.
try to sql
(`type`:'express post',`from`:'st mary's street',`value`:'50')
and it will drop the value field, throw an error, and quite possibly duplicate several type and half filled froms depending on how the error handling is done.
This article is basically admitting its cheaper to change the street names than unfux their buggy software, so something is up. what are the other options that meet that criteria?
Earlier quoted context omitted.
>but this way, you're less likely to run into an issue where it takes you to Kings Landing in the wrong town because you didn't type King's Landing in the town you meant. That's pretty uncompelling. Should we also get rid of the letter s to avoid mix-ups between Kings Landing and King Landing?
Devils advocate: the apostrophe isn’t pronounced. The s is.
Earlier quoted context omitted.
BS in "BS 7666" stands for British Standard and not anything else. If the standard restricts street names to those certain characters, may be it really is BS .
The '666' portion doesn't inspire confidence either. We love apostrophes so much we have them on our supermarkets. If they're not there we add them. e.g. I'm going to Sainbury's e.g. I'm going to Tesco's ...despite the fact that it's real name is plain old Tesco.
https://en.wikipedia.org/wiki/Caldor
My mom used to buy small appliances and Christmas gifts there -- and she always called it Caldor's.
Clothes, she usually bought at Marshalls -- which hasn't had an apostrophe since 1974.
Earlier quoted context omitted.
Interestingly, the OpenStreetMap project considers road signage to be unquestionable "ground truth". If the sign changes, the map changes. We can't use any other database because that might not be available under a compatible licence.
I haven’t checked but how do they handle streets if the signs have two different spellings? There was a street growing up that was spelled two different ways and I still don’t know what the right one was!
Earlier quoted context omitted.
Not at all. If I understand correctly, the failure to synchronize was a fundamental flaw in the the networking code and had nothing to do with the payloads inside the networking code.
that could still be ' handling, try to sql (`type`:'express post',`from`:'st mary's street',`value`:'50') and it will drop the value field, throw an error, and quite possibly duplicate several type and half filled froms depending on how the error handling is done. This article is basically admitting its cheaper to change the street names than unfux their buggy software, so something is up. what are the other options…
By this point, the flaws are pretty well-documented. If you find anything in the reports about handling of apostrophes, feel free to cite it.
The underlying communication protocol from node to node wasn't even SQL; it was an XML format called "Riposte." There was, perhaps, SQL involved in eventual account database updating, but issues had occurred in message transit even before that phase, and it's those issues that led to account reconciliation errors and (incorrect) charges of fraud on the part of the subpostmasters.
As far as I can tell, this isn't an issue with the specific database itself, but the standard they are required to record geographic data in, which the end of the article mentions as "BS 7666". https://www.agi.org.uk/wp-content/uploads/2020/11/BS7666Guid... # Standard data types used in BS 7666 CharacterString: a sequence of alphanumeric characters ... If I had to guess, alphanumeric is interpreted as [0-9a-z]. The s…
Better not prod Falkirk council, as otherwise they'd have the issue of Bo'ness vs Borrowstounness to deal with. Similarly Grangemouth apparently has a Bo'ness Road... A related issue would be places in England named 'by-the-Sea', e.g. Newbiggin-by-the-Sea. So the signs shall simply have to match reality.
https://en.wikipedia.org/wiki/Westward_Ho%21
Edit: ironically HN formatting couldn’t handle the exclamation mark either.
So, no "O'Malley" or "O'Kelly" or "O'Brien" will ever be honored with a street name in North Yorkshire using their actual (Anglicized) name? This isn't a new issue. Around 1990 one of the computer labs at my school was run by someone with an Irish surname starting "O'", and I remember him complaining about software which couldn't handle his name. It's been 30 years, and there are still problems?!? (To say nothing of…
You can print apostrophes on a street sign without any database issues because a street sign doesn't interface directly with a database. At least not yet... All the technical issues here have already been solved a hundred times, there's plenty of other options. It's a little worrying that we're eliminating punctuation in real life because of issues with integrating with geographical databases.
Interestingly, the OpenStreetMap project considers road signage to be unquestionable "ground truth". If the sign changes, the map changes. We can't use any other database because that might not be available under a compatible licence.
I know a business which has to pay a nominal $1 license fee for the names of its own stores to a map maker, simply because the business has lost any evidence that it had the names before the map maker put them in the map.