Re: [Talk-us] Talk-us Digest, Vol 130, Issue 17
SteveA, The authoritative source for railroad GIS data is usually considered to be BTS: https://www.bts.gov/ When I worked at BNSF, that is what was used to initially populate the linework for our rail feature class. Class I railroads (the very large ones) are generally regulated by the Federal Railroad Administration. PUC is for telecom, electric and gas. Jay On Thu, Sep 13, 2018 at 8:05 AM wrote: > Send Talk-us mailing list submissions to > talk-us@openstreetmap.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstreetmap.org/listinfo/talk-us > or, via email, send a message with subject or body 'help' to > talk-us-requ...@openstreetmap.org > > You can reach the person managing the list at > talk-us-ow...@openstreetmap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk-us digest..." > > > Today's Topics: > >1. Re: USPS Post Boxes (EthnicFood IsGreat) >2. Re: Denver RTD's public_transport growth (OSM Volunteer stevea) > > > -- > > Message: 1 > Date: Wed, 12 Sep 2018 18:29:23 -0400 > From: EthnicFood IsGreat > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] USPS Post Boxes > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Date: Wed, 12 Sep 2018 14:25:15 -0700 > > From: Peter Dobratz > > To: bhou...@gmail.com > > Cc: "talk-us@openstreetmap.org Openstreetmap" > > , 354...@gmail.com > > Subject: Re: [Talk-us] USPS Post Boxes > > > > It would be good to standardize on operator tags for the 4 major carriers > > as you mentioned. The logos for DHL, FedEx, and UPS have those exact > > letters in them, so if people map what they see, then they will end up > with > > those exact values. However, as mentioned, the USPS logo actually > contains > > the text United States Postal Service. > > > > I could be convinced to switch my tagging from United States Postal > Service > > to USPS. Are there any arguments to support the short form beyond it > being > > easier to type? > > [...] > > I would like to point out there are free, little utilities like > Typertask that will quickly expand a few keystrokes into many more > letters. This can greatly speed up typing long strings like "United > States Postal Service". > > Mark > > > > -- > > Message: 2 > Date: Wed, 12 Sep 2018 16:49:58 -0700 > From: OSM Volunteer stevea > To: talk-us > Subject: Re: [Talk-us] Denver RTD's public_transport growth > Message-ID: <3f4ca4b1-673d-4035-b268-122ee2c9b...@softworkers.com> > Content-Type: text/plain; charset=us-ascii > > On Sep 2, 2018, at 9:52 PM, OSM Volunteer stevea < > stevea...@softworkers.com> wrote: > > > > I "found something rectangular" and sketched in > http://wiki.osm.org/wiki/Colorado/Railroads which we might agree (as a > useful, communicative wiki) is "alpha-1" or so. > > Following up to my own post, (that wiki continues as "early alpha"), two > important tasks emerge: > > 1) Denver RTD's University of Colorado A Line (train) needs nodes/ways > added to OSM, tagged public_transport=platform to grow the route from > public_transport:version=1 to v2. Seeing this is a pretty > heavily-travelled passenger=suburban route=train, this shouldn't be too > difficult, and > > 2) TIGER Review of existing mainline freight rail (primarily mainline > BNSF routes Colorado Springs, Pikes Peak, Spanish Peaks and Walsenburg > Subdivisions) will need some additional authoritative data sources > (Colorado PUC?) to "untangle" them from UP lines: they have blurred so > much and are have gotten so confused that the original TIGER data are > virtually incomprehensible as they exist in OSM at present. > > Of course, keeping the wiki synced with the data in OSM is the whole > point. Then we go beta and eventually Colorado/Railroads become "a pretty > darn good set of statewide rail data, well-documented." One state at a > time, OSM rail data (from decade-old hoary TIGER data) do measurably and > demonstrably improve. > > Thanks, especially to Colorado OSMers/rail enthusiasts who have responded > so far, > > SteveA > California > > > -- > > Subject: Digest Footer > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > > > -- > > End of Talk-us Digest, Vol 130, Issue 17 > > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Talk-us Digest, Vol 130, Issue 8
Here are the North Carolina nuclear evacuation routes. https://www.ncdot.gov/travel-maps/maps/Pages/evacuation-routes.aspx The hurricane routes are here: https://www.ncdot.gov/travel-maps/maps/Documents/coastal-evacuation-routes.pdf On Thu, Sep 6, 2018 at 8:03 AM wrote: > Send Talk-us mailing list submissions to > talk-us@openstreetmap.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstreetmap.org/listinfo/talk-us > or, via email, send a message with subject or body 'help' to > talk-us-requ...@openstreetmap.org > > You can reach the person managing the list at > talk-us-ow...@openstreetmap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk-us digest..." > > > Today's Topics: > >1. Re: Evacuation Routes (Rihards) > > > -- > > Message: 1 > Date: Thu, 6 Sep 2018 13:38:35 +0300 > From: Rihards > To: "talk-us@openstreetmap.org" > Subject: Re: [Talk-us] Evacuation Routes > Message-ID: > Content-Type: text/plain; charset=utf-8 > > On 2018.09.06. 02:06, Eric H. Christensen wrote: > > I recently finished an update to the evacuation routes feature[0], > turning it into a relation (route). I'll be working on adding hurricane > evacuation routes to areas I'm familiar with (Maryland, Hampton Roads area > of Virginia, and Northeast North Carolina) but I encourage others to add > evacuation routes to their local areas as well. > > That page says "Cycle routes or bicycle route are named or numbered or > otherwise signed routes. May go along roads, trails or dedicated cycle > paths." > > Is that correct? > > > Currently, JOSM doesn't recognize this route type and I don't think > they're being rendered on any third-party software but I'm hoping once > enough data is in the system we'll be able to show a reason for rendering > such information. > > > > Thanks, > > Sparks > > > > [0] https://wiki.openstreetmap.org/wiki/Tag:route%3Devacuation > -- > Rihards > > > > -- > > Subject: Digest Footer > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > > > -- > > End of Talk-us Digest, Vol 130, Issue 8 > *** > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Talk-us Digest, Vol 130, Issue 3
How may I reformat a SD card or microSD card as described above? How can I check my card? On Mon, Sep 3, 2018 at 12:54 AM wrote: > Send Talk-us mailing list submissions to > talk-us@openstreetmap.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstreetmap.org/listinfo/talk-us > or, via email, send a message with subject or body 'help' to > talk-us-requ...@openstreetmap.org > > You can reach the person managing the list at > talk-us-ow...@openstreetmap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk-us digest..." > > > Today's Topics: > >1. Whole-US Garmin Map update - 2018-08-31 (Dave Hansen) >2. Re: Naming numbered roads as "State Route X", "Interstate X", > etc. (Nathan Mills) >3. Re: Naming numbered roads as "State Route X", "Interstate X", > etc. (Kevin Kenny) >4. Re: Naming numbered roads as "State Route X", "Interstate X", > etc. (Paul Johnson) >5. Denver RTD's public_transport growth (OSM Volunteer stevea) > > > -- > > Message: 1 > Date: Sun, 02 Sep 2018 14:34:59 + > From: Dave Hansen > To: , > Subject: [Talk-us] Whole-US Garmin Map update - 2018-08-31 > Message-ID: > > These are based off of Lambertus's work here: > > http://garmin.openstreetmap.nl > > If you have questions or comments about these maps, please feel > free to ask. However, please do not send me private mail. The > odds are, someone else will have the same questions, and by > asking on the talk-us@ list, others can benefit. > > Downloads: > > http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-08-31 > > Map to visualize what each file contains: > > > http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-08-31/kml/kml.html > > > FAQ > > > > Why did you do this? > > I wrote scripts to joined them myself to lessen the impact > of doing a large join on Lambertus's server. I've also > cut them in large longitude swaths that should fit conveniently > on removable media. > > http://daveh.dev.openstreetmap.org/garmin/Lambertus/2018-08-31 > > Can or should I seed the torrents? > > Yes!! If you use the .torrent files, please seed. That web > server is in the UK, and it helps to have some peers on this > side of the Atlantic. > > Why is my map missing small rectangular areas? > > There have been some missing tiles from Lambertus's map (the > red rectangles), I don't see any at the moment, so you may > want to update if you had issues with the last set. > > Why can I not copy the large files to my new SD card? > > If you buy a new card (especially SDHC), some are FAT16 from > the factory. I had to reformat it to let me create a >2GB > file. > > Does your map cover Mexico/Canada? > > Yes!! I have, for the purposes of this map, annexed Ontario > in to the USA. Some areas of North America that are close > to the US also just happen to get pulled in to these maps. > This might not happen forever, and if you would like your > non-US area to get included, let me know. > > -- Dave > > > > > -- > > Message: 2 > Date: Sun, 02 Sep 2018 16:16:43 -0400 > From: Nathan Mills > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Naming numbered roads as "State Route X", > "Interstate X", etc. > Message-ID: <80a31c08-0990-446f-aa49-172fc3d87...@nwacg.net> > Content-Type: text/plain; charset="utf-8" > > The New Sapulpa Road situation is in practice a road with a secondary > name. Just like Flagler Street in part of Miami (FL, not OK) is defined by > the state legislature as being "Natan A Rok Boulevard" (or similar, working > from memory here). > > My personal opinion is that if local practice and the USPS continue to use > the old name, that name should stay in the name tag, while the > Legislature's political name should be tagged as an alt_name. That said, > there are situations in which most/all signage refers to the new name, in > which case switching them makes sense. (Martin Luther King Jr. Boulevard in > Fayetteville, AR being an example. Most still call it 6th Street, but the > city, nearly all signage, and the USPS' preferred name are all "Martin > Luther King Jr Boulevard," and they are going to keep it up until everyone > gets with the program) > > Sometimes, the name really is "Highway 66" or "Route 22." Admittedly, it > can sometimes be hard to tell for sure without local knowledge. As long as > people do their best and aren't dogmatic about it when someone who knows > better comes along in the future it will all work out in the end. > > -Nathan > > On September 1, 2018 5:28:11 PM EDT, Paul Johnson > wrote: > >On Sat, Sep 1, 2018 at 12:01 PM Peter Dobratz wrote: > > > >To
Re: [Talk-us] Talk-us Digest, Vol 129, Issue 35
Where were the buildings from? I am in Raleigh and can help. On Thu, Aug 30, 2018 at 8:02 AM wrote: > Send Talk-us mailing list submissions to > talk-us@openstreetmap.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstreetmap.org/listinfo/talk-us > or, via email, send a message with subject or body 'help' to > talk-us-requ...@openstreetmap.org > > You can reach the person managing the list at > talk-us-ow...@openstreetmap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk-us digest..." > > > Today's Topics: > >1. Re: buggy buildings in Maryland (Ben Discoe) > > > -- > > Message: 1 > Date: Wed, 29 Aug 2018 17:38:52 -0700 > From: Ben Discoe > To: Open Street Map Talk-US > Subject: Re: [Talk-us] buggy buildings in Maryland > Message-ID: > tehhdmrel-heo_zcrt9oevhny-n0k...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > +1 to Elliot Plack's proposal to use Simplify to remove the redundant > nodes from the poor quality imported buildings. > > In fact, I did this myself for another massive import: User "jumbanho" > imported buildings for the large city of Raleigh, NC back in January > 2010. > There were lots of degenerate nodes, which I cleaned up in batches > using JOSM's simplify. I did most of the cleanup in 2015. > > -Ben > On Mon, Aug 20, 2018 at 5:30 AM Elliott Plack > wrote: > > > > Here's a potential fix: use the SimplifyArea JOSM Plugin. > https://wiki.openstreetmap.org/wiki/JOSM/Plugins/SimplifyArea > > > > The plugin is built for fixing over-noded and buggy imports. > > > > As a test, I downloaded the plugin and then downloaded some of Annapolis > sailor's buildings. > > > > This building should only contain four nodes: > https://www.openstreetmap.org/way/525751797 > > > > This building should only contain eight nodes: > https://www.openstreetmap.org/way/526209538 > > > > The plugin successfully reduced the nodes for both buildings without > affecting the shape, unlike the simplify way tool. > > > > I tested it on a larger swath of 500 buildings and it took less than a > second to run. > > > > I haven't uploaded any of the changes yet, but I think this would be a > good path forward. > > > > On Thu, Aug 16, 2018 at 8:02 PM Frederik Ramm > wrote: > >> > >> Hi, > >> > >> On 08/16/2018 08:08 PM, Elliott Plack wrote: > >> > I'd say go ahead and remove the extraneous nodes > >> > >> This has now been done. > >> > >> > and also any buildings > >> > that are either version 0 or do not have any new tags (like names or > >> > addresses) > >> > >> It appears that of the 177,151 buildings still there, only 29,513 have > >> tags other than building=*. In most cases, these other tags are > >> addr:street and addr:housenumber. > >> > >> I'll let this rest for a bit to give others a chance to chime in. > >> > >> 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 > > > > -- > > Elliott Plack > > http://elliottplack.me > > ___ > > Talk-us mailing list > > Talk-us@openstreetmap.org > > https://lists.openstreetmap.org/listinfo/talk-us > > > > -- > > Subject: Digest Footer > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > > > -- > > End of Talk-us Digest, Vol 129, Issue 35 > > ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Talk-us Digest, Vol 129, Issue 33
The power squadrons are racing boats. That is not a government agency. Few people are going to mix up NASCAR and USPS, and I think the same thing applies here. Powerboats are not in a fixed location. Get Outlook for Android On Tue, Aug 28, 2018 at 8:03 PM -0400, wrote: Send Talk-us mailing list submissions to talk-us@openstreetmap.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstreetmap.org/listinfo/talk-us or, via email, send a message with subject or body 'help' to talk-us-requ...@openstreetmap.org You can reach the person managing the list at talk-us-ow...@openstreetmap.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Talk-us digest..." Today's Topics: 1. USPS Post Boxes (Leif Rasmussen) 2. Re: USPS Post Boxes (Paul Johnson) 3. Re: USPS Post Boxes (Jmapb) 4. Re: USPS Post Boxes (Jack Burke) -- Message: 1 Date: Tue, 28 Aug 2018 15:31:32 -0400 From: Leif Rasmussen <354...@gmail.com> To: talk-us Subject: [Talk-us] USPS Post Boxes Message-ID: Content-Type: text/plain; charset="utf-8" Hi everyone, A couple of days ago, I noticed that different post boxes in the United States had different ways of tagging that they were part of the USPS system. Roughly 60% had "operator"="USPS", 40% "operator"="United States Postal Service", and about 15 similar to "operator"="United States Post Services" or "United States Post Office". I wanted to make them all the same, so I asked on the OSMUS Slack group about the tags, and most people supported "USPS". I then proceeded to upload a changeset manually converting 1500 "United States Postal Service" or similar to "USPS". I should have waited longer before uploading. https://www.openstreetmap.org/changeset/62020302 https://overpass-turbo.eu/s/Boq All post boxes in the USPS system now have "operator"="USPS". After uploading, people expressed concern about the choice of "USPS" over "United States Postal Service". The wiki states that abbreviations should be expanded, "USPS" could be confused with other agencies , and this counted as an automated edit, which should have had better planning with the OSM community. I would now like to propose converting all post boxes with the tag "operator"="USPS" to "operator"="United States Postal Service". I would also like to add the tag "operator:wikidata"="Q668687" to the post boxes that currently have "operator"="USPS". Please reply with any feedback or concerns you have with this proposal. Thank you, Leif Rasmussen OSM username: LeifRasmussen -- next part -- An HTML attachment was scrubbed... URL: -- Message: 2 Date: Tue, 28 Aug 2018 14:36:45 -0500 From: Paul Johnson To: Leif Rasmussen <354...@gmail.com> Cc: talk-us Subject: Re: [Talk-us] USPS Post Boxes Message-ID: Content-Type: text/plain; charset="utf-8" I fully support the expanded version, not the abbreviated version. On Tue, Aug 28, 2018, 14:32 Leif Rasmussen <354...@gmail.com> wrote: > Hi everyone, > A couple of days ago, I noticed that different post boxes in the United > States had different ways of tagging that they were part of the USPS > system. Roughly 60% had "operator"="USPS", 40% "operator"="United States > Postal Service", and about 15 similar to "operator"="United States Post > Services" or "United States Post Office". I wanted to make them all the > same, so I asked on the OSMUS Slack group about the tags, and most people > supported "USPS". I then proceeded to upload a changeset manually > converting 1500 "United States Postal Service" or similar to "USPS". I > should have waited longer before uploading. > https://www.openstreetmap.org/changeset/62020302 > https://overpass-turbo.eu/s/Boq > All post boxes in the USPS system now have "operator"="USPS". > After uploading, people expressed concern about the choice of "USPS" over > "United States Postal Service". The wiki states that abbreviations should > be expanded, "USPS" could be confused with other agencies > , and this > counted as an automated edit, which should have had better planning with > the OSM community. > I would now like to propose converting all post boxes with the tag > "operator"="USPS" to "operator"="United States Postal Service". I would > also like to add the tag "operator:wikidata"="Q668687" to the post boxes > that currently have "operator"="USPS". Please reply with any feedback or > concerns you have with this proposal. > Thank you, > Leif Rasmussen > OSM username: LeifRasmussen > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > -- next part -- An HTML attachment was scrubbed... URL: -- Message: 3 Date: Tue, 28 Aug 2018
