Maybe wait for waze to start supporting such features before entering nonsense into WME
You might missed the "we need [...] to discuss and agree the syntax with Waze" in OP.
From this topic
davipt wrote:Of course ideally should not be an abuse of the alt-city with freeform hashes, but a proper key-val alt-street (and even alt-city variations), but I do still hope it is a map with free values.
We agreed that we're talking about "Key-Values just like Alt street names", ok?
Sure, we can wait for Waze to start supporting some feature, then wait while they fix it, then start to add it to the map, then wait for a decision to activate it in your country... For instance, neither of recent features like gas prices, house numbers, U-turns... neither is working here in Poland. We can't even use "state" fields in an address
The benefits of the Key-Values:
- It will help Waze to concentrate their limited resources on a new feature itself, implementing it in client, adjusting search and routing server, rather than web interface. And those Key-Values are already implemented in WME as Alternate names.
- It will allow the community to review the feature before it's implemented and propose a correction. So we don't have a situation like with house numbers.
- It will allow to prepare the map data (by community) and implement the feature (by Waze staff) at the same time. And as soon as the feature is ready, Waze could even convert those Key-Values into their internal representation. Or they could convert them periodically during tiles update.
I'd really like to see people discussing the idea of Key-Values itself. But sadly, people just see Alt streets here and speculate about database performance impact