Re: [Tagging] Basic cartography features missing, why?

2020-11-06 Thread Seth Deegan
A gravel area tag/tagging convention is needed. One use I’ve seen is highways in particular seem to have gravel separator between the actual road and usually grass. Standardizing a area (a way) with just the surface=gravel tag could work. El El vie, nov. 6, 2020 a la(s) 12:34, Anders Torger escri

Re: [Tagging] Basic cartography features missing, why?

2020-11-07 Thread Seth Deegan
I actually just found that article about OSM’s problems. One of the major topics mentioned, the fact that OSM acts as a database and not a map, and that this acts as a hinderance to the expansion and development of the project, is very true. As a result, I’ve came to think that implementing Vecto

Re: [Tagging] Basic cartography features missing, why?

2020-11-08 Thread Seth Deegan
sidewalks... Who is > supposed to use and rely on such data? > > Duplicate tags are mildly irritating while processing, but it is not a > serious or main problem for > data consumers. > > (and it is from person who put a lot of effort into tagging improvements, > wikifiddl

Re: [Tagging] Basic cartography features missing, why?

2020-11-08 Thread Seth Deegan
good result > with currently available open source tools, and there will have to be some > compromises which worsen the cartography in some cases. > > I have not heard an update on this project in the past few months, so it > may be stalled. > > -- Joseph Eisenberg > > On S

Re: [Tagging] Deprecate water=pond?

2020-11-11 Thread Seth Deegan
Yes, but the range in size of lakes is massive (local ones compared to the Great Lakes in the U.S.). You wouldn’t want the names of smaller lakes showing up at lower zoom levels like the Great Lakes should. If one was to establish a rendering difference, they should probably do so by computing the

[Tagging] Tagging Cycle Route Relations vs. Ways

2020-11-16 Thread Seth Deegan
name>=*s of Ways. However, I think osm-carto *should* render and *prefer* to render Relation names for Cycle routes over the names of the Ways. The Editors should also somehow influence users to map Relations for Cycle routes instead of naming them. Thoughts? Seth Deegan (lectrician1)

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

2020-11-16 Thread Seth Deegan
/wiki/Key:name > [2] https://wiki.openstreetmap.org/wiki/Cycle_routes#Rendered_cycle_maps > [3] https://cycling.waymarkedtrails.org > [4] https://wiki.openstreetmap.org/wiki/Relation:superroute > [5] > https://cycling.waymarkedtrails.org/#route?id=2763798&map=4!57.9189!7.9873 > > > On 1

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

2020-11-16 Thread Seth Deegan
bers. It's not a relational database model. > > If many streets are called "Polygon Alley" you tag each one with > name=Polygon Alley. No normalization applies, just tag it. > Best, Peter Elderson > > > Op ma 16 nov. 2020 om 18:17 schreef Seth Deegan : > >>

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

2020-11-16 Thread Seth Deegan
May I ask why not source=*? I know it's basically depreciated, but many times I find myself wondering where past mappers got the info for a route (this happened just today). I would find it very helpful. It also doesn't require the tagging of all of the ways. On Mon, Nov 16, 2020 at 8:45 PM Kevin

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

2020-11-16 Thread Seth Deegan
ack in the history to find a source. On Mon, Nov 16, 2020 at 9:09 PM Seth Deegan wrote: > May I ask why not source=*? I know it's basically depreciated, but many > times I find myself wondering where past mappers got the info for a route > (this happened just today). I would find

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

2020-11-17 Thread Seth Deegan
> > it does an OK job of this: click the History button to get a > recent-around-here list of 20 edits (click the Load More button for 20 > more…and again and again if you like). > Yes, the History button does do a good job. But I'm talking about this: Clicking on one specific changeset will “dr

Re: [Tagging] Extremely long Amtrak route relations / coastline v. water

2020-11-22 Thread Seth Deegan
I recently found out about the Extremely long Amtrak route relations from clay_c. Your message is a bit confusing at first but I think you are proposing that relations and super-relations should be used more-often to reduce the complexity of processing data for data consumers? In that case, I wou

Re: [Tagging] surface=boardwalk? is it duplicate of surface=wood?

2020-11-22 Thread Seth Deegan
I agree with Dave F. It's a duplicate. On Sat, Nov 21, 2020 at 7:43 PM Dave F via Tagging < tagging@openstreetmap.org> wrote: > To me, boardwalk describes the design & appearance rather than the surface > construction: An elevated walkway. > Although I do admit that's mostly influenced by The Dr

Re: [Tagging] Animal trails

2020-11-30 Thread Seth Deegan
You could add a `note=*` to every element. You should probably contact the mappers of that region and explain to them not to add them. I agree that in this case, mapping animal tracks is *especially *necessary. If someone isn't going to map it now, they're going to do so in the future (as you've s

Re: [Tagging] Continuous shoulder rumble strips (CSRS)

2020-12-20 Thread Seth Deegan
Those are known as rumble strips. The wiki has traffic_calming=rumble_strip: https://wiki.openstreetmap.org/wiki/Key:traffic_calming#Common_values There is no page for the tag though, differentiating the types of rumble strips there are. For examples, I’ve seen them on: The side of a highway (sh