Re: [Talk-us] USA Rail: Calling all OSM railfans! (especially in California)
Keep me updated from Washington State. I work for a Railroad. Nathan P email: natf...@gmail.com On Sun, Mar 29, 2015 at 5:08 PM, Russ Nelson nel...@crynwr.com wrote: stevea writes: I have run into devotees of old_railway_operator=* and respect the tag by leaving it be where I encounter it, though I don't go out of my way to add it unless I have absolute positive knowledge of it (rarely to never). Yeah, it's an NE2 thing which he added automatically by changing the name of abandoned railroads to old_railway_operator. He's technically correct because the branch of a railroad, the name it goes by, is often not the name of the company who operated it. The line that goes south of Lake Ontario in NY was called the Hojack, but was operated by New York Central. It would be nice if map renderers, when presented with an abandoned railroad that has no name, rather than follow the USGS practice of saying Abandoned Railroad Bed, would look for name= first, old_railway_operator= second, and only if those two are absent, rendered the railway as a dotted line labeled Abandoned Railroad Bed just like the USGS does. In California, rail is approximately early alpha. For the USA as a whole, I'd say rail is even before that, in an early development phase. New York rail is 99% done. I say 97% because I need to hit some railroad yards in Buffalo still. -- --my blog is athttp://blog.russnelson.com Crynwr supports open source software 521 Pleasant Valley Rd. | +1 315-600-8815 Potsdam, NY 13676-3213 | Sheepdog ___ 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] USA Rail: Calling all OSM railfans! (especially in California)
stevea writes: I have run into devotees of old_railway_operator=* and respect the tag by leaving it be where I encounter it, though I don't go out of my way to add it unless I have absolute positive knowledge of it (rarely to never). Yeah, it's an NE2 thing which he added automatically by changing the name of abandoned railroads to old_railway_operator. He's technically correct because the branch of a railroad, the name it goes by, is often not the name of the company who operated it. The line that goes south of Lake Ontario in NY was called the Hojack, but was operated by New York Central. It would be nice if map renderers, when presented with an abandoned railroad that has no name, rather than follow the USGS practice of saying Abandoned Railroad Bed, would look for name= first, old_railway_operator= second, and only if those two are absent, rendered the railway as a dotted line labeled Abandoned Railroad Bed just like the USGS does. In California, rail is approximately early alpha. For the USA as a whole, I'd say rail is even before that, in an early development phase. New York rail is 99% done. I say 97% because I need to hit some railroad yards in Buffalo still. -- --my blog is athttp://blog.russnelson.com Crynwr supports open source software 521 Pleasant Valley Rd. | +1 315-600-8815 Potsdam, NY 13676-3213 | Sheepdog ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tesla Supercharger import
On Sat, Mar 28, 2015 at 11:40 PM, Charles Samuels o...@charles.derkarl.org wrote: I am not subscribed to imports, please CC me directly. To engage in the process fully, you'll need to subscribe. I have not yet asked Tesla Motors for their permission, I have a hard time believing it'd be refused. Let us know when that process is complete. My software is capable of recurring up-to-datenings based on a new tag: tesla:ref Experience among the other up-to-datenings used with OSM is that a single conflation key is not enough. You'll need a proximity search as well: fortunately easy in your case as these stations almost by definition are not close to each other. You'll also want to read up on import procedure for OSM. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Tesla Supercharger import
I am not subscribed to imports, please CC me directly. I now have the software and the data to do a complete import of every global Tesla Supercharger station. My software is capable of recurring up-to-datenings based on a new tag: tesla:ref which is based on the name Tesla uses in their Javascript on this page: http://www.teslamotors.com/en_GB/findus . In the page source, search for nid and it's the big long JSON dump. I parse that and merge it with an OSM file I extract with Overpass Turbo. I have already taken the liberty of manually identifying the tesla:ref for nodes in North America and the UK. I have missed a few, though, such as Node 3225936795 because it doesn't have an operator tag which is how I've been searching for the nodes so far. Right now, if a tag doesn't match with what Tesla publishes on their web site, I overwrite OSM's. I have not yet asked Tesla Motors for their permission, I have a hard time believing it'd be refused. This is what the imported node looks like when there's nothing in OSM already: node version='1' id='-61' lat='36.254143' lon='-120.237920' tag k='amenity' v='charging_station' / tag k='operator' v='Tesla Motors Inc.' / tag k='capacity' v='6' / tag k='socket:tesla_supercharger' v='6' / tag k='name' v='Tesla Supercharger Harris Ranch' / tag k='addr:city' v='Coalinga' / tag k='tesla:ref' v='harrisranchsupercharger' / tag k='opening_hours' v='24/7' / /node This is what the imported node looks like when merged with a present node: node version='5' id='2327799782' lat='37.024450' lon='-121.565350' tag k='website' v='http://www.teslamotors.com/supercharger/Gilroy' / tag k='operator' v='Tesla Motors Inc.' / tag k='tesla:ref' v='gilroysupercharger' / tag k='opening_hours' v='24/7' / tag k='name' v='Tesla Supercharger Gilroy' / tag k='car' v='yes' / tag k='bicycle' v='no' / tag k='amenity' v='charging_station' / tag k='capacity' v='10' / tag k='addr:state' v='CA' / tag k='addr:postcode' v='95020' / tag k='addr:housenumber' v='681' / tag k='addr:city' v='Gilroy' / tag k='socket:tesla_supercharger' v='10' / tag k='addr:street' v='Leavesley Road' / tag k='access' v='customers' / /node I am not subscribed to imports, please CC me directly. Charles Santa Cruz County, CA, USA ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tesla Supercharger import
On Saturday, March 28, 2015 11:49:05 PM Bryce Nesbitt wrote: On Sat, Mar 28, 2015 at 11:40 PM, Charles Samuels o...@charles.derkarl.org wrote: I am not subscribed to imports, please CC me directly. To engage in the process fully, you'll need to subscribe. Ok, I will once I get Tesla's permission, and I'll try again there. I have not yet asked Tesla Motors for their permission, I have a hard time believing it'd be refused. Let us know when that process is complete. I'll ask them for their permission. My software is capable of recurring up-to-datenings based on a new tag: tesla:ref Experience among the other up-to-datenings used with OSM is that a single conflation key is not enough. You'll need a proximity search as well: fortunately easy in your case as these stations almost by definition are not close to each other. I just added this feature, which I should've thought of earlier because now I don't need to manually merge stations. You'll also want to read up on import procedure for OSM. Doing so now... Thanks, Charles ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tesla Supercharger import
On Sat, Mar 28, 2015 at 11:40 PM, Charles Samuels o...@charles.derkarl.org wrote: I now have the software and the data to do a complete import of every global Tesla Supercharger station. node version='5' id='2327799782' lat='37.024450' lon='-121.565350' tag k='website' v='http://www.teslamotors.com/supercharger/Gilroy' / tag k='operator' v='Tesla Motors Inc.' / tag k='tesla:ref' v='gilroysupercharger' / tag k='opening_hours' v='24/7' / tag k='name' v='Tesla Supercharger Gilroy' / tag k='car' v='yes' / tag k='bicycle' v='no' / tag k='amenity' v='charging_station' / tag k='capacity' v='10' / tag k='addr:state' v='CA' / tag k='addr:postcode' v='95020' / tag k='addr:housenumber' v='681' / tag k='addr:city' v='Gilroy' / tag k='socket:tesla_supercharger' v='10' / tag k='addr:street' v='Leavesley Road' / tag k='access' v='customers' / /node I surveyed this node. http://www.openstreetmap.org/node/2776570644 I see nothing wrong with what you have done. You've built upon what another mapper had already added. I was so disappointed that another mapper beat me to the punch. ;-) Being the slacker that I am, I have pictures of the Buckeye AZ site to update the wili page http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcharging_station. However, I have not added the pictures yet. The debate I've had with myself on mapping these nodes is one or many? Each Tesla charger takes up one parking space. Each charger has an individual reference node. Blink and SemaCharge also have a unique reference id per charger. In the case of Telsa, the address is actually on the actual 4x8 ish foot electrical walled off box. The node was already on the map and that you updated is near where the box is. In some respects all this does not matter, because a person driving a Tesla could find the location...well if it rendered. Perhaps the next step is to put in a bug report for the main OSM map. The challenge is to make a cute icon that would also take into other kinds of chargers in the rest of the world. I took notice of what Telsa is trying to accomplish. The electronic car is just a toy of the urban environment and is not practical as a regular vehicle until Tesla came along. Part of the charging station map almost looks like the history US route 66. It looks like you can almost make it across America now. http://www.teslamotors.com/findus#/bounds/35.5722872795,-107.2834384999,31.259882347870708,-117.8303134999?search=superchargername=usplace=buckeyesupercharger You still may want to bring along a Swiss Army knife set of adapters just to make sure that you don't get stranded. http://shop.teslamotors.com/collections/model-s-charging-adapters Regards, Greg ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tesla Supercharger import
On Sun, Mar 29, 2015 at 8:05 AM, Charles Samuels o...@charles.derkarl.org wrote: I'll ask them for their permission. While you ask them for permission, you might want to suggest that they switch to OSM instead of using google [1] maps. I think they use google maps in their navigation system but it wouldn't hurt to them thinking. [1] http://www.teslamotors.com/findus#/bounds/35.5722872795,-107.2834384999,31.259882347870708,-117.8303134999?search=superchargername=us -- @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
Re: [Talk-us] Tesla Supercharger import
Hi Charles, tag k='capacity' v='6' / tag k='socket:tesla_supercharger' v='6' / tag k='name' v='Tesla Supercharger Harris Ranch' / tag k='addr:city' v='Coalinga' / tag k='tesla:ref' v='harrisranchsupercharger' / This telsa:ref tag seem weird, should probably be just ref, or ref:telsa if the value is a db key. However, given the stations have names + location, it is not needed to keep the data updated. Consider dropping it. You need to get permission. They might not want to encourage the data being duplicated in OSM. Please review the import policy, you need to setup an OSM wiki page documenting the import. Also, it would be a good idea to be on the import list. Thanks Jason ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
