[Talk-ca] What do I poutine the name tag of a road with a suffix?

[Minh Nguyen]

Vào lúc 00:46 2022-12-12, stevea đã viết:
> I think it would be freaking amazing if TTS (or other kinds of software-driven, "AI"(ish)-driven... use cases for OSM data) EVER became as accurate as "pronouncing" (rendering, routing, speaking...) the data in OSM as humans are at pronouncing [the same, similar] data.  Such as on a sign, when they see it, according to local convention, and determining that it IS an abbreviation, and if so HOW to (render, route, speak) that abbreviation.  But I don't think we'll ever arrive:  like Zeno's paradox [1], (Achilles and the Tortoise, I think) we'll get closer and closer, without ever truly achieving arrival / perfection.  Something like that.
> 
> I like the tenet that OSM Contributors put into the map what "is" (locally, and we seem to globally or almost globally say "eschew abbreviations"), rather than abbreviate.  If this is too long, or too abbreviated, or "inconvenient" for the "parser" (renderer, router, TTS...) let the (renderer, router, TTS...) deal with it.  If that means special casing, or "in Alberta, follow these special rules..." well, that's up to the (renderer, router, TTS...) to deal with.  So, deal with it.
> 
> This allows (continues to allow) mappers, as data entry volunteers, to follow simple rules, like "don't abbreviate" or "if the sign says Blvd. enter Boulevard."  Does Alberta have something odd going on?  Well, it can either be "untangled," or if it can't/won't, let the special-casing (in the parser) happen.

As an engineer, I'm trained in the belief that there are many 
possibilities, but there are tradeoffs to every choice. The tradeoff to 
"deal with it" is that some probably won't, to the detriment of ordinary 
end users -- or, as I like to think of them, prospective fellow OSM 
contributors.

It's true that some amount of special-casing by geography is 
unavoidable. For example, I've heard that U-turns are generally 
prohibited in British Columbia, so routers are expected to just apply 
that rule instead of relying on explict turn restrictions. Inconvenient 
for data consumers, perhaps, but workable.

On the other hand, we no longer expect renderers to add lots of special 
cases to choose route shields based on ref=* on ways. Instead, route 
relations have more structured tags like network=CA:AB:primary, so that 
renderers such as OsmAnd and OSM Americana [1] can choose the right 
shield with a minimum of guesswork. OSM tried guesswork before and it 
didn't work well.

If the messiness and lack of structure in OSM name=* tags globally 
somehow leads to a reliable, open-source, AI-powered TTS engine, then 
who could complain? But that possibility doesn't strictly need to 
prevent us from considering alternative approaches that provide more 
context when necessary, such as (speaking of Salt Lake City) the 
name:full=* key. [2]

[1] 
<https://zelonewolf.github.io/openstreetmap-americana/#map=10/53.5389/-113.4807>
[2] https://community.openstreetmap.org/t/usage-of-name-full/6382

-- 
minh at nguyen.cincinnati.oh.us