SC 31 extended

[ohroadscholar]

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.

[Markkos1992]

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. 

[mapmikey]

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

[Jim]

Great - I'll merge it in tonight.

[Markkos1992]

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.

[mapmikey]

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.

[Markkos1992]

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.

[Markkos1992]

Did we want to extend SC I-74FutMyr to SC 707?  I did not seem to think about this before oddly enough.

[Markkos1992]

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.

[Markkos1992]

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...

[mapmikey]

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.

[yakra]

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?

[si404]

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.

[rickmastfan67]

Is this thread fully completed?  Just trying to mark some old threads (2+ years old since last post) as 'solved' so they can be moved to the other section.

[Markkos1992]

I only kept it open in regard to deleting Future I-74, which has not been deleted.