The segment selected in the URL is improperly labeled and locked as “I-35 N” on both sides of the freeway and should be labeled as “I-35 S”. Confusing when the GPS says “Turn on I-35 North… Enter ramp onto I-35 South”. This issue begins approximately where selected and continues to be improperly/inconsistently named nearly to San Marcos.
Going South all the way to Loop 1604, the naming is inconsistent going from I-35 N/S to “Exchange Ave” to “I-35 Access Road” and marked as a Service Road to a Primary Road. All of the I-35 access roads north of Loop 1604 to San Marcos need to be unlocked or updated to be named and marked consistently. Thanks!
Most of the Southbound access roads have been updated to reflect “I-35 S” but some further North starting in New Braunfels at Hwy 46/Loop 337 still show “I-35 N” on both sides of the highway and some random segments are locked, some aren’t. These still need to be corrected.
Also, no changes have been made further South near FM 3009 going further South into San Antonio, the road type suddenly alternates from Service Road to Primary Street and the name changes from “I-35 S” to “Exchange Ave” to “I-35 Access Rd”. These access roads should have a consistent name and road type.
I’m working on this as I get to it. I have been waiting for an unlock request to go through to fix the primary streets/service road part that you’re talking about. I know exactly what and where you’re talking about. I’m working on it. Give me a little time and I’ll get to it. I usually work on the map 2 hours at a time looking for all sorts of things. As soon as that unlock request comes through, I’ll get it taken care of.
One thing to keep in mind is that the road may locally be known as something like “N I-35 S Service Rd” or “Exchange Ave” or something else. For instance, in my area, US Hwy 75 has N and S designations on the highway only but the Service Rd is N Central Expy and in this case N/S has to do with falling on the North side of the city vs. the South, not the directionality. So even SB traffic is on “N Central Expy”. Just be careful that the changes you request are reflected on the local signage. Some service roads do have names in certain parts of town.
I cannot locate any signs along “Exchange Ave” marking is as such, nor can I find any establishments addressed as “Exchange Ave”. Besides that, there is already an Exchange Ave a few miles off I-35 within the same city of Schertz:
I don’t think there can be two completely separate streets within the same city with the same street name. I think it may just be an error in Google or some other map database that got carried over into Waze when its map database was built. These access roads along I-35 are not named, they are simply on/off access roads for the freeway. All establishments that I can find are addressed as “IH 35 North/South”, for example Enterprise car rental in Schertz address is “17299 IH 35 NORTH” but cannot be found by Google map search because the road is incorrectly labeled as “Exchange Ave”. This is the purpose of Waze, it’s user managed by people that know the roads. Google doesn’t know them like we do.
I also flagged a map error traveling North on I-35 tonight where the navigation randomly routed me off the freeway. “txemt” marked it as “Not Identified” within about an hour after I marked the map issue. The problem is quite obvious, and I dropped the marker directly on it as I drove by. This segment is also locked and was last modified on Thu Aug 09 2012 by txemt. Please fix this error.
There have been quite a few of the “general error” reports that Wazers have been sending in, but don’t give an exact reason as to what the problem is. I usually spend a good 5 minutes trying to figure out what’s wrong. I check connections in the area, look at segment names, and look before I select “not identified.” I wish there was a way to ask the user for more information about the issue when something isn’t found.
Sometimes I assume the GPS location is off on where the person happens to be traveling. If you take the lower level of I-10 toward downtown, the GPS will put you on side streets 2 blocks from the interstate. I’ve seen URs for that exact problem and there’s nothing we can do to fix that.
Also, changes here take about 10 days to reflect in the app. If there is anything else that you can see that needs to be fixed, let us know.
I would like to invite you to figure out what’s wrong with these “general errors.” If you can figure it out, you’ve done a better job than I have. This is most likely similar to what I saw when I clicked “not identified” for your request.
I don’t see anything wrong with those, I-10 & Vance Jackson seems to be marked in the middle of a shopping mall and Olmos Creek Dr looks fine.
I see a ton of changes on I-35 and its looking great, thanks! If we can just get more segments, particularly Ramps, unlocked then it will be as good as it can get.
On Vance Jackson, the only proper way into the whole shopping center heading northbound is a left on Greencrest. Drivers will make lefts into the cutouts, so I’m locking that section so it doesn’t flip. I mapped the parking lot, it used to be mapped out and turn restrictions set; not sure what happened there. Also, that section of Vance Jackson gets gridlocked from Greencrest to I-10, so it could just be that.
Olmos Creek, someone probably wants a driveway into that apartment complex. I did notice that routes from NB Huebner to SB Military were cutting through there. Though that’s not a problem if it is a quicker route, something else might be wrong with the section of Huebner that gets cut. I added parking lots and parking lot roads to trap the drive-thrus. If problems keep popping up around that area, it might be that Huebner needs to be redone.
The New Braunfels/San Marcos area is full of locks by that user that need to be unlocked. Those were made when locking was something different. I don’t lock my segments (except a few), I think it’s ridiculous to do it.