Re: [OSM-talk] Waterway=* and Waterways wiki pages merge
sent from a phone > On 23. Mar 2018, at 19:42, François Lacombe wrote: > > Mixing waterways and culverts or gates in the same list isn't so clear. it is not mixing (or should not) waterways and culverts. The culvert property is for stating that a waterway runs inside a culvert (the culvert is implied, but strictly the way is not representing the culvert, e.g. the name is of the waterway, not the culvert), like bridge=yes which states a highway runs over a bridge. If you wanted, you could still map the culvert as an explicit object (usually not done because most mappers don’t have much information to add to a culvert, besides that it is a culvert). cheers, Martin ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Waterway=* and Waterways wiki pages merge
There are many way of thinking about this.
Mixing waterways and culverts or gates in the same list isn't so clear.
If I want to know which are the possible waterways I can map, it's not a
concern they can be under a culvert or through a gate.
The point is to give essential features and let people find more precise
things on keys pages if and only if they want to.
This is what is done on power features list.
https://wiki.openstreetmap.org/wiki/Key:power
François
2018-03-23 18:02 GMT+01:00 Martin Koppenhoefer :
>
>
> 2018-03-23 17:58 GMT+01:00 Martin Koppenhoefer :
>
>> 2018-03-23 17:01 GMT+01:00 François Lacombe :
>>
>>>
>>> One additional issue is the "additional attributes for waterways" in the
>>> feature table here : https://wiki.openstreetmap.org/wiki/Key:waterway
>>> It's not a good idea to put attributes in the feature table since they
>>> can be related to other tags as well.
>>> Can they get removed from this list ?
>>>
>>
>>
>>
>> I would keep a reference to the attributes there, it could be a different
>> table or a list if you prefer, it is only for reference, as far as I have
>> seen all of those attributes already have their own tag / key page where
>> they are defined, and if you want to include references to them from other
>> feature pages, you can do it with the standard tag templates like
>> {{Tag|tunnel|culvert}}.
>>
>>
>
> the scheme seems to be used for other key pages as well, see for example
> https://wiki.openstreetmap.org/wiki/Key:highway
>
> Cheers,
> Martin
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Waterway=* and Waterways wiki pages merge
2018-03-23 17:58 GMT+01:00 Martin Koppenhoefer :
> 2018-03-23 17:01 GMT+01:00 François Lacombe :
>
>>
>> One additional issue is the "additional attributes for waterways" in the
>> feature table here : https://wiki.openstreetmap.org/wiki/Key:waterway
>> It's not a good idea to put attributes in the feature table since they
>> can be related to other tags as well.
>> Can they get removed from this list ?
>>
>
>
>
> I would keep a reference to the attributes there, it could be a different
> table or a list if you prefer, it is only for reference, as far as I have
> seen all of those attributes already have their own tag / key page where
> they are defined, and if you want to include references to them from other
> feature pages, you can do it with the standard tag templates like
> {{Tag|tunnel|culvert}}.
>
>
the scheme seems to be used for other key pages as well, see for example
https://wiki.openstreetmap.org/wiki/Key:highway
Cheers,
Martin
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Waterway=* and Waterways wiki pages merge
2018-03-23 17:01 GMT+01:00 François Lacombe :
>
> One additional issue is the "additional attributes for waterways" in the
> feature table here : https://wiki.openstreetmap.org/wiki/Key:waterway
> It's not a good idea to put attributes in the feature table since they can
> be related to other tags as well.
> Can they get removed from this list ?
>
I would keep a reference to the attributes there, it could be a different
table or a list if you prefer, it is only for reference, as far as I have
seen all of those attributes already have their own tag / key page where
they are defined, and if you want to include references to them from other
feature pages, you can do it with the standard tag templates like
{{Tag|tunnel|culvert}}.
Cheers,
Martin
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Waterway=* and Waterways wiki pages merge
Hi Martin, Understood, I won't merge the overview page, and will only move stuff between two page as to remove redundancies. One additional issue is the "additional attributes for waterways" in the feature table here : https://wiki.openstreetmap.org/wiki/Key:waterway It's not a good idea to put attributes in the feature table since they can be related to other tags as well. Can they get removed from this list ? François 2018-03-23 16:20 GMT+01:00 Martin Koppenhoefer : > > > 2018-03-23 15:45 GMT+01:00 François Lacombe : > >> Hi, >> >> I'm currently thinking about wiki improvement about waterways. >> >> It would be great to move (with caution) the content of the Waterways >> page to Key:waterway >> https://wiki.openstreetmap.org/wiki/Key:waterway >> https://wiki.openstreetmap.org/wiki/Waterways >> >> This would prevent redundancy and ease tagging documentation maintenance. >> There are many translations which aren't up to date currently. >> Waterways page will be redirected to Key:waterway >> >> Does anyone have a concern about this ? >> > > > I am a bit unsure about this. Some years ago (actually 7), those > "collector" / "overview" pages have been set up. They were (if I interpret > it right) not thought as specific tagging documentation, but as overview > pages about a certain topic, with references to tag definition pages, so > you could find the right tag page. > > The key:waterway page should be mainly about the key waterway and should > contain exhaustive information about this key. It has a reference to the > more generic Waterways overview page, where you can find references to the > main concepts and tags, not only waterway=* tags but including man_made > tags, natural=* tags and others. > > Clearly all relevant information regarding the waterway key and its > meaning, application and interpretation, should be on the key:waterway > page. If such information is only on the overview page, it should be > verified/discussed and transferred. > It is also not needed to repeat all the waterway specific information on > the overview page, its purpose is different: give an overview and lead to > relevant tag pages. > > I can imagine that this initial distinction may have been blurred in the > years since it was created, so a review surely makes sense, but generally I > think it is a good idea to have the overview pages (about topics, rather > than keys). > > Btw., what I wrote is not only referring to waterways, but in analogy also > to other topics like these: > > https://wiki.openstreetmap.org/wiki/Speed_limits > https://wiki.openstreetmap.org/wiki/Highways > https://wiki.openstreetmap.org/wiki/Landuse > https://wiki.openstreetmap.org/wiki/Landcover > https://wiki.openstreetmap.org/wiki/Places > https://wiki.openstreetmap.org/wiki/Addresses > https://wiki.openstreetmap.org/wiki/Public_transport > https://wiki.openstreetmap.org/wiki/Power > and maybe more > > None of these pages has ever been voted, naturally. > > I'm generally in favor of keeping them, but they should be reviewed to > make sure the overview pages are concise overview pages, and relevant > information is on the key and tag pages. > > They should also get a disclaimer what they are meant to be, so that > people aren't confused. > > Regarding missing and out of date translations: this is the standard > situation in the wiki, even for the "main languages", with maybe very few > exceptions. We should care for the English version here, and leave > translations to the local communities, who could also decide not to > translate some pages (because they know they are so few they will not be > able to keep it updated). > > Cheers, > Martin > > > ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Waterway=* and Waterways wiki pages merge
2018-03-23 15:45 GMT+01:00 François Lacombe : > Hi, > > I'm currently thinking about wiki improvement about waterways. > > It would be great to move (with caution) the content of the Waterways page > to Key:waterway > https://wiki.openstreetmap.org/wiki/Key:waterway > https://wiki.openstreetmap.org/wiki/Waterways > > This would prevent redundancy and ease tagging documentation maintenance. > There are many translations which aren't up to date currently. > Waterways page will be redirected to Key:waterway > > Does anyone have a concern about this ? > I am a bit unsure about this. Some years ago (actually 7), those "collector" / "overview" pages have been set up. They were (if I interpret it right) not thought as specific tagging documentation, but as overview pages about a certain topic, with references to tag definition pages, so you could find the right tag page. The key:waterway page should be mainly about the key waterway and should contain exhaustive information about this key. It has a reference to the more generic Waterways overview page, where you can find references to the main concepts and tags, not only waterway=* tags but including man_made tags, natural=* tags and others. Clearly all relevant information regarding the waterway key and its meaning, application and interpretation, should be on the key:waterway page. If such information is only on the overview page, it should be verified/discussed and transferred. It is also not needed to repeat all the waterway specific information on the overview page, its purpose is different: give an overview and lead to relevant tag pages. I can imagine that this initial distinction may have been blurred in the years since it was created, so a review surely makes sense, but generally I think it is a good idea to have the overview pages (about topics, rather than keys). Btw., what I wrote is not only referring to waterways, but in analogy also to other topics like these: https://wiki.openstreetmap.org/wiki/Speed_limits https://wiki.openstreetmap.org/wiki/Highways https://wiki.openstreetmap.org/wiki/Landuse https://wiki.openstreetmap.org/wiki/Landcover https://wiki.openstreetmap.org/wiki/Places https://wiki.openstreetmap.org/wiki/Addresses https://wiki.openstreetmap.org/wiki/Public_transport https://wiki.openstreetmap.org/wiki/Power and maybe more None of these pages has ever been voted, naturally. I'm generally in favor of keeping them, but they should be reviewed to make sure the overview pages are concise overview pages, and relevant information is on the key and tag pages. They should also get a disclaimer what they are meant to be, so that people aren't confused. Regarding missing and out of date translations: this is the standard situation in the wiki, even for the "main languages", with maybe very few exceptions. We should care for the English version here, and leave translations to the local communities, who could also decide not to translate some pages (because they know they are so few they will not be able to keep it updated). Cheers, Martin ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [OSM-dev] OpenStreetMap Carto release v4.9.0
W dniu 23.03.2018 o 15:43, Stefan Keller pisze: > How can I help implementing rendering of castles (forts, ruins, > manors, palaces)? > https://github.com/gravitystorm/openstreetmap-carto/issues/744 Thanks! Well, I'm not sure - it's mostly about weighting the problems and picking the proper solutions now, so any help with making decisions will do. With historic=ruins (of course it's not in the historic=castle tagging) it's easier, I feel we're pretty close to find a proper icon: https://github.com/gravitystorm/openstreetmap-carto/issues/331#issuecomment-372013931 However with the rest (castles, fortresses, palaces, manors, stately...) all the icons are more or less ready, but we have a problem what to do with having different valid and used in practice tagging schemes and the discussion on the Tagging list still does not make it clear enough for me: https://github.com/gravitystorm/openstreetmap-carto/pull/3099#issuecomment-374607590 -- "My method is uncertain/ It's a mess but it's working" [F. Apple] ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Waterway=* and Waterways wiki pages merge
Hi, I'm currently thinking about wiki improvement about waterways. It would be great to move (with caution) the content of the Waterways page to Key:waterway https://wiki.openstreetmap.org/wiki/Key:waterway https://wiki.openstreetmap.org/wiki/Waterways This would prevent redundancy and ease tagging documentation maintenance. There are many translations which aren't up to date currently. Waterways page will be redirected to Key:waterway Does anyone have a concern about this ? Water Management page would stay and be completed with recent hydropower tagging adding https://wiki.openstreetmap.org/wiki/Water_management All the best François ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [OSM-dev] OpenStreetMap Carto release v4.9.0
Hi Daniel Nice. Many thanks for your work! How can I help implementing rendering of castles (forts, ruins, manors, palaces)? https://github.com/gravitystorm/openstreetmap-carto/issues/744 :Stefan 2018-03-23 14:41 GMT+01:00 Daniel Koć : > Dear all, > > Today, v4.9.0 of the openstreetmap-carto stylesheet (the default > stylesheet on the OSM website) has been released. Once changes are > deployed on the openstreetmap.org it will take couple of days before all > tiles show the new rendering. > > Changes include > > Major changes > - A bug where closed ways with natural=cliff or natural=tree_row were > not rendering has been fixed. This required fixing a transform bug. The > fix will apply to all objects when they are created in OSM, but there is > no migration for existing databases. Deployments will have to decide if > the effects are serious enough to require them to reload the database. > > Changes > - Adding place=square name rendering > - Adding rendering for different types of towers and masts > - Making gardens to use grass color with plant nursery pattern > - Adding rendering for intermittent water bodies > - Give oceans outline and simplify shapefiles on z0-7 > - Simplify (generalize) admin borders > - Move natural=grassland and landuse=meadow earlier > - Start rendering aerialway name > - Adding icons for amenity=bbq, amenity=shower, leisure=sauna and > advertising=column > - Adding special icons for shop=dairy, shop=medical_supply and shop=music > - Move amenity=toilets to higher zoom levels > - Fixing some SVG icons artifacts > - Make military=danger_area font dark pink and slanted > - Changing rendering for construction=steps to distinguish it from roads > - Changing label colour of private parking > - Small documentation and code fixes > > Thanks to all the contributors for this release, including james2432, > Penegal and jragusa, new contributors. > > For a full list of commits, see > https://github.com/gravitystorm/openstreetmap-carto/compare/v4.8.0...v4.9.0 > > As always, we welcome any bug reports at > https://github.com/gravitystorm/openstreetmap-carto/issues > > -- > "My method is uncertain/ It's a mess but it's working" [F. Apple] > > ___ > dev mailing list > d...@openstreetmap.org > https://lists.openstreetmap.org/listinfo/dev ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] OpenStreetMap Carto release v4.9.0
You're welcome :) On Fri, Mar 23, 2018, 9:45 AM Daniel Koć, wrote: > Dear all, > > Today, v4.9.0 of the openstreetmap-carto stylesheet (the default > stylesheet on the OSM website) has been released. Once changes are > deployed on the openstreetmap.org it will take couple of days before all > tiles show the new rendering. > > Changes include > > Major changes > - A bug where closed ways with natural=cliff or natural=tree_row were > not rendering has been fixed. This required fixing a transform bug. The > fix will apply to all objects when they are created in OSM, but there is > no migration for existing databases. Deployments will have to decide if > the effects are serious enough to require them to reload the database. > > Changes > - Adding place=square name rendering > - Adding rendering for different types of towers and masts > - Making gardens to use grass color with plant nursery pattern > - Adding rendering for intermittent water bodies > - Give oceans outline and simplify shapefiles on z0-7 > - Simplify (generalize) admin borders > - Move natural=grassland and landuse=meadow earlier > - Start rendering aerialway name > - Adding icons for amenity=bbq, amenity=shower, leisure=sauna and > advertising=column > - Adding special icons for shop=dairy, shop=medical_supply and shop=music > - Move amenity=toilets to higher zoom levels > - Fixing some SVG icons artifacts > - Make military=danger_area font dark pink and slanted > - Changing rendering for construction=steps to distinguish it from roads > - Changing label colour of private parking > - Small documentation and code fixes > > Thanks to all the contributors for this release, including james2432, > Penegal and jragusa, new contributors. > > For a full list of commits, see > https://github.com/gravitystorm/openstreetmap-carto/compare/v4.8.0...v4.9.0 > > As always, we welcome any bug reports at > https://github.com/gravitystorm/openstreetmap-carto/issues > > -- > "My method is uncertain/ It's a mess but it's working" [F. Apple] > > ___ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk > ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk] OpenStreetMap Carto release v4.9.0
Dear all, Today, v4.9.0 of the openstreetmap-carto stylesheet (the default stylesheet on the OSM website) has been released. Once changes are deployed on the openstreetmap.org it will take couple of days before all tiles show the new rendering. Changes include Major changes - A bug where closed ways with natural=cliff or natural=tree_row were not rendering has been fixed. This required fixing a transform bug. The fix will apply to all objects when they are created in OSM, but there is no migration for existing databases. Deployments will have to decide if the effects are serious enough to require them to reload the database. Changes - Adding place=square name rendering - Adding rendering for different types of towers and masts - Making gardens to use grass color with plant nursery pattern - Adding rendering for intermittent water bodies - Give oceans outline and simplify shapefiles on z0-7 - Simplify (generalize) admin borders - Move natural=grassland and landuse=meadow earlier - Start rendering aerialway name - Adding icons for amenity=bbq, amenity=shower, leisure=sauna and advertising=column - Adding special icons for shop=dairy, shop=medical_supply and shop=music - Move amenity=toilets to higher zoom levels - Fixing some SVG icons artifacts - Make military=danger_area font dark pink and slanted - Changing rendering for construction=steps to distinguish it from roads - Changing label colour of private parking - Small documentation and code fixes Thanks to all the contributors for this release, including james2432, Penegal and jragusa, new contributors. For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.8.0...v4.9.0 As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues -- "My method is uncertain/ It's a mess but it's working" [F. Apple] ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
