Re: [Tagging] Tagging standards [moved from osmf-talk]
вт, 25 окт. 2022 г., 0:59 Illia Marchenko : > Then so: > > > > > > > > > > > > > > > > P. S. After https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Tagging standards [moved from osmf-talk]
вт, 25 окт. 2022 г., 0:30 Asa Hundert : > Am Mo., 24. Okt. 2022 um 01:05 Uhr schrieb Illia Marchenko > : > > > > I suggest alternative solution: some machine readable spec, which > defines mapping between stable identifier and tags. For example (XML): > > > > > > > […] > > In XML, ids must be unique. Then so: > Did you mean "my personal notion of what > this stands for ID"? After reading > https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua > consumers are doing that already. > This is example only. Of course, another options is possible, including Lua, JSON or even binary. Regards, Illia. > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Tagging standards [moved from osmf-talk]
Am Mo., 24. Okt. 2022 um 01:05 Uhr schrieb Illia Marchenko : > > I suggest alternative solution: some machine readable spec, which defines > mapping between stable identifier and tags. For example (XML): > > > […] In XML, ids must be unique. Did you mean "my personal notion of what this stands for ID"? After reading https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua consumers are doing that already. Asa ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - Approved - Payment denominations
Hi, the proposal has been approved. https://wiki.openstreetmap.org/wiki/Proposed_features/Payment_denominations In the coming days, I will create wiki pages for the keys. I will also try to incorporate some of the comments by users who voted against the proposal or abstained from voting (without changing the core of the accepted tagging scheme, of course). Kind regards, Michael ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - Voting - amenity=mailroom
Voting has started for amenity=mailroom https://wiki.openstreetmap.org/wiki/Proposed_features/amenity%3Dmailroom Please take a second and vote (for it). Thanks. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - archaeological_site
On 24/10/22 07:11, Mateusz Konieczny via Tagging wrote: Oct 22, 2022, 15:09 by dieterdre...@gmail.com: sent from a phone On 22 Oct 2022, at 12:47, Anne-Karoline Distel wrote: Following the rejection of the crannog proposal with the concern about the hierarchy above the proposed tag, I now propose to change the key from site_type to archaeological_type such a retagging would be a waste of time, I would not pursue this idea, and given the high majority that is required nowadays it is also unlikely to succeed. You could just continue mapping the settlement sites and crannogs as you please and have a wonderful time, document the tags, speak about it so that other people interested in mapping this kind of feature can join you. :-) personally it seems to me that it has chance of being a good idea +1 It can coexist with past tags ... Migration can then proceed; A mechanical edit can be done to add the new tags. (normal approval process) After some time of use, the older tags can be removed .. (normal approval process) ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Tagging standards [moved from osmf-talk]
On 23.10.22 21:26 Brian M. Sperlongano wrote: In my mind, the one thing that has been sorely lacking from this discussion is a clear articulation of the problem we are trying to solve here, from both a data producer (mapper) and data consumer (renderer etc) perspective. Standardization is crucial for those aspects of our data model that a data consumer has to design algorithms around. Things like lane mapping, Conditional Restrictions, the standards for 3d buildings and indoor mapping, and so on. When I spend months writing code for working with some aspect of OSM data, I need a stable foundation to build on. So I want to be reasonably confident that ... * changes won't be made casually * my use case won't be rendered impossible because it is overlooked or deemed unimportant by someone with different priorities * there will be efforts to align the data with the new standard in a timely fashion (no decade-long coexistence of "old" and "new" styles) * I can easily learn of any changes relevant to me * I'm preferably even consulted as an expert before changes are made. At the moment, none of that is the case. It is not at all unheard of for a mapper to just write things to the wiki that break the core logic and assumptions of established standards. Or for a descriptivist wiki editor to discover that some percentage of the database does things differently and to rewrite the wiki instead of fixing the data. And the only way for me to prevent or even notice any of that is to watch thousands of wiki pages for changes (most of which will be formatting noise) and then attempt to convince the person making the change why it would be a bad idea. Do I have the perfect solution to achieve that? No. But you asked for problems to solve, and we will have to deal with those problems if we want people to confidently invest their time into building more complex OSM-based software – the kind of software needed to match the features that our competitors are already rolling out. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - archaeological_site
sent from a phone > On 23 Oct 2022, at 22:15, Mateusz Konieczny via Tagging > wrote: > > personally it seems to me that it has chance of being a good idea which one, deprecating site_type or ignoring the „rejection“ of the voting? Cheers Martin ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
