Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: mapcat on November 28, 2023, 06:36:35 pm
-
This isn't a single intersection anymore. It's laid out the way OSM shows it: one intersection for 22 and 110 (https://www.google.com/maps/@44.5130422,-88.9199376,3a,76.5y,49.81h,90.12t/data=!3m7!1e1!3m5!1sHMfTPZPL1zJRxcWdpvQcVQ!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fpanoid%3DHMfTPZPL1zJRxcWdpvQcVQ%26cb_client%3Dmaps_sv.tactile.gps%26w%3D203%26h%3D100%26yaw%3D74.644394%26pitch%3D0%26thumbfov%3D100!7i13312!8i6656?entry=ttu), where northbound 110 leaves the 22/110 concurrency, and then immediately to the north another where 161 heads west (https://www.google.com/maps/@44.5136988,-88.9200179,3a,75y,334.94h,95.7t/data=!3m6!1e1!3m4!1shFHgsoeV_--9YUeDI5N59Q!2e0!7i13312!8i6656?entry=ttu) from 110. 161 is signed at the 22/110 intersection, so there may be a short concurrency there.
-
I thought it worked better as one point due to the exceptionally short distance. Since 110 continues south, and to avoid breaking labels, I am retaining WI22/110 as the east endpoint label for WI 161. I also see a big kink in WI 110 to the north that I need to incorporate into that route.
-
I thought it worked better as one point due to the exceptionally short distance. Since 110 continues south, and to avoid breaking labels, I am retaining WI22/110 as the east endpoint label for WI 161. I also see a big kink in WI 110 to the north that I need to incorporate into that route.
You can avoid breaking .lists by keeping the ones in use as alternate labels, i.e., WI110 +WI22/110 http://www.openstreetmap.org/?lat=44.513706&lon=-88.920078 (http://www.openstreetmap.org/?lat=44.513706&lon=-88.920078)