Some suggestions, if I may be so bold:sketch wrote:We'd also have to ask Waze to run scripts or whatever to change every instance of "State Rte" and "State Hwy" and "SR-" and "SH-", by state, to fit the state abbreviation or initial (where applicable)
- Start by making a list just from scratch to get your shields list. Though what you see on my table are screenshots from the client, initially we had just any example for the shield, design team will draw them for the client themselves.
- Collect the main used pattern for each shield you want to show. Remember, patterns are national (countrywide) currently, as you told me, even if you have the state field it's not been used in shield generation process
- Sort it out: one shield can have many pattern, but one pattern can only have one shield. You will have to decide what's to be changed, if two states used the same code. Of course, you can also have Amit persuade the devs to make use of the state field too (so every state can have a different shield for "State Hwy") - but I'm not sure if they would do it at all, and if they do what the timeframe for such rework might be.
- Once you have the complete and agreed upon list: fix up the streetnames.
From real good experiance in AU: let the editors adapt patterns in streetnames, not Waze. It's a big community thing, you will get a lot from it if you make it a community endeavour. Also, once the patterns are active, newly edited roads will get their shields automatically, so the editors have a direct feedback from theyr work.We went the different way, for most of the roads had no numbers. Now check via livemap, every road with a bullet has it's proper shield in the client, all done by the community (in allmost notime), who is VERY proud of the shields now, because all worked together to get that project done. Waze scripting might be a fast way, but doing it yourself is like adding glue to the community
Re: Shields