Re: [Tagging] highspeed=yes
Hi Martin, Am 11.07.2017 um 01:27 schrieb Martin Koppenhoefer: >> On 10. Jul 2017, at 23:42, Michael Reichert wrote: >> >> The main question is: >> Shold the whole line (the definition of "line" is a different discussion >> worth) get highspeed=yes or only the parts which are suitable for high >> speeds due to large curve radius, special signalling and train >> protection etc.? What is your opinion? > > > What is a "line" in osm tags? > If you map a specific train connection (route=train) it would apply to the > whole thing, if you tag a piece of rail (route=railway or railway=rail) I > would only put it on those parts that are suitable for highspeed trains. Line in this context refers to all railway tracks between two stations except sidings, yards, spurs etc. (i.e. all tracks which would get usage=*). Best regards Michael -- Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten ausgenommen) I prefer GPG encryption of emails. (does not apply on mailing lists) signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] key trees
I might be wrong, but there seemed to be a big push a while back to make “landuse=farmland” take over any land where stuff is grown and have crop=* handle what is physically there and the produces=* tag handle what is harvested. A lot of the grapes grown in my area are on horizontal steel trellis’ in plastic greenhouses (landuse=greenhouse_horticulture) - grown for sale in bunches (they are really expensive), and don’t look anything like a California nor Japanese “vineyard” with grapes in big long rows outdoors on vertical supports - nor a basic dirt farm field. Rice fields are flooded, are named and special here in Japan (tanbo: 田んぼ), with the extremely common kanji “ta” 田 representing a rice field - I suppose this is true elsewhere in Asia. Perhaps some cultures would have a special word or crop that is treated differently than all others That is “just another crop” elsewhere, like rice is here. Making everything that grows plants for food or processed plant products (cotton) has its merits. Being able to tag everything under the same landuse idea (farmland) and then add additional tags to say what is on the land, what grows on it, and what it makes: greenhouse=yes, trellis=* netting=* crop=* produces=* is nice. Most commercial apple and pear orchards here have retractable netting that goes over an entire orchard, it would be nice to tag it somehow. But this runs counter to tagging things in a way that makes it fit into English words for new tagger friendliness (orchard / vineyard / etc) and the idea of “duck tagging (tag an orchard as an orchard), so I think both systems are in use at the same time and adaptable enough for any situation - I wouldn’t call the few greenhouses trapped between a trunk road and a train road a “vineyard” - and the large swaths of California or North of Mt Fuji are most certainly “vineyards”, regardless of what the grapes are used for. With increased uses of tagging presets in iD, this might be come a moot point. Javbw > On Jul 11, 2017, at 8:43 AM, Warin <61sundow...@gmail.com> wrote: > > Hi, > > According to the OSMwiki the key tree; > > > 1) is to be used for plants ... that would include shrubs and grasses. > > > 2) is to be used to define what is growing in an orchard. > > > 3) has been 'approved'? > > > > > I would suggest it would be better > > > If this is only for use with the key landuse=orchard then a sub key such as > orchard=berry_tree, * would be better? > > > > > > > > > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] key trees
Hi, According to the OSMwiki the key tree; 1) is to be used for plants ... that would include shrubs and grasses. 2) is to be used to define what is growing in an orchard. 3) has been 'approved'? I would suggest it would be better If this is only for use with the key landuse=orchard then a sub key such as orchard=berry_tree, * would be better? ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] highspeed=yes
sent from a phone > On 10. Jul 2017, at 23:42, Michael Reichert wrote: > > The main question is: > Shold the whole line (the definition of "line" is a different discussion > worth) get highspeed=yes or only the parts which are suitable for high > speeds due to large curve radius, special signalling and train > protection etc.? What is your opinion? What is a "line" in osm tags? If you map a specific train connection (route=train) it would apply to the whole thing, if you tag a piece of rail (route=railway or railway=rail) I would only put it on those parts that are suitable for highspeed trains. Cheers, Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] highspeed=yes
Hi, I have a small dispute with user flierfy about the usage of highspeed=yes and would like to ask for your opinions. [1] I think that highspeed=yes should only be use that tracks whose speed limit is above a certain minimum speed (On The Ground Rule). The speed might vary between countries. flierfy thinks that the whole railway line should be tagged from its beginning to its end if it contains one part which qualifies for highspeed=yes. Example: The railway line from Leipzig to Dresden clearly qualifies [2] for highspeed=yes between km 4.0 (near Leizig-Sellershausen) to km 23.8 (near Bennewitz) and from ~ 30.2 (between Wurzen and Kühren) to 59.6 (between Bornitz bei Oschatz and Riesa). Only on these two sections trains may run faster than 160 kph (limit is 200 kph there). Other sections have speed limits between 100 kph and 160 kph. Flierfy tagged the whole line with highspeed=yes. http://www.openrailwaymap.org/?lang=&lat=51.33372202647613&lon=13.089437484741211&zoom=13&style=standard The high speed line might be completed on one day in future but it will takes years, many years. The wiki pages Key:highspeed, DE:Key:highspeed and OpenRailwayMap/Tagging at OSM wiki do not mention whether the tag should be used for the whole line or only for the parts whose speed limit is "high". In difference, DE:OpenRailwayMap/Tagging has contained the additional sentence that the whole line should get highspeed=yes. That sentence was added by user rurseekatze on 2015-12-29 [3]. I don't remember a discussion about it on a mailing list. Fliefy refers in the changeset discussion between us to DE:OpenRailwayMap/Tagging. The definition of this tag was discussed on a meeting of railway mappers in Cologne in July 2014 but we did not find any consensus there and left it unmodified. In March 2015 a mapper attempted to add highspeed=yes to the Northeast Corridor from Washington to Boston. After 25 comments in the changeset discussion the tag was removed. https://www.openstreetmap.org/changeset/29723896 The main question is: Shold the whole line (the definition of "line" is a different discussion worth) get highspeed=yes or only the parts which are suitable for high speeds due to large curve radius, special signalling and train protection etc.? What is your opinion? Best regards Michael PS I invited fliefy to join this mailing list on Friday and waited with posting my question until today to be fair. [1] changeset discussion in German (just for reference): https://www.openstreetmap.org/changeset/50067730 [2] assuming that high speed in Germany means 200 kph or faster. Other countries might have other limits. [3] https://wiki.openstreetmap.org/w/index.php?title=DE%3AOpenRailwayMap%2FTagging&type=revision&diff=1256039&oldid=1238373 -- Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten ausgenommen) I prefer GPG encryption of emails. (does not apply on mailing lists) signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Time is now: tag ALL traffic signs in OSM
It is interesting your petition. My point of view is , even the meaning of two traffic signs in differents places would be the same, it would be different traffic signs. In some countries there are other codes for the road marks (but with the same meaning) so they aren't the same traffic sign so they can't stay at two positions (right and down or up side) When there is two traffic signs in one pole you can tag it with subtag numbers as the Finnish Commnity does. Example with traffic_sign:2:forward= or traffic_sign:2:backward. It is important because when there is more than a traffic sign one is active until the limitation or the situation that informs you the second. Example: in https://www.mapillary.com/ map/im/7NffYKT31sYbbZSqQutpSw this specific maxspeed limit is only for the crossing. Once you have passed the crossing you will have the implicit maxspeed limit or other. For this reason it is important to tag the order of the traffic sign. People from Mapillary do that, they know how the OSM community does not want automatted imports but they made available to tag some traffic signs detected in their pics through the JOSM plug-in. I have also talk to them and they are in contact for updates. Salut i senyals de trànsit (Health and traffic signs) yopaseopor ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
