Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on January 21, 2022, 06:17:54 am

Title: MO: Point Concerns after 1/20/2022 Update
Post by: Markkos1992 on January 21, 2022, 06:17:54 am

I-70/US 40:  128 should be synced with the east end of I-70 BL (Columbia).

US 40:  SSteAve looks like it should just be SteAve.  The other nearby labels with prefixes in the label seem to be essential.

US 63:  The +X34a point being added has caused a duplicate label error.

Title: Re: MO: Point Concerns after 1/20/2022 Update
Post by: Markkos1992 on January 28, 2022, 02:10:34 am

After last night's revision, I have the following comments.

US 50/US 63: 
1.  CityViewDr should be McCSt (McCarty St) (https://www.google.com/maps/@38.5435809,-92.1201453,3a,75y,99.62h,77.84t/data=!3m6!1e1!3m4!1sHxYVrQpKLEKrFw-dnVdptQ!2e0!7i16384!8i8192).
2.  A point is needed at LafSt (Lafayette St) (https://www.google.com/maps/@38.5665766,-92.1644533,3a,75y,340.6h,91.24t/data=!3m6!1e1!3m4!1spVqTHQwJIrwf2QT0--aVpw!2e0!7i16384!8i8192) for the interchange there.

Title: Re: MO: Point Concerns after 1/20/2022 Update
Post by: Markkos1992 on January 31, 2022, 11:19:48 pm

I think that the US 63 points ended up out of order somehow creating a broken US 50/US 63 concurrency.

Beyond that, do you see a specific reason to not add a point at Lafayette St on US 50/US 63?  It is definitely its own full interchange.

Title: Re: MO: Point Concerns after 1/20/2022 Update
Post by: Markkos1992 on February 02, 2022, 06:45:09 am

Thanks for being prompt Highway63.