Re: [Talk-us] Dirt Roads (formerly: Abandoned railway)
Seeing as I already spend 70% of my time mapping unpaved roads in Colorado, and I've some opinions of my own about the subject, I'm happy to set up and run wiki pages etc bout the subject if people think that this would help Mark From: Clifford Snow To: stevea Cc: talk-us Sent: Tuesday, September 2, 2014 6:26 PM Subject: Re: [Talk-us] Dirt Roads (formerly: Abandoned railway) On Tue, Sep 2, 2014 at 9:52 AM, stevea wrote: I'd like to see (more) well-identified, well-prioritized, even-novices-can-do-this-if-they-want such projects emerge and be displayed in our wiki (or someplace) so that fired-up OSM volunteers itching to map can "shop along the shelf," pick out a sub-project that gives chew-and-digest satisfaction (whether it lasts a day, a week or a month) and results in that warm feeling of accomplishment (beautiful, high quality data as useful results) once done. Now, THAT'S a crowd-sourced mapping project! We're getting there, though in a low gear. Discussions like these, some identification, some organization, some inspiration, and we will rev it up faster. Elephants are best eaten one bite at a time. (A metaphor, not literal) +1 -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ 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 Valley Hwy/I-25
Just did a visual on http://www.openstreetmap.org/way/10386713 and it is indeed S Valley Highway From: "russdeff...@gmail.com" To: Frederik Ramm Cc: "talk-us@openstreetmap.org Openstreetmap" Sent: Thursday, January 16, 2014 6:23 PM Subject: Re: [Talk-us] South Valley Hwy/I-25 Will discuss at our winter editathon, thanks for making me aware - something this CO native (not to Denver though) did not know. > On Jan 16, 2014, at 1:25 PM, Frederik Ramm wrote: > > Hi, > > I have recevied a message about a potential problem with the naming > of I-25 in the Denver, CO area. The message goes: > >> Someone got super confused when doing the map in Colorado/Denver >> Area. We do not have an interstate called the South Valley Hwy. They >> confused a different super tiny street with Interstate 25. Please >> someone change it to reflect that I-25 is NOT South Valley Hwy. > > I don't want to make such a change myself because it looks like the I-25 > has been imported from TIGER where it was called South Valley Hwy > already, plus Wikipedia also says that "The cities of Denver [...] were > first to begin building multi-lane highway segments along the route of > what would eventually become Interstate 25. [...] Denver's segment was > originally known as the Valley Highway [...]". And the only other South > Valley Highway I can find, http://www.openstreetmap.org/way/10386713, > looks like it might in fact be Inverness Way. (DavidJDBA, are you > reading this?) > > Definitely something for the locals to brood about ;) > > 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___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] access restriction, water only: How to tag?
True, but the thread has not identified that it is indeed on an island. If it is boat-only for that reason, then of course. If it is at a place where you could walk there legally, but that the conditions make it very dangerous to get there, then why not? From: Thomas Colson To: talk-us@openstreetmap.org Sent: Friday, July 26, 2013 5:57 AM Subject: Re: [Talk-us] access restriction, water only: How to tag? Yes. If a campsite is on a lake shore, or an island, and the only way to get there is by boat, I don’t see how sac_scale depicts that information. From:Mark Newnham [mailto:m...@newnhams.com] Sent: Friday, July 26, 2013 7:46 AM To: Open Street Map Talk-US Subject: Re: [Talk-us] access restriction, water only: How to tag? Is there something about sac_scale=* that doesn't work here? From:Mike Thompson To: Thomas Colson Cc: Open Street Map Talk-US Sent: Thursday, July 25, 2013 9:25 PM Subject: Re: [Talk-us] access restriction, water only: How to tag? > By foot, impossible and serious injury if attempted. What is the specific thing that makes it dangerous? A cliff? swamp? dense undergrowth? Perhaps a landuse tag or natural=cliff would be appropriate? Agree with Richard that access= is about legal restrictions not about danger or practicality. Mike ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] JuicyTrails Map and App based on OSM data released
Just downloaded it onto a Samsung Galaxy 2. 1. when the phone goes to sleep, as soon as it wakes up, the position of the map reverts back to the current position. If I'm using the phone to review where I'm going to walk before I get to the start point, this is really annoying. Suggest that: a. This is the default behavior when the app is recording a trace. b. Maybe it could be user definable when not recording? 2. No search by town name. If reviewing the map prior to walking, I have to drag the map across a distance. On the phone, again, really annoying. In addition, at a zoom level high enough to make scrolling easier, the text of the town names is to small to read. I'm pretty sure at least one competitor product allows a settable minimum text size From: derrick nehrenberg To: talk-us@openstreetmap.org Sent: Thursday, July 25, 2013 7:55 PM Subject: [Talk-us] JuicyTrails Map and App based on OSM data released Hi OSM folks, I posted my GPS tracking and trail map app to the Google Play store today. I am writing because I am interested in getting some early feedback from the OSM community, especially regarding feature requests or improvements to the map, website, and app. It would also be great to hear thoughts about how juicytrails can facilitate trail mapping. Here is the Google Play app store link https://play.google.com/store/apps/details?id=com.juicytrails.juicytrailsfree&hl=en If people like it, it would be nice to get some good reviews going... The trail map features all kinds of dirt trails (hiking, horse, bicycle, motorcycle, ATV, and 4WD) as well as paved footways and cycleways, all based on OSM data. I started this project basically to fulfill my own trail navigation needs. I have done quite a bit of OSM trail mapping myself, but even I was shocked how many trails appeared when we turned the rendering lights on in the USA. Denver, Boston, and California have the most mapped trails. I have mapped quite a bit in Moab, Utah, Fruita, Durango, Crested Butte, and Salida Colorado. Here is our burgeoning website and map. http://juicytrails.com/ A central goal of this project is to turn hardcopy trail maps into trail dollars. We have actually already been doing this part of the project for a couple years. We are working with a growing list of trail associations to get their trails on OSM and juicytrails.com and then subsequently on hardcopy maps which we will sell directly to trail associations for a very, very small production fee of $.50 per map. The trail associations then sell directly to retailers for $1.50 each, and then the retailers sell for $2.99 each, clearing $1.00 minimum per map. The hardcopy maps have download codes used for installing offline versions of the maps into the Free Juicytrails App. These maps have been a minor hit, and have sold extremely well in some locations. Thanks for reading. derrick nehrenberg ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] access restriction, water only: How to tag?
Is there something about sac_scale=* that doesn't work here? From: Mike Thompson To: Thomas Colson Cc: Open Street Map Talk-US Sent: Thursday, July 25, 2013 9:25 PM Subject: Re: [Talk-us] access restriction, water only: How to tag? > By foot, impossible and serious injury if attempted. What is the specific thing that makes it dangerous? A cliff? swamp? dense undergrowth? Perhaps a landuse tag or natural=cliff would be appropriate? Agree with Richard that access= is about legal restrictions not about danger or practicality. Mike ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] what do we mean by geocoding?
I work in the Uitilities/Billing industry and do a reasonable amount of work in addressing quality (in order to get lower USPS rates with things like the Intelligent Mail Barcoder and suchlike). I'd just like to throw a couple of things in to enhance the discussion. 1. In 90% of cases in the US, The physical address (which can be found using a reverse geocode) is the Postal Address. Obvious areas of difference are: a. PO Boxes b. Rural Areas where there is no mail delivery. But in this case, the Physical address can be found using a reverse geocode. 2. In an earlier part of the thread, someone mentioned PO Boxes. These are Mailing Addresses not physical addresss. The distinction is important. 3. Importantly - a. Both Google and Openstreetmap don't know anything about actual addresses in the US. For reverse geocode purposes, they just guess based on the approximate lat/long location. b. An easy example to show you is this - A search for "6188 South Poplar St, Centennial. CO" in both google and openstreetmap will both return results - Google will even give you a Streetview. But that property simply doesn't exist. It never has/ c. If you go to USPS, https://tools.usps.com/go/POLocatorAction.action they know that it doesn't exist. This is the address quality that USPS supplies. USPS provides an easy to understand, comprehensive addressing method that would allow OSM to provide a consistent addressing methodology to addresses. For example, An armchair mapper might map an address like North Caley as North Caley, Nort Caley NTH Caley or N Caley. (These are the most common ways by the way for manually entered addresses). The only reverse 911 addresses I have provided are validated USPS addresses. If the USPS standard was applied to addressing (and it is a standard that everyone in the US knows and understands) then OSM would be gain a leap in addressing quality. In fact, I would imagine that 75% of the work could be done by Bots There are plenty of tools that the USPS supplies to enhance address quality. https://www.usps.com/business/manage-address-quality.htm Hope this helps the discussion Mark From: Bryce Nesbitt To: talk-us@openstreetmap.org Sent: Saturday, June 22, 2013 4:05 PM Subject: Re: [Talk-us] what do we mean by geocoding? On Fri, Jun 21, 2013 at 6:47 PM, Richard Welty wrote: Surveying postal addresses by opening mailboxes (illegal) or knocking on doors doesn't seem feasible. >> >> but the enhanced 911 addresses are basically the same as the postal >addresses and have the potential to become available. i'm working on >that in my part of upstate NY. e911 is a very hopeful source for OSM: high quality coding would be huge. For good background, read: http://en.wikipedia.org/wiki/Enhanced_9-1-1#Wireline_enhanced_911 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Neighborhoods / Zillow
I'm interested in this, I recently posted a question on how to map subdivisions, I'm using landuse=residential,name=Name of Subdivision to map mine. I think it's important that for US purposes, we can distinguish between HOA managed subdivisions, which are defined as a legal entity, and all other types of indicators (hamlet, neighborhood etc). My city, (Centennial, Colorado) which is quite new, has no areas that are 'neighbourhoods', all residential areas are either subdivisions or are are defined as just a city address (for those that have no HOA. There is no naming 'creep' as someone raised in this thread. Mark From: Martijn van Exel To: Russell Deffner Cc: OSM US Talk Sent: Tuesday, June 11, 2013 1:56 PM Subject: Re: [Talk-us] Neighborhoods / Zillow Russ -- Yes, MR2 will have the ability to work on a specific location (likely to be specified as a point + radius, or bbox). What do you mean by correlating place values, correlating with what? Rural areas are not as important for neighborhood coverage I would say. On Tue, Jun 11, 2013 at 1:37 PM, Russell Deffner wrote: I think this is a good idea but have some suggested considerations. > >If I remember correctly, MapRoulette 2 has the ability to localize the >challenge, correct? If/when is that available I think that would be a great >challenge, just a simple “verify this is the proper neighborhood name and >appropriate value”. However, I have not seen a real good reference for >correlating the place values in the US (although I haven’t looked); does >someone know of one? or maybe a good first step is to try and create one. >Also I don’t think this will get us anywhere near complete as we get into >rural areas we don’t know and that don’t have local mappers (and those using >MR), so we may need to further do some sort of ‘challenge’ (that may not work >with MR) to ‘import’/cross-reference another data set. > >=Russ >russdeffner on OSM > >From:Martijn van Exel [mailto:m...@rtijn.org] >Sent: Tuesday, June 11, 2013 12:58 PM >To: OSM US Talk >Subject: [Talk-us] Neighborhoods / Zillow > >Hiya, > >OSM has pretty poor neighborhood coverage in the US. We have around 1100 >place=neighbo[u]rhood. Geonames has ten times that at 11,000 (feature class >P.PPLX - not sure if all of those are neighborhoods) and Zillow has 7,000. >Both these data sets are provided under (different) CC licenses. Could we use >either Geonames or Zillow to drive improvement to neighborhood name coverage >in OSM? I am not proposing an import, but a local MapRoulette challenge might >work where people with local knowledge accept / reject proposed neighborhood >points, or something along those lines. > >Martijn >-- >Martijn van Exel >http://oegeo.wordpress.com/ >http://openstreetmap.us/ -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Guidance on road designation
I would tend to agree. They're definitely not secondary routes, Its really a question of whether something else (minor?) might be more appropriate despite their size, From: Richard Welty To: talk-us@openstreetmap.org Sent: Sunday, June 2, 2013 5:03 PM Subject: Re: [Talk-us] Guidance on road designation On 6/2/13 6:55 PM, Mark Newnham wrote: > I'm looking for some guidance on road designation. I have a sample of the > area here http://www.openstreetmap.org/?lat=39.59736&lon=-104.89872&zoom=17. > > My difficulty is with the size of the roads vs their utility. Having scanned > the mailing lists and the wiki, I have tended to designate them tertiary, but > am happy to change them. > > As background, this area is the edge of the Denver Technology Center, south > of Denver, but this question applies to the whole area, and in fact most > modern build on the Front Range of the Rocky Mountains. > > First example, Running East/West is East Peakview Avenue. This is a typical > example of a divided highway in the DTC. The road is wide (approx 12ft per > carriageway, 2 lanes in each direction, center divider approx 3feet wide, > plus 3rd lane when left turns are available) > Second example, Running North/South is South Syracuse Way which is not a > divided highway. The lanes are again 12ft Wide, 2 in each direction plus an > additional 12 ft in the center for left turns. > > Whilst the roads are designed to take huge volumes of traffic, outside of > peak hours they probably carry 300-400 vehicles per hour and 100 vehicles per > hour or less on the weekend. The roads don't go anywhere and never will. > > What would be the best mechanism for designation? > i'd say that anything serving as an undivided collector (one step up from a residential/unclassified) is good as tertiary. a case can be made that you might upgrade the streets that are 2 lanes each way to secondary, but that is really a local judgement call. typically there's a bit of hash of functional vs actual traffic load vs physical configuration, it's not actually terribly well defined. as i zoom out, i see that a bunch of these, while 4 lanes, are relatively short. that suggests that maybe they shouldn't be upgraded, they're not through routes. you're local, what do you think? richard ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Guidance on road designation
I'm looking for some guidance on road designation. I have a sample of the area here http://www.openstreetmap.org/?lat=39.59736&lon=-104.89872&zoom=17. My difficulty is with the size of the roads vs their utility. Having scanned the mailing lists and the wiki, I have tended to designate them tertiary, but am happy to change them. As background, this area is the edge of the Denver Technology Center, south of Denver, but this question applies to the whole area, and in fact most modern build on the Front Range of the Rocky Mountains. First example, Running East/West is East Peakview Avenue. This is a typical example of a divided highway in the DTC. The road is wide (approx 12ft per carriageway, 2 lanes in each direction, center divider approx 3feet wide, plus 3rd lane when left turns are available) Second example, Running North/South is South Syracuse Way which is not a divided highway. The lanes are again 12ft Wide, 2 in each direction plus an additional 12 ft in the center for left turns. Whilst the roads are designed to take huge volumes of traffic, outside of peak hours they probably carry 300-400 vehicles per hour and 100 vehicles per hour or less on the weekend. The roads don't go anywhere and never will. What would be the best mechanism for designation? TIA Mark___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
