PhoenixofMT wrote: I've also been adding u-turns to various nodes along long remote highways. A couple of times I've been routed an hour or more down a wrong turn because the "closest" place to turn around was 50 miles away - past dozens of unmapped opportunities. Often the routed u-turn is at the end of a turnoff, so it looks like a normal left or right turn, and the purple route coming back looks like the purple route going out.

Make sure you read the legality of U-turn's in Montana.

PhoenixofMT wrote:Though I'll point out that my intention is to add these to places where you can pretty much turn completely off the road and essentially make a right or left turn back the way you came. (Technically not a U-turn?) Turnouts intended to give tractors access to fields and similar are often adequate.

Are you referring to something of this nature and marking them as PLR?

PhoenixofMT wrote:I don't think I would trust myself to gauge a slope from the satellite, even on a straightaway, to suggest a place for a three-point turn on a highway.

I wouldn't be marking any U-turns on a highway personally. I think there are enough little turnouts in front of ranchers fields that you can make a U-turn safely with out it having to be marked on the map.

PhoenixofMT wrote:Kinda like that, but without the PLR. Probably a little bigger.

What would you name these?

PhoenixofMT wrote:(my Area Manager application was approved and soon I'll be able to edit the whole Gallatin valley including some areas outside of cell coverage .)

Congratulations!!! I'll add you to the list on the states Wiki page.

PhoenixofMT wrote:So basically, I'm watching out for the little turnouts you mention, or nice wide entrances to private driveways, and periodically marking a node there to allow a U-turn. You shouldn't need to drive more than a couple of miles before the client tells you to turn around.

Now that you mentioned it in the way you did it makes more sense to have those U-turns.

Ambiguous and I'm out of state for awhile.


Sent from my iPhone using Tapatalk

Sorry meant ambitious.


Sent from my iPhone using Tapatalk

Yes so this is pretty ambitious. How would you propose we go about gathering all this data? Manually searching segment by segment and then consolidating all that information will take an immense amount of time and pull us away from our main focus of editing.

The only plausible way I can see this even becoming possible would be for some one to create multiple scripts for this to pull data.

Created a To Do List to consolidate the "To Do List." Post here your thoughts that would benefit the state and then consolidate that information to be posted on the talk page.

herrchin wrote:Another TODO item would be elevation work given the newer "seagull" guidelines. Normalizing all elevation +/- levels for all interchanges, bringing railroads up from -5 to ground or the appropriate +/- if a bridge/tunnel, marking tunnels and bridges appropriately even when there's no other crossing road, etc.

Thank you for the reminder. I hadn't thought of doing this as I've been busy on the Interstate-Highway system for the wiki.

Do you have ideas for handing off the baton for a highway when someone has completed all the segments they have rights to? (that's one thing the NE county-based system handles reasonably well; it corresponds quite closely to editing rights).

As of now, MT only has a few regular (2) editors of whom all lvls are below the required lvl to make edits. So for now we will have to use the UR request thread to make edits and make a note of what has been completed.

[quote="herrchin"]Hardin was a mess when I started on it! Barely above basemap, one editor just flipped all the unknown direction roads to 2-way and left it at that. So yeah, it needs more love [WHITE SMILING FACE]️
/quote]

That it was, I never got around to it when I had it in my driving area. I was working on parts of Billings at the time. When I did get to it, some other editor cough* cough* beat me to it.

I would add fixing direction and state on the more remote roads. It's pretty frustrating to add a road and not realize that the state has defaulted to Idaho because it comes before Montana alphabetically and a bunch of nearby roads were assigned the wrong state with the base map import back in 2009. These are everywhere, and are often mixed with unknown and one-way roads, which potentially prevent routing. I've seen one-way roads not far off of the highway that would be unroutable because there's no way to get to the far end.

I've also been adding u-turns to various nodes along long remote highways. A couple of times I've been routed an hour or more down a wrong turn because the "closest" place to turn around was 50 miles away - past dozens of unmapped opportunities. Often the routed u-turn is at the end of a turnoff, so it looks like a normal left or right turn, and the purple route coming back looks like the purple route going out.