1. Failure to capitalize "La" of "La Cruz".kentsmith9 wrote:Why are these two an error?
"S De la Cruz Blvd" → error.
"N Via de las Cruces Hwy" → error.
2. Failure to capitalize "Las" of "Las Cruces".
- a few thousand comparisons - not hundreds of thousands. But if it is too slow, make the squares smaller.berestovskyy wrote: No doubt those buckets will reduce number of comparisons, but add complexity. And still there are will be thousands of comparisons and the check still will be very slow.
I would be looking for drivable segments at the same elevation that touch or cross without forming a junction. These might look okay, but they do not route correctly.berestovskyy wrote: So we're looking at quite slow and complex check here. But what's is the "goal"? Does this non-ground elevation affects TTS or routing?
Are you now satisfied that there is no discrepancy between my statements?kentsmith9 wrote: I saw a discrepancy between your two statements that I could not identify the correct solution.
Current exceptions for the USA for first word of name:kentsmith9 wrote: I did not see the official list linked to what letters are supposed to be allowed in each country.
The main point of my post was to demonstrate that allowing a word to be lowercase necessarily will fail to detect when that word should be capitalized and that the compass direction (e.g., "W de Vanter Ave") must be excluded when evaluating what is the first letter of a name.kentsmith9 wrote: I now understand the second one if 'las' is not on the accepted list. I would then understand the first one if 'de' was not on the original displayed list.
I am saying that this is necessary to make check #94 complete - and that checking every word against a list cannot substitute for checking the first actual word alone. So we need a list of words that are ignored at the beginning of a name ("E", "N", "S", "W", "to"). A note that false positives are theoretically possible is fine by me.sketch wrote:A Validator check for first letter notwithstanding initial compass directions is fine ...
No. Go right ahead. I just made up the list myself as I was replying. It is not canon or accurate.kentsmith9 wrote: Thanks for the list. Is this list agreed by the whole USA community? I am not questioning your accuracy,
I cannot comment much on other countries.kentsmith9 wrote: Maybe the problem is berestovskyy's message was for all countries and yours was only for the USA?
But if that is the case, in California we have plenty of Spanish roads, so if "la" and "de" are allowed in other countries, why not allow it in the US?
Yes, this is just a transition from divided to undivided. I thought that it was a simple case for demonstration. I didn't know that you had logic to detect an intersection.berestovskyy wrote:Validator does not report too-sharp bow-ties.
Sure, Validator can look for similar street names, but I guess it will eliminate any use of this check, because the check basically was designed to detect situations like this...
NOTE: Be aware of the geometry used in the bow tie. If the angles are too steep (45 degrees or greater) a driver traveling along one of the one-way segments may be told to "turn" or "stay" at the intersection instead of receiving no instruction.