Re: [Talk-us] South Carolina State Highways - primary overload
All, On 09.12.2013 06:42, James Mast wrote: Is it just me, or are there way too many primary state highways when some of them should really be secondary instead? After this discussion has now more or less concluded that we should be reverting the edits in question, I have compiled a list of all highways where user mjbyars has changed the highway type at some point in the past, and reverted them to the previous highway type. Only the highway tag was changed in this process, everything else remained in the current state. The revert changeset is this: http://www.openstreetmap.org/changeset/20401446 There may be some situations where a way was split by the user (which to the database looks like a modification of one way and a new creation of another); in these cases, the new highway will likely still be of the former (higher) highway type and not be reverted. So if you do spot the odd remnant of primary overload, please do fix it by hand. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
Thank you Frederik. Really appreciate it. -James Date: Wed, 5 Feb 2014 22:59:57 +0100 From: frede...@remote.org To: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload All, On 09.12.2013 06:42, James Mast wrote: Is it just me, or are there way too many primary state highways when some of them should really be secondary instead? After this discussion has now more or less concluded that we should be reverting the edits in question, I have compiled a list of all highways where user mjbyars has changed the highway type at some point in the past, and reverted them to the previous highway type. Only the highway tag was changed in this process, everything else remained in the current state. The revert changeset is this: http://www.openstreetmap.org/changeset/20401446 There may be some situations where a way was split by the user (which to the database looks like a modification of one way and a new creation of another); in these cases, the new highway will likely still be of the former (higher) highway type and not be reverted. So if you do spot the odd remnant of primary overload, please do fix it by hand. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
All right, I'll be sending the e-mail to the DWG in a few minutes then. Life has been a little crazy here preventing me from doing it sooner than this. -James From: mart...@openstreetmap.us Date: Wed, 29 Jan 2014 07:07:48 -0800 To: rickmastfa...@hotmail.com CC: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload I think you're making the right call, James. On Tue, Jan 28, 2014 at 11:33 PM, James Mast rickmastfa...@hotmail.com wrote: So, nobody else has a comment on how the repair work should be done? Last chance before I respond back to the DWG e-mail (and as of right now, will be recommending just the reverting of only the 'highway=xxx' upgrades). Just want to make sure the masses don't have a problem with this. -James From: rickmastfa...@hotmail.com To: talk-us@openstreetmap.org Date: Mon, 20 Jan 2014 05:01:19 -0500 Subject: Re: [Talk-us] South Carolina State Highways - primary overload Nobody else has a comment on what should be done here? If you don't remember the start of this discussion of this subject, here's the link to the original post I made on this subject to the list so you can see it: https://lists.openstreetmap.org/pipermail/talk-us/2013-December/012349.html -James Date: Thu, 16 Jan 2014 07:24:50 -0500 From: nice...@att.net To: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload On 1/16/2014 12:16 AM, James Mast wrote: Anyways guys, post what you think should be done here so I can get back to the DWG on this subject. (I'm personally all for the reverting of the highway=xxx upgrades this user has done only and not a full scale revert of all his changesets as he did do some highway cleanup in some changesets while doing the 'highway=xxx' upgrades.) I would be for the revert of the highway=xxx changes. While the Wiki has no hard and fast rule on the 'right way' to tag these, clearly some information has been lost by eliminating a highway type. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel President, US Chapter OpenStreetMap http://openstreetmap.us/ http://osm.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
On Sun, Dec 22, 2013 at 7:42 PM, Greg Morgan dr.kludge...@gmail.com wrote: I use residential for 0 to 25 mph residential roads. That tag seems obvious. I use tertiary for 30 to 35 mph roads. I see most of these types of roads as connecting residential subdivisions. These roads tend to have bike lanes too. I also see dashed yellow lines or two solid yellow lines as another indication of changing the road to tertiary in mostly residential areas. I use secondary for 40 to 45 mph roads. I like the simplicity of that scheme, but it sort of breaks down when you go up to primary and trunk - many urban primary roads will also be 35-35 mph. What do you do for trunk roads? -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
I think you're making the right call, James. On Tue, Jan 28, 2014 at 11:33 PM, James Mast rickmastfa...@hotmail.com wrote: So, nobody else has a comment on how the repair work should be done? Last chance before I respond back to the DWG e-mail (and as of right now, will be recommending just the reverting of only the 'highway=xxx' upgrades). Just want to make sure the masses don't have a problem with this. -James From: rickmastfa...@hotmail.com To: talk-us@openstreetmap.org Date: Mon, 20 Jan 2014 05:01:19 -0500 Subject: Re: [Talk-us] South Carolina State Highways - primary overload Nobody else has a comment on what should be done here? If you don't remember the start of this discussion of this subject, here's the link to the original post I made on this subject to the list so you can see it: https://lists.openstreetmap.org/pipermail/talk-us/2013-December/012349.html -James Date: Thu, 16 Jan 2014 07:24:50 -0500 From: nice...@att.net To: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload On 1/16/2014 12:16 AM, James Mast wrote: Anyways guys, post what you think should be done here so I can get back to the DWG on this subject. (I'm personally all for the reverting of the highway=xxx upgrades this user has done only and not a full scale revert of all his changesets as he did do some highway cleanup in some changesets while doing the 'highway=xxx' upgrades.) I would be for the revert of the highway=xxx changes. While the Wiki has no hard and fast rule on the 'right way' to tag these, clearly some information has been lost by eliminating a highway type. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel President, US Chapter OpenStreetMap http://openstreetmap.us/ http://osm.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
So, nobody else has a comment on how the repair work should be done? Last chance before I respond back to the DWG e-mail (and as of right now, will be recommending just the reverting of only the 'highway=xxx' upgrades). Just want to make sure the masses don't have a problem with this. -James From: rickmastfa...@hotmail.com To: talk-us@openstreetmap.org Date: Mon, 20 Jan 2014 05:01:19 -0500 Subject: Re: [Talk-us] South Carolina State Highways - primary overload Nobody else has a comment on what should be done here? If you don't remember the start of this discussion of this subject, here's the link to the original post I made on this subject to the list so you can see it: https://lists.openstreetmap.org/pipermail/talk-us/2013-December/012349.html -James Date: Thu, 16 Jan 2014 07:24:50 -0500 From: nice...@att.net To: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload On 1/16/2014 12:16 AM, James Mast wrote: Anyways guys, post what you think should be done here so I can get back to the DWG on this subject. (I'm personally all for the reverting of the highway=xxx upgrades this user has done only and not a full scale revert of all his changesets as he did do some highway cleanup in some changesets while doing the 'highway=xxx' upgrades.) I would be for the revert of the highway=xxx changes. While the Wiki has no hard and fast rule on the 'right way' to tag these, clearly some information has been lost by eliminating a highway type. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
Nobody else has a comment on what should be done here? If you don't remember the start of this discussion of this subject, here's the link to the original post I made on this subject to the list so you can see it: https://lists.openstreetmap.org/pipermail/talk-us/2013-December/012349.html -James Date: Thu, 16 Jan 2014 07:24:50 -0500 From: nice...@att.net To: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload On 1/16/2014 12:16 AM, James Mast wrote: Anyways guys, post what you think should be done here so I can get back to the DWG on this subject. (I'm personally all for the reverting of the highway=xxx upgrades this user has done only and not a full scale revert of all his changesets as he did do some highway cleanup in some changesets while doing the 'highway=xxx' upgrades.) I would be for the revert of the highway=xxx changes. While the Wiki has no hard and fast rule on the 'right way' to tag these, clearly some information has been lost by eliminating a highway type. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
On 1/16/2014 12:16 AM, James Mast wrote: Anyways guys, post what you think should be done here so I can get back to the DWG on this subject. (I'm personally all for the reverting of the highway=xxx upgrades this user has done only and not a full scale revert of all his changesets as he did do some highway cleanup in some changesets while doing the 'highway=xxx' upgrades.) I would be for the revert of the highway=xxx changes. While the Wiki has no hard and fast rule on the 'right way' to tag these, clearly some information has been lost by eliminating a highway type. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
I have finally heard back from the DWG group on this subject. They said that they lack the manpower to actually investigate these edits and find out what they should be. However, they said that they can identify *every* highway=xxx upgrade that the user did in a time frame and revert them. They would need to rely on us here in the talk-us community though to let them know if this seems like a sensible thing to do in this case before they do anything. So, do you guys think we should ask them to do a revert on all of the highway=xxx upgrade changes the user made in South Carolina (and also where he did it in Georgia too)? We would need to try to lock down the time period that he did this in changeset # wise so that there are no problems with the highway type revert. It just sucks that with the new OSM layout, that got rid of the page #'s in the URLs for a user's changesets. That would have made this job a tad easier to do allowing just url editing to get to older changesets he did. Anyways guys, post what you think should be done here so I can get back to the DWG on this subject. (I'm personally all for the reverting of the highway=xxx upgrades this user has done only and not a full scale revert of all his changesets as he did do some highway cleanup in some changesets while doing the 'highway=xxx' upgrades.) -James ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
On Tue, Dec 10, 2013 at 6:25 PM, Martijn van Exel mart...@openstreetmap.uswrote: I think discussion can only be useful if and when we have a common understanding of what 'trunk', 'primary', 'secondary' etc. mean to us. I don't think we're anywhere close to that, looking at the various and partly mutually contradictory wiki pages on the topic: I think this part of the tagging scheme that is the most puzzling issue for US mappers. In the Phoenix area, http://www.openstreetmap.org/#map=11/33.5683/-112.0901, I've used primary as a way of showing travelers what is the best way to get through all of our mountain preserve areas. Since the traffic has to funnel through these passages the amount of traffic that these roads has to handle probably lines up with what a primary road should be. I use residential for 0 to 25 mph residential roads. That tag seems obvious. I use tertiary for 30 to 35 mph roads. I see most of these types of roads as connecting residential subdivisions. These roads tend to have bike lanes too. I also see dashed yellow lines or two solid yellow lines as another indication of changing the road to tertiary in mostly residential areas. I use secondary for 40 to 45 mph roads. The roads that I have marked as primary are any where from 35 mph to 50 mph. I use motorway for the major concrete highways. This gives me a plan that I can follow with some consistency even if I cannot say that it is the correct thing to do. I ignore JOSM validation on this question because there is no highway reference for tertiary, secondary, and primary in most cases where I have used the tags. However, leaving a more than 25 mph road as residential seems like the wrong thing to do. I hope this helps, Greg ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
2013/12/11 Evin Fairchild evindf...@gmail.com I think the reason why things like this happen is because the highway tagging scheme in OSM was modeled off of UK's road-classification system and really isn't compatible with the road-classification system in the US. it is mainly the names that are taken from the UK classification. Every road system is compatible with the current system, you simply have to structure the data according to relative importance of the road (i.e. an unclassified is less important than a tertiary which is less important than a secondary than a primary). If you need additional attributes (like state-highway) this doesn't necessarily have to be expressed in the main highway tag. E.g. in Germany there are some streets that despite not being a motorway have an additional sign which restricts usage to certain motorized vehicles (no small motorcycles, no pedestrians, no bikes etc.) and we detached this from the main highway classification and add an additional motorroad=yes to these. If state-highway means that maintenance is done by the state you could also use operator=* for these (or maybe you can already see this property by the ref tag?). cheers, Martin ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
I found this to be very annoying. I did a lot of work on the SC Highways some time back. I noticed that in a few counties most of the state highways were marked as primary. I reverted most of them back to secondary except for the ones that were truly trunk routes. Its frustrating to see work that you spent a lot of time and effort on get vandalized as such On Mon, Dec 9, 2013 at 7:49 AM, Mike N nice...@att.net wrote: On 12/9/2013 12:42 AM, James Mast wrote: So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. Disclaimer: I'm not familiar with DOT classifications in general. At first, the user seemed to be knowledgeable about highway classifications for the segments in question. But I agree - now that nearly everything was just changed to primary, it seems to be both less useful and inconsistent with most of the rest of the US. It seems that the intent was to match some other map rendering or road classification which has fewer classification levels. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us -- Tim Huemmer Webmaster Owner RRPictureArchives.NET ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
Tim, I sent the user a message inside of OSM that did all of this changing of the state highways in SC to primary/trunk and haven't gotten a response back yet in over 24h. I'll be contacting the DWG later tonight (giving the guy another ~5 hours to respond before I e-mail the DWG) about this subject. So please don't try to do many more changes just in case they decide a mass revert of this users changesets is the best way to fix all of this. That way, there will not be any major conflicts when they try to do this if possible. -James Date: Tue, 10 Dec 2013 11:13:10 -0500 From: tim.huem...@gmail.com To: talk-us@openstreetmap.org Subject: Re: [Talk-us] South Carolina State Highways - primary overload I found this to be very annoying. I did a lot of work on the SC Highways some time back. I noticed that in a few counties most of the state highways were marked as primary. I reverted most of them back to secondary except for the ones that were truly trunk routes. Its frustrating to see work that you spent a lot of time and effort on get vandalized as such On Mon, Dec 9, 2013 at 7:49 AM, Mike N nice...@att.net wrote: On 12/9/2013 12:42 AM, James Mast wrote: So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. Disclaimer: I'm not familiar with DOT classifications in general. At first, the user seemed to be knowledgeable about highway classifications for the segments in question. But I agree - now that nearly everything was just changed to primary, it seems to be both less useful and inconsistent with most of the rest of the US. It seems that the intent was to match some other map rendering or road classification which has fewer classification levels. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us -- Tim Huemmer Webmaster Owner RRPictureArchives.NET ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
James, I think discussion can only be useful if and when we have a common understanding of what 'trunk', 'primary', 'secondary' etc. mean to us. I don't think we're anywhere close to that, looking at the various and partly mutually contradictory wiki pages on the topic: http://wiki.openstreetmap.org/wiki/United_States_Road_Classification http://wiki.openstreetmap.org/wiki/United_States_Roadway_Classification_Guidelines http://wiki.openstreetmap.org/wiki/United_States_roads_tagging http://wiki.openstreetmap.org/wiki/Highway:International_equivalence Some user observations / discussion has happened on the respective Talk pages, and I found some observations here: http://wiki.openstreetmap.org/wiki/User:NE2/classification_FAQ As long as we are not aligned on what constitutes the various OSM highway classes, we don't really have a good argument to make other than 'it looks too primary-heavy' and it will always be a back-and-forth based on gut feelings. You can't really have a discussion that way and expect it to reach a satisfying conclusion. I'm not saying it shouldn't be addressed. I am saying that if we are, we should carefully consider what has been said on the topic before so we don't repeat ourselves, and be prepared for a lengthy discussion. It would help if someone could take the time to collect and summarize what is currently on the wiki. Unfortunately I can't volunteer to do this right now. I will do my best to contribute to the discussion but my exposure to the U.S. main road system is limited. On Sun, Dec 8, 2013 at 9:42 PM, James Mast rickmastfa...@hotmail.com wrote: Is it just me, or are there way too many primary state highways when some of them should really be secondary instead? The US Highways should normally be the primary/trunk highways and only a few select State Highways should be primary or trunk. To be honest, it seems that 98% of all the State highways segments in SC are marked as primary right now. There is no way almost all of the State Highways in SC can be primary. Just look at almost any other state. None are overloaded with primaries. One of the major routes that sticks out to me is SC-64 near the Savannah River Site where it's marked as trunk going to the security gate [1]. Now, if the Savannah River Site didn't exist and the highway was still open to the public past that point, I wouldn't agrue the point of it being trunk or primary. But since that segment of state highway goes nowhere anymore after leaving US-278 going West, this would be a classic case of it having to be secondary, or maybe even being tertiary. So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. He also did some of this in Georgia, but not to the extent as in South Carolina. Unfortunately, this user did it over 200+ changesets, so, if reverting was the option, it would take forever I would think. -James [1] - http://www.openstreetmap.org/#map=14/33.2388/-81.4205layers=N ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us -- Martijn van Exel President, US Chapter OpenStreetMap http://openstreetmap.us/ http://osm.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
I think the reason why things like this happen is because the highway tagging scheme in OSM was modeled off of UK's road-classification system and really isn't compatible with the road-classification system in the US. When I was new here three years ago, I found it kind of odd that there wasn't a way to distinguish state highways from other arterials. Perhaps this user feels like all state highways should be tagged as primary to distinguish them from other roads. That's kind of how I felt when I first joined OSM, but I didn't go around unilaterally changing all of the state highways in Washington to primary. However, I cannot explain why that one road you mentioned is marked as trunk. On Sun, Dec 8, 2013 at 9:42 PM, James Mast rickmastfa...@hotmail.comwrote: Is it just me, or are there way too many primary state highways when some of them should really be secondary instead? The US Highways should normally be the primary/trunk highways and only a few select State Highways should be primary or trunk. To be honest, it seems that 98% of all the State highways segments in SC are marked as primary right now. There is no way almost all of the State Highways in SC can be primary. Just look at almost any other state. None are overloaded with primaries. One of the major routes that sticks out to me is SC-64 near the Savannah River Site where it's marked as trunk going to the security gate [1]. Now, if the Savannah River Site didn't exist and the highway was still open to the public past that point, I wouldn't agrue the point of it being trunk or primary. But since that segment of state highway goes nowhere anymore after leaving US-278 going West, this would be a classic case of it having to be secondary, or maybe even being tertiary. So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. He also did some of this in Georgia, but not to the extent as in South Carolina. Unfortunately, this user did it over 200+ changesets, so, if reverting was the option, it would take forever I would think. -James [1] - http://www.openstreetmap.org/#map=14/33.2388/-81.4205layers=N ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
2013/12/9 James Mast rickmastfa...@hotmail.com There is no way almost all of the State Highways in SC can be primary. Just look at almost any other state. None are overloaded with primaries. +1, also there are almost no secondary highways which also seems strange. cheers, Martin ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
2013/12/9 Shawn K. Quinn skqu...@rushpost.com Even weirder: http://www.openstreetmap.org/#map=13/34.3071/-80.9977 is this stretch of SC 34 that goes primary-secondary-primary for no real reason I can see. +1, this one should probably be primary. cheers, Martin ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
On 12/9/2013 12:42 AM, James Mast wrote: So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. Disclaimer: I'm not familiar with DOT classifications in general. At first, the user seemed to be knowledgeable about highway classifications for the segments in question. But I agree - now that nearly everything was just changed to primary, it seems to be both less useful and inconsistent with most of the rest of the US. It seems that the intent was to match some other map rendering or road classification which has fewer classification levels. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] South Carolina State Highways - primary overload
Is it just me, or are there way too many primary state highways when some of them should really be secondary instead? The US Highways should normally be the primary/trunk highways and only a few select State Highways should be primary or trunk. To be honest, it seems that 98% of all the State highways segments in SC are marked as primary right now. There is no way almost all of the State Highways in SC can be primary. Just look at almost any other state. None are overloaded with primaries. One of the major routes that sticks out to me is SC-64 near the Savannah River Site where it's marked as trunk going to the security gate [1]. Now, if the Savannah River Site didn't exist and the highway was still open to the public past that point, I wouldn't agrue the point of it being trunk or primary. But since that segment of state highway goes nowhere anymore after leaving US-278 going West, this would be a classic case of it having to be secondary, or maybe even being tertiary. So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. He also did some of this in Georgia, but not to the extent as in South Carolina. Unfortunately, this user did it over 200+ changesets, so, if reverting was the option, it would take forever I would think. -James [1] - http://www.openstreetmap.org/#map=14/33.2388/-81.4205layers=N ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] South Carolina State Highways - primary overload
Oregon's suffering from this as well, I've just got too much on my plate to fix the Oregon situation. On Sun, Dec 8, 2013 at 11:42 PM, James Mast rickmastfa...@hotmail.comwrote: Is it just me, or are there way too many primary state highways when some of them should really be secondary instead? The US Highways should normally be the primary/trunk highways and only a few select State Highways should be primary or trunk. To be honest, it seems that 98% of all the State highways segments in SC are marked as primary right now. There is no way almost all of the State Highways in SC can be primary. Just look at almost any other state. None are overloaded with primaries. One of the major routes that sticks out to me is SC-64 near the Savannah River Site where it's marked as trunk going to the security gate [1]. Now, if the Savannah River Site didn't exist and the highway was still open to the public past that point, I wouldn't agrue the point of it being trunk or primary. But since that segment of state highway goes nowhere anymore after leaving US-278 going West, this would be a classic case of it having to be secondary, or maybe even being tertiary. So, does anybody else agree with me on this subject of primary overload in South Carolina? If so, how do we go about fixing this with a reasonable approach? Looking at some of the history of some of the ways, it seems that only one user was doing the upgrade from secondary to primary/trunk over the past 4+ months. He also did some of this in Georgia, but not to the extent as in South Carolina. Unfortunately, this user did it over 200+ changesets, so, if reverting was the option, it would take forever I would think. -James [1] - http://www.openstreetmap.org/#map=14/33.2388/-81.4205layers=N ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
