Author Topic: SC 31 extended  (Read 733 times)

0 Members and 1 Guest are viewing this topic.

Offline ohroadscholar

  • Newbie
  • *
  • Posts: 4
  • Gender: Male
  • Last Login:September 29, 2020, 08:58:29 pm
SC 31 extended
« on: September 15, 2020, 11:10:00 pm »
SC 31 extension from SC 544 to SC 707 is now open in the Myrtle Beach Area. There are no other exits between 544 and 707.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1722
  • Last Login:Today at 07:05:39 pm
Re: SC 31 extended
« Reply #1 on: September 16, 2020, 11:18:59 am »
It looks like it was an issue on our end with moving the route from usanf to usasc.  This was already done when we finished usasc.


Issue: https://forum.travelmapping.net/index.php?topic=104.105

Posts on adding SC 31 extension: https://forum.travelmapping.net/index.php?topic=104.msg16240#msg16240

Fix for SC 31 in usasc:  https://github.com/TravelMapping/HighwayData/pull/4176

mapmikey, as the maintainer for usasc, please make sure everything looks right before marking this as solved.

EDIT:  Jim requested on Github that your approval be placed here as well. 



« Last Edit: September 16, 2020, 06:38:36 pm by Markkos1992 »

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 830
  • Last Login:Today at 07:45:06 am
    • Co-curator Virginia Highways Project
Re: SC 31 extended
« Reply #2 on: September 17, 2020, 09:09:41 am »
After looking at the github conversation, I believe I am being asked if it is ok for you guys to make the change to get SC 31 fully in the SC State Highway list.

The way I do updates for any of my states is to copy/paste the route waypoints off the github file for the route, make the changes in notepad and save on my PC, then when all changes are done, e-mail them to Jim.

I do it this way to ensure I don't unintentionally undo a change somebody else might have made with or without my knowledge.

So my repository is only good for dire emergency - as in the github site completely loses the file and cannot be recovered.

Short answer:  yes...please make the fix to SC 31

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2162
  • Last Login:Today at 06:00:03 pm
Re: SC 31 extended
« Reply #3 on: September 17, 2020, 10:50:41 am »
Great - I'll merge it in tonight.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1722
  • Last Login:Today at 07:05:39 pm
Re: SC 31 extended
« Reply #4 on: September 17, 2020, 11:34:00 am »
Quote
I do it this way to ensure I don't unintentionally undo a change somebody else might have made with or without my knowledge.

I did not even use your repository.  I used the overall master usanf file that was leftover for SC 31.

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 830
  • Last Login:Today at 07:45:06 am
    • Co-curator Virginia Highways Project
Re: SC 31 extended
« Reply #5 on: September 17, 2020, 04:34:42 pm »
Quote
I do it this way to ensure I don't unintentionally undo a change somebody else might have made with or without my knowledge.

I did not even use your repository.  I used the overall master usanf file that was leftover for SC 31.

I'm apparently using the term repository for the wrong thing.  I mean the repository on my PC at home.  If I have access to some other repository on Github I am ignorant of it.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1722
  • Last Login:Today at 07:05:39 pm
Re: SC 31 extended
« Reply #6 on: September 17, 2020, 05:04:32 pm »
You are correct.  I was thinking about Github.  I am sure you have a Github repository, but I doubt with the way you submit files that it was ever used.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1722
  • Last Login:Today at 07:05:39 pm
Re: SC 31 extended
« Reply #7 on: September 20, 2020, 08:55:13 am »
Did we want to extend SC I-74FutMyr to SC 707?  I did not seem to think about this before oddly enough.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1722
  • Last Login:Today at 07:05:39 pm
Re: SC 31 extended
« Reply #8 on: September 25, 2020, 07:11:41 pm »
https://forum.travelmapping.net/index.php?topic=3826.0

I think that we should treat this situation based on what we do for I-66FutBow in KY.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1722
  • Last Login:Today at 07:05:39 pm
Re: SC 31 extended
« Reply #9 on: September 28, 2020, 03:54:15 pm »
https://forum.travelmapping.net/index.php?topic=3826.0

I think that we should treat this situation based on what we do for I-66FutBow in KY.

https://forum.travelmapping.net/index.php?topic=1837.msg20511#msg20511

I support deleting SC I-74FutMyr at this point.  Who knows if/when I-74 will be in SC...

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 830
  • Last Login:Today at 07:45:06 am
    • Co-curator Virginia Highways Project
Re: SC 31 extended
« Reply #10 on: September 29, 2020, 06:41:47 am »
This would also be my inclination.  Even if it does come someday, will it actually exist south of SC 22 (I-73) or US 501?  I don't think there are any plans to extend the freeway further south...seems like if it were easy to do they would've taken it back to US 17.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3343
  • Last Login:Today at 02:01:59 pm
Re: SC 31 extended
« Reply #11 on: November 19, 2020, 02:58:34 am »
It seems a bit suspect that the end of a supposedly E-W route would turn around and go that far back west. That's way worse than I-64.
Anyone remember what the original rationale was for including this, or was it all Tim?
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1524
  • Last Login:Today at 04:46:55 pm
Re: SC 31 extended
« Reply #12 on: November 19, 2020, 04:51:16 am »
There's not any future corridor signs on these. Happily vote for a delete, even if we keep usaif, as they are very much unsigned.