News:

The server restarts at 2 AM and 6 PM Eastern Time daily. This results in a short period of downtime, so if you get a 502 error at those times, that is why.
- Alex

Main Menu

US 31 Hamilton County, Indiana

Started by mukade, December 19, 2010, 08:20:20 PM

Previous topic - Next topic

bmeiser

#200
Fair enough.  I think the orange for Keystone should probably start north of 96th then and Kokomo 31 should definitely be orange.  Old Meridian is definitely a fuckup.

Sliverback, I didn't think they had any funding/design for that interchange either.  My dad, who works for a local highway construction company, seems to think they do so I just assumed they did.  Maybe he meant that they are "definitely planning" to put an interchange there not "definitely putting" one there.

As far as posting images go, I uploaded this screenshot to my Dropbox account and pasted the public URL for it between between "[img]" tags.  You can upload the image to any sort of image service (imgur.com is free and I don't think it even requires an account) and use the "[img]" tag to post the image.  There's a button in the toolbar (under the bold button) that will place the "[img]" tag in the post for you. Hopefully that helps!


dfwmapper

Quote from: bmeiser on December 03, 2014, 12:04:24 PM
Fair enough.  I think the orange for Keystone should probably start north of 96th then and Kokomo 31 should definitely be orange.  Old Meridian is definitely a fuckup.
Google doesn't let things exist in isolation because it looks bad when you zoom the map out. The the Kokomo bypass was freeway or expressway, it would be visible as a floating orange line with no connection to anything else at certain zoom levels. It will have to stay as it is until 31 is access controlled all the way down. Google really needs to redefine the expressway priority to be closer to OSM's trunk highway (or add another priority in between expressway and national highway), but I doubt it will ever happen.

theline

For preparing pictures to post on the board, I'd recommend tinypic.com. It's very easy to use and the result shows up with IMG tags all ready to go. No registration needed. The photos stick around for a long time too. Pictures I posted a couple of years ago still show up.

silverback1065


silverback1065

Google Maps has been a bit of a disaster on the edit front. the site keeps changing colors of everything! why do interchanges suddenly change color? they all used to be orange, now some are white.  Who makes the executive decisions there?

mukade

Quote from: dfwmapper on December 03, 2014, 12:33:46 PM
Quote from: bmeiser on December 03, 2014, 12:04:24 PM
Fair enough.  I think the orange for Keystone should probably start north of 96th then and Kokomo 31 should definitely be orange.  Old Meridian is definitely a fuckup.
Google doesn't let things exist in isolation because it looks bad when you zoom the map out. The the Kokomo bypass was freeway or expressway, it would be visible as a floating orange line with no connection to anything else at certain zoom levels. It will have to stay as it is until 31 is access controlled all the way down. Google really needs to redefine the expressway priority to be closer to OSM's trunk highway (or add another priority in between expressway and national highway), but I doubt it will ever happen.

Then why is there a short orange segment on US 23 in Delaware, Ohio and a disconnected orange segment on US 24 in Napoleon, Ohio? I think the zoom works correctly in those instances.

I think Google Maps is just very inconsistent. The US 41 freeway segment near Vincennes and SR 641 in Terre Haute are also not the right color - in addition to US 31 n Kokomo. Its a shame because they react to changes much faster than the competition, but they are also stubborn about not fixing errors when brought to their attention. I don't even bother anymore.

silverback1065

Quote from: mukade on December 03, 2014, 09:04:36 PM
Quote from: dfwmapper on December 03, 2014, 12:33:46 PM
Quote from: bmeiser on December 03, 2014, 12:04:24 PM
Fair enough.  I think the orange for Keystone should probably start north of 96th then and Kokomo 31 should definitely be orange.  Old Meridian is definitely a fuckup.
Google doesn't let things exist in isolation because it looks bad when you zoom the map out. The the Kokomo bypass was freeway or expressway, it would be visible as a floating orange line with no connection to anything else at certain zoom levels. It will have to stay as it is until 31 is access controlled all the way down. Google really needs to redefine the expressway priority to be closer to OSM's trunk highway (or add another priority in between expressway and national highway), but I doubt it will ever happen.

Then why is there a short orange segment on US 23 in Delaware, Ohio and a disconnected orange segment on US 24 in Napoleon, Ohio? I think the zoom works correctly in those instances.

I think Google Maps is just very inconsistent. The US 41 freeway segment near Vincennes and SR 641 in Terre Haute are also not the right color - in addition to US 31 n Kokomo. Its a shame because they react to changes much faster than the competition, but they are also stubborn about not fixing errors when brought to their attention. I don't even bother anymore.
It's quite frustrating dealing with their bs I've only been approved once without proof. But even with valid proof they refuse!

tdindy88

Someone needs to get on their ass about Old Meridian though, that's just plain wrong. I'm almost willing to let US 31 and Keystone slide as they appear now, but not Old Meridian. Next thing I know Keystone will be a freeway down to Binford Blvd.

dfwmapper

Quote from: mukade on December 03, 2014, 09:04:36 PM
Then why is there a short orange segment on US 23 in Delaware, Ohio and a disconnected orange segment on US 24 in Napoleon, Ohio? I think the zoom works correctly in those instances.
Because Ohio is outside the area I usually map in. Submitted edits to fix them though.
QuoteI think Google Maps is just very inconsistent. The US 41 freeway segment near Vincennes and SR 641 in Terre Haute are also not the right color - in addition to US 31 n Kokomo. Its a shame because they react to changes much faster than the competition, but they are also stubborn about not fixing errors when brought to their attention. I don't even bother anymore.
Those are all correct as they are per guidelines. 641 can probably be justified as a freeway once it's open all the way to I-70.

Quote from: tdindy88 on December 03, 2014, 10:06:17 PM
Someone needs to get on their ass about Old Meridian though, that's just plain wrong. I'm almost willing to let US 31 and Keystone slide as they appear now, but not Old Meridian. Next thing I know Keystone will be a freeway down to Binford Blvd.
Already taken care of.

mukade

Quote from: dfwmapper on December 04, 2014, 12:06:25 AM
Quote from: mukade on December 03, 2014, 09:04:36 PM
Then why is there a short orange segment on US 23 in Delaware, Ohio and a disconnected orange segment on US 24 in Napoleon, Ohio? I think the zoom works correctly in those instances.
Because Ohio is outside the area I usually map in. Submitted edits to fix them though.
QuoteI think Google Maps is just very inconsistent. The US 41 freeway segment near Vincennes and SR 641 in Terre Haute are also not the right color - in addition to US 31 n Kokomo. Its a shame because they react to changes much faster than the competition, but they are also stubborn about not fixing errors when brought to their attention. I don't even bother anymore.
Those are all correct as they are per guidelines. 641 can probably be justified as a freeway once it's open all the way to I-70.

Quote from: tdindy88 on December 03, 2014, 10:06:17 PM
Someone needs to get on their ass about Old Meridian though, that's just plain wrong. I'm almost willing to let US 31 and Keystone slide as they appear now, but not Old Meridian. Next thing I know Keystone will be a freeway down to Binford Blvd.
Already taken care of.

If I understand your comment right, guidelines trump reality? This section of US 412 would also be "wrong": https://www.google.com/maps/@36.1952949,-94.9452078,10z?

So how do weird errors keep coming back? Two examples are US 24 from Antwerp to Defiance. This has gone back and forth between freeway and non freeway more than once. It is not a freeway, but it is shown in orange. Compare that to real sections of freeway that are not shown in orange (for example, the ones like US 31 Kokomo which once was shown in orange and others cited in this thread). Another example is US 52 in Lafayette is another one that is confounding. That route follows Teal Road and the US 231 bypass, not Sagamore Parkway. I am pretty sure it has been shown right in the past, but it is back to being wrong.

So back to US 31 - it is great that Gmaps beats everyone with timely updates, but what are even more important things are accuracy and consistency. It seems like some subjective guidelines trump reality. I'm not talking about errors like we see with Old Meridian. That seems to have been fixed already as noted.

NE2

The Goog likes to apply its own rules to reality, reality be damned.

Someone should downgrade the entire Hawaiian freeway system because it's not connected to any others.
pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

dfwmapper

Quote from: mukade on December 04, 2014, 06:01:46 AM
If I understand your comment right, guidelines trump reality? This section of US 412 would also be "wrong": https://www.google.com/maps/@36.1952949,-94.9452078,10z?
Yes. It should probably be marked as an expressway from the I-44 interchange to the east end of the Cherokee Turnpike, but that would be hard to get approved with as many at-grade intersection as there are. The Goog's priorities really don't apply well to the west and midwest where it isn't worth grade-separating every section line road that has a dozen people living off of it, or building frontage roads for farm driveways with an AADT in the single digits.
QuoteSo how do weird errors keep coming back? Two examples are US 24 from Antwerp to Defiance. This has gone back and forth between freeway and non freeway more than once. It is not a freeway, but it is shown in orange. Compare that to real sections of freeway that are not shown in orange (for example, the ones like US 31 Kokomo which once was shown in orange and others cited in this thread).
US 24 is marked as an expressway from the first at-grade intersection eastward, which is correct. Expressway and freeway both show up in orange, though expressways were yellow for quite a while when they made the change to make arterials white instead of light yellow.
QuoteAnother example is US 52 in Lafayette is another one that is confounding. That route follows Teal Road and the US 231 bypass, not Sagamore Parkway. I am pretty sure it has been shown right in the past, but it is back to being wrong.
There's something corrupt internally that is preventing that getting fixed. Tried to fix that when I fixed IN 25, but it wouldn't submit. it's been reported, so it might get fixed sometime this millennium.
QuoteSo back to US 31 - it is great that Gmaps beats everyone with timely updates, but what are even more important things are accuracy and consistency. It seems like some subjective guidelines trump reality. I'm not talking about errors like we see with Old Meridian. That seems to have been fixed already as noted.
What difference does it make in your driving life if 11 miles of the road is orange vs. yellow? Either way it's obvious that it is the primary N/S route, and directions are going to send you over it. Consistency with the rest of US 31 means it should stay yellow.

NE2

There are a shitload of freeways that are correctly marked on the Goog and don't connect to anything else. See Virginia, Myrtle Beach, even I-22 for now. Don't do the Goog's dirty work for them like a good German in the 1930s.

(And then there's WIS 29, which isn't a freeway but appears as one. Same with US 101 south of Frisco and US 395 in Washington.)
pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

billtm

I know this may be a little off topic, but I don't think it requires its own thread. Does anyone know how to access satellite imagery on the new Google maps? :confused:

silverback1065

Quote from: billtm on December 04, 2014, 03:14:53 PM
I know this may be a little off topic, but I don't think it requires its own thread. Does anyone know how to access satellite imagery on the new Google maps? :confused:

Just click on the box on the lower left side of the screen it should look like a tiny satellite view of the area you are zoomed into. it's labeled "earth" even though it isn't referring to the program

NE2

Quote from: billtm on December 04, 2014, 03:14:53 PM
I know this may be a little off topic, but I don't think it requires its own thread. Does anyone know how to access satellite imagery on the new Google maps? :confused:
Click the question mark, then "return to classic Google Maps". :bigass:
pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

silverback1065

Quote from: NE2 on December 04, 2014, 03:50:43 PM
Quote from: billtm on December 04, 2014, 03:14:53 PM
I know this may be a little off topic, but I don't think it requires its own thread. Does anyone know how to access satellite imagery on the new Google maps? :confused:
Click the question mark, then "return to classic Google Maps". :bigass:
That also works. I am happy that the distance measurement tool is back and better than ever!

bmeiser


silverback1065

It's already showing up on Google Maps. That's the fastest I've seen that happen.

billtm

Will there be more flyover ramps, or is the interchange now completed?

silverback1065

Quote from: billtm on December 17, 2014, 05:29:06 PM
Will there be more flyover ramps, or is the interchange now completed?

one more, it will go from 465 east to us 31 n.  check this out: http://us31hamiltoncounty.in.gov/wp-content/uploads/2014/01/b_465-LEAN.jpg

billtm

Quote from: silverback1065 on December 17, 2014, 05:30:41 PM
Quote from: billtm on December 17, 2014, 05:29:06 PM
Will there be more flyover ramps, or is the interchange now completed?

one more, it will go from 465 east to us 31 n.  check this out: http://us31hamiltoncounty.in.gov/wp-content/uploads/2014/01/b_465-LEAN.jpg
So that means there will still be a stoplight for WB I-465 to SB US-31 traffic?

silverback1065

Quote from: billtm on December 17, 2014, 05:34:26 PM
Quote from: silverback1065 on December 17, 2014, 05:30:41 PM
Quote from: billtm on December 17, 2014, 05:29:06 PM
Will there be more flyover ramps, or is the interchange now completed?

one more, it will go from 465 east to us 31 n.  check this out: http://us31hamiltoncounty.in.gov/wp-content/uploads/2014/01/b_465-LEAN.jpg
So that means there will still be a stoplight for WB I-465 to SB US-31 traffic?

From the looks of it yes. and there may be one for EB 465 to SB meridian st.  The geometry of that ramp makes me think they will need a light or a yield sign, but those are guesses by me.

billtm

Quote from: silverback1065 on December 17, 2014, 05:38:10 PM
Quote from: billtm on December 17, 2014, 05:34:26 PM
Quote from: silverback1065 on December 17, 2014, 05:30:41 PM
Quote from: billtm on December 17, 2014, 05:29:06 PM
Will there be more flyover ramps, or is the interchange now completed?

one more, it will go from 465 east to us 31 n.  check this out: http://us31hamiltoncounty.in.gov/wp-content/uploads/2014/01/b_465-LEAN.jpg
So that means there will still be a stoplight for WB I-465 to SB US-31 traffic?

From the looks of it yes. and there may be one for EB 465 to SB meridian st.  The geometry of that ramp makes me think they will need a light or a yield sign, but those are guesses by me.

Since both stoplights are going to SB Meridian St., does that mean I-67 is still possible :sombrero:, or does the whole interchange have to be free-flowing? :confused:

silverback1065

Quote from: billtm on December 17, 2014, 05:43:14 PM
Quote from: silverback1065 on December 17, 2014, 05:38:10 PM
Quote from: billtm on December 17, 2014, 05:34:26 PM
Quote from: silverback1065 on December 17, 2014, 05:30:41 PM
Quote from: billtm on December 17, 2014, 05:29:06 PM
Will there be more flyover ramps, or is the interchange now completed?

one more, it will go from 465 east to us 31 n.  check this out: http://us31hamiltoncounty.in.gov/wp-content/uploads/2014/01/b_465-LEAN.jpg
So that means there will still be a stoplight for WB I-465 to SB US-31 traffic?

From the looks of it yes. and there may be one for EB 465 to SB meridian st.  The geometry of that ramp makes me think they will need a light or a yield sign, but those are guesses by me.

Since both stoplights are going to SB Meridian St., does that mean I-67 is still possible :sombrero:, or does the whole interchange have to be free-flowing? :confused:

I think 67 would work since it would use ramps that you wouldn't have to stop at.



Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.