Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: the_spui_ninja on May 02, 2025, 11:53:06 am
-
So I was going around cleaning up OpenStreetMap after the new CO 85 signage in Colorado Springs/Fountain popped up, and I noticed that we might not have the routing of US 160 in Walsenburg correct. It appears to follow the south half of the business loop, with the "through town" routing being (mostly) unsigned.
Exit 49 showing 160 west exiting I-25 (https://www.google.com/maps/@37.6151288,-104.7575515,3a,41.2y,337.22h,93.21t/data=!3m7!1e1!3m5!1sj059iI5CBOeQ2JvnZFw1-g!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-3.2073693316017255%26panoid%3Dj059iI5CBOeQ2JvnZFw1-g%26yaw%3D337.2243871894631!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D)
BL reassurance shield (https://www.google.com/maps/@37.6177441,-104.7607309,3a,41.2y,288.35h,80.52t/data=!3m7!1e1!3m5!1sK5OubtkHochjDuc_hRZhiQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D9.484756265027812%26panoid%3DK5OubtkHochjDuc_hRZhiQ%26yaw%3D288.3531157190944!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D)
160 east turns right, not left (https://www.google.com/maps/@37.6223786,-104.7813223,3a,22.2y,85.75h,88.06t/data=!3m7!1e1!3m5!1sECD3Jfvvz2wxHi9SDrmvZw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D1.9429764711394455%26panoid%3DECD3Jfvvz2wxHi9SDrmvZw%26yaw%3D85.75202976175596!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D)
I am planning to move 160 over to the BL alignment. What should I do with the old alignment? It's inventoried as "160B" by CDOT (https://dtdapps.coloradodot.info/otis/HighwayData#/ui/0/0/criteria/160B/305.526/306.35 (https://dtdapps.coloradodot.info/otis/HighwayData#/ui/0/0/criteria/160B/305.526/306.35)), but signage shows it's possibly (https://www.google.com/maps/@37.6311927,-104.7691882,3a,39.4y,362.52h,90.58t/data=!3m7!1e1!3m5!1szPUAEWYDTe8Y-yyq46FaMA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-0.5789665564299895%26panoid%3DzPUAEWYDTe8Y-yyq46FaMA%26yaw%3D2.518333098417486!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D) part of CO 10, or it's still a branch (https://www.google.com/maps/@37.6309834,-104.7696537,3a,27.3y,268.86h,91.76t/data=!3m7!1e1!3m5!1sGKPLMxawFkx-O9CXdaIGAA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-1.7562021466381026%26panoid%3DGKPLMxawFkx-O9CXdaIGAA%26yaw%3D268.8635729606974!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D) of US 160.
Random EAST 10 sign by the railroad tracks facing the road not at an intersection (https://www.google.com/maps/@37.6254877,-104.7818648,3a,90y,245.35h,76.6t/data=!3m7!1e1!3m5!1sGnXPlfrgwfIKlaq0CAdlew!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D13.396254153296809%26panoid%3DGnXPlfrgwfIKlaq0CAdlew%26yaw%3D245.35497898079598!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D)
Not really sure what to do with this one.
-
That 160 sign just west of the I-25/CO 10 interchange had a 10 sign on it (https://www.google.com/maps/@37.6310085,-104.7696677,3a,41.1y,253.46h,91.9t/data=!3m8!1e1!3m6!1soekbtEKT4_hoy0vh2DmvWw!2e0!5s20210801T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-1.9011742281044377%26panoid%3DoekbtEKT4_hoy0vh2DmvWw%26yaw%3D253.4598616269488!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D) about a year before the photo you linked, which may have just fallen off. It seems signage would support calling it CO 10 if that's what you want to do. I agree with moving 160 off that segment.
-
That 160 sign just west of the I-25/CO 10 interchange had a 10 sign on it (https://www.google.com/maps/@37.6310085,-104.7696677,3a,41.1y,253.46h,91.9t/data=!3m8!1e1!3m6!1soekbtEKT4_hoy0vh2DmvWw!2e0!5s20210801T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-1.9011742281044377%26panoid%3DoekbtEKT4_hoy0vh2DmvWw%26yaw%3D253.4598616269488!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D) about a year before the photo you linked, which may have just fallen off. It seems signage would support calling it CO 10 if that's what you want to do. I agree with moving 160 off that segment.
That was my gut thought (extend CO 10 to the business loop), but I wanted to see if anyone else had any other ideas. If no one objects, I'll extend CO 10 based on the tenuous signage (hey, it's better than nothing, right?).
-
Random EAST 10 sign by the railroad tracks facing the road not at an intersection (https://www.google.com/maps/@37.6254877,-104.7818648,3a,90y,245.35h,76.6t/data=!3m7!1e1!3m5!1sGnXPlfrgwfIKlaq0CAdlew!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D13.396254153296809%26panoid%3DGnXPlfrgwfIKlaq0CAdlew%26yaw%3D245.35497898079598!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D)
This replaced what looks like TO EAST 10 JCT EAST 160 (https://www.google.com/maps/@37.6256127,-104.7818559,3a,18.1y,200.09h,89.51t/data=!3m8!1e1!3m6!1s3ChiWuvr2ed8A9lDUgemrg!2e0!5s20071001T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.4889584935996254%26panoid%3D3ChiWuvr2ed8A9lDUgemrg%26yaw%3D200.0928871224169!7i3328!8i1664?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoASAFQAw%3D%3D) in 2007-2012. So it seems that an attempt was made to sign it as 10.
-
That 160 sign just west of the I-25/CO 10 interchange had a 10 sign on it (https://www.google.com/maps/@37.6310085,-104.7696677,3a,41.1y,253.46h,91.9t/data=!3m8!1e1!3m6!1soekbtEKT4_hoy0vh2DmvWw!2e0!5s20210801T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-1.9011742281044377%26panoid%3DoekbtEKT4_hoy0vh2DmvWw%26yaw%3D253.4598616269488!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQyOS4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D) about a year before the photo you linked, which may have just fallen off. It seems signage would support calling it CO 10 if that's what you want to do. I agree with moving 160 off that segment.
Between Sept '18 (https://maps.app.goo.gl/jWJayKAgbca29Tf49) & July '21 (https://maps.app.goo.gl/TkVisBxs2jDNWhh98), they replaced all the US-160 signage with CO-10 signage @ the I-25 Exit 50 interchange.
So, that's more evidence that US-160 was indeed rerouted and that became all CO-10.
-
https://github.com/TravelMapping/HighwayData/pull/8339 (https://github.com/TravelMapping/HighwayData/pull/8339)
Think this got it.