Author Topic: Clinched Routes Highway Shields  (Read 34828 times)

0 Members and 1 Guest are viewing this topic.

Offline theFXexpert

  • TM Collaborator
  • Full Member
  • *****
  • Posts: 111
  • Gender: Male
  • Last Login:Today at 09:13:00 pm
Re: Clinched Routes Highway Shields
« Reply #195 on: April 15, 2021, 10:51:03 am »
Added some new shields late last night https://github.com/TravelMapping/Web/pull/640

Manatoba Provincial Roads (the secondary system canmbp), Northwest Territory, Guam, and Texas Recreation Roads.

The Winnipeg City Routes also had really really bold numbers on them that didn't look right compared to the field posts on Streetview, so I trimmed them down.

I don't know how well the Guam shields will look since they are vertically oriented unlike almost everything else we have.

While setting up a case statement for usatxre in shieldgen to parse the numbers, I think I came up with a solution to the long standing problem of shields getting messed up when a region's tier 4 routes cross into other regions. I set up a regular expression to strip out prefixes that are exactly 2 uppercase letters. This works better than the default case which does a simple string replace based on the region. The regular expression can handle edge cases like FLA1A, TXOSR, and VTF5 easily too. With few exceptions that are already handled elsewhere, this can parse most tier 4/5 systems in the US and Canada. In the pull request, I'm using cannt as a pilot for this (a small system that crosses into Alberta a couple times). I don't think I want to make this the default case since the default case may handle prefixes we want to keep or something else.