Xavizard Knight's Comments
| Changeset | When | Comment |
|---|---|---|
| 169304196 | 5 months ago | I don't have plans to delete these tags (at least not for now), as they don't seem to break anything and they don't annoy me that much as to go out of my way and go delete them right now (aside from being logically contradictory if we look it from a tag meaning perspective). But I will delete them when I finish the ways. The only propose of your noexit tags is explicitly tagging for the router (osm.wiki/Tagging_for_the_router) because you are only using them to appease the OSMI validator. And actually, this seems like a validator that's acting weird because it only flagged the four gates that you've modified, and not the many other unfinished ways that are scattered in this neighbourhood. This behaviour should be reported as a bug instead of adding tags to mitigate it. The wiki page of the noexit=yes tag (noexit=yes) also provides guidelines that conflict with your tagging:
Also, it's confusing that you say adding barriers and accessways is "nonbeneficial micromapping" since you're adding these noexit tags to help a routing software on barriers and accessways. |
| 169304196 | 5 months ago | This looks a lot to me like "tagging for the router". The reason why some gates have ways behind them and others don't in this neighbourhood, is because some paths can be seen from aerial and/or street-level imagery.
There are many other houses nearby with partially or completely missing entry ways that you haven't yet tagged with noexit=yes, like for example house numbers 147, 149, 157, 159, 163, 173, 179, 183, 185, 191, 193, 195, 197, 199, 209, 211, 213, 215 or 217, among others. Adding noexit=yes tags to barrier=gate nodes doesn't make sense because:
And if you argue that these gates are technically noexit situations because the way on the other side isn't (yet) mapped to OSM, then I assure you that I would have mapped the gates differently if the way didn't continue on the other side (because otherwise it would be a disused: or an abandoned: gate). |
| 169304196 | 5 months ago | Hello! Thank you for contributing to OpenStreetMap! In this commit, you've added noexit=yes tags to four gates of houses.
|
| 167262598 | 7 months ago | Hello! Thank you for your contributions! In this edit, you added a footpath way that goes through the backyard of the house near C/Sagrada Família, but then crosses a hedge barrier and goes to the backyard of another house. This seems incorrect. I do not live there, but for what it can be seen from the near Camí del Fornás and from aerial and topographical imagery, there is no way to cross that hedge barrier. The two backyards are two different and separate backyards with no apparent connection. Also, you've mapped this way (and others within the backyards) with footway=sidewalk (which is incorrect because this way is not besides a road) and motor_vehicle=no (which is unnecessary; otherwise it would be another type of highway). Do you have any sources that point to the hedge crossing being there? |
| 166578641 | 7 months ago | Bon dia!
Els noms dols etiquetes venen de tal i com es mencionen a geovalls i a altres documents i recursos de l'Ajuntament, que surten com "bens" i "masies" (fixa't que els dos noms són en plural, inclús quan es refereixen a un sol element).
He corregit les etiquetes errònies en aquest changeset:
|
| 165006740 | 8 months ago | Bones! Benvingut a OpenStreetMap! Moltes gràcies per tunes contribucions! No sabia que el Carrer del Call també se l'hi diu Corraló dels gats. Sempre està bé aprendre coses noves! En tun changeset has comentat que falta d'etiquetar-hi uns escalons al començant del carrer que connecta amb el Carrer dels Jueus; però aquests escalons ja estan mapejats a OSM. Estan posats com tres trams separats d'escales, amb vies peatonals del mig. És possible que no els hagis vist perquè són força curts. Si no recordo malament, els vaig mapejar en base al mapa topogràfic de l'ICGC. El Carrer del Call està dividit en 9 vies; enumerant-les d'esquerra a dreta, aquestes vies són les següents:
Els escalons a què et refereixes són les vies 4, 6 i 8 ja existents o són unes altres que no hi són al mapa? També has afegit les etiquetes tunnel=yes i layer=-1 al tram que està al descobert en lloc del tram que passa per sota la casa-pont. Ha estat això un error o han fet modificacions recents que han tapat el carrer? (Fa uns quants mesos que no hi tombo per aquest carrer, així que corregeix-me si m'equivoco). |
| 164937675 | 8 months ago | Thanks to you for creating the proposal and the tagging scheme! I find it very useful to add information about sensory accommodations to OSM
And you can tell that because the check_date dates in my first commit were from 2 months ago lol
|
| 164056335 | 9 months ago | I don't think that the generic fuel name is written anywhere near the pumps in Repsol gas stations, everything is filled with the branded fuel logos and colours and such. Although, to be honest, I don't look them much when I go there xD For now, I've been able to find more info online. On Repsol's website, they talk about Repsol Blue+ as their version of Adblue fuel, which means that Blue+ is equivalent to fuel:adblue.
Besides, the fuel:diesel and fuel:GTL_diesel tags do also appear in other Repsol gas station throughout the city that originally came from a 2010 import (that I should have looked before tagging my way... ups). I'll add these values and replace the old ones in my upcoming commit |
| 164056335 | 9 months ago | Heyas!
For adding fuel tags, I used a combination of the ones that are in the JOSM built-in preset and some taginfo search as guidance. For "fuel:blue+", "fuel:diesel_e+" and "fuel:diesel_e+10" I assumed that these are Repsol-exclusive fuel types whose name/type is this, or industry-wide ways of referring about them, so I added them as such. I'm doing edits on other gas stations in Valls, so I'll revise the fuel tags of this station and the others, and I'll try to fit them more common values.
Thanks for the heads-up! |
| 164068699 | 9 months ago | Bones! Gràcies per la rectificació de l'etiqueta waylet.
Aquest shop=yes prové del preset de Transport > Cotxe > Benzinera del JOSM, i l'he posat per indicar que aquesta benzinera té una petita botigueta a on es poden comprar snacks i accessoris de manteniment per al cotxe. Quina etiqueta suggereixes usar en lloc de la shop= per marcar aquesta tenda (si és que es pot marcar d'alguna manera)? |
| 164056335 | 9 months ago | Would it be nice to have an international whole-world standard for traffic sign tagging? Yes! It would be very nice indeed! Unfortunately, such an international standard is very unlikely to ever happen.
A month or so ago, yopaseopor released for comments a proposal for using "traffic_sign:id" for the national traffic sign codes (https://community.openstreetmap.org/t/new-proposal-about-traffic-sign-international-code-mapping/125438). The results were mixed, some liked it, but others opposed it because it will conflict with their local systems; and it caused a big and long debate on the forum. If something as simple as moving a single tag, caused this much of a debate, then discussing an entire international traffic sign tagging system is a literally impossible mission that will lead to absolutely nowhere. These are the reasons why I think that international standards in the world of traffic signs are futile. Taking into consideration all the signs, organisation systems of these signs, exceptions to those systems, icons, and placement of everything is a colossal task.
And yes, you are absolutely correct that many countries, not only in Europe, but in the entire world, have very similar traffic signs, thanks to the Vienna Convention. But this doesn't mean that everybody who follows the convention has identical signs, every country has a different combo of symbols, fonts, text, icons, colours and even shapes. And also, the Vienna Convention goes out the window in the destination sign situation, where every country is a whole different world, so the convention can do very little with roundabouts and intersection signs. An international debate and/or international proposal for how we should map Catalan traffic signs only in Catalonia is nonsense. Catalonia-specific things should be proposed, debated and approved by users in Catalonia only; it doesn't make sense to involve other mappers from the other side of the world that have no idea of how things work in Catalonia. If there were two or more competing local standards, with no way to set things clear of which to use, an internation debate could be a tiebreaker to solve the situation; but that's not the case here. Catalonia had no local traffic sign standard before, we are creating one. As easy as that. Other countries and territories in the world do also have their own ways of tagging and mapping traffic signs, like Finland, for example (osm.wiki/Finland/Traffic_signs#Traffic_sign_mapping_in_Finland). Do you also chase the commits of every new Finland traffic sign that gets added to OSM? Regarding the fact that only users are working on this system, I get your point. But you may also know that not so many people are interested in traffic signs, so there's nothing that we can do about this. I'm not a fan of taking people hostage and forcing them to read the several manuals of Spanish and Catalan traffic sign specifications, so I'm afraid that this situation may not change in the near future... xD At least, two people actively working for a standard is better than one. And in every debate and conversation that we've had on the Catalan community Telegram group chat so far, no one has opposed this standard so far.
In OSM there are many things that are regional and national-specific.
It makes no sense to involve the international community in something that is Catalonia-specific. But still, if international feedback comes our way, we'll consider it and implement it if we find it useful. It's true that debates in changeset comments are hard, but again, here's the forum thread where we can discuss this better:
And here is the WIP wiki page of this standard (everything that I told you about the tagging system is also here):
|
| 164056335 | 9 months ago | Heyas again!
As I told you in the previous commit, this push of traffic signs that I'm doing lately is for the Catalan traffic sign tagging system. Fortunately for you, now this tagging system has a forum discussion page here where we are working out the final bits of the standard:
And the wiki documentation page is being worked on here:
The wiki documentation contains a big table with a bunch of Spanish and Catalan destination signs and examples of how they are tagged. International traffic signs are also shown as additional samples (despite this tagging scheme only covering Catalonia for now). As you can see, the tags for marking the destinations are based of the tags used in the Relation:destination_sign (osm.wiki/Relation:destination_sign#Tags). In our standard we use tags like "destination", "distance", "colour:back", "colour:text", "colour:arrow", "destination:ref", "destination:symbol"... If the destination sign is structured like a list of more than one destination, we add numbers to the end of the above tags (":1" or nothing for the first and main destination, ":2" for the second, ":3" for the third, and so on). If a destination text is too long for a single line, and it occupies more than one line in the sign, we place each line in a ":a" and ":b" tags. This also helps for references and icons where there are more than one in a single line, where they also get the letter-at-the-end-of-the-number treatment. On roundabout signs, where there's a list of destinations per each exit of the roundabout, we place the direction of the exit before the number, via the tags ":through:", ":slight_right:", ":right:", ":sharp_right:", ":u_turn:", ":sharp_left:", ":left:" and ":slight_left:". The result is a system that can tackle every destination traffic sign that we've encountered so far, at the expense of being super tag verbose in the most complex signs. Feel free to deposit your feedback and opinions in English in the forum thread if you like. You may quickly realise upon glimpsing at the forum thread that we only talk yopaseopor and myself. That's because we are the only two users in the Catalan community that are traffic sign nerds and willing to work on their mapping and tagging. We've had debates about traffic signs on the OSM Catalan Telegram group.
Your argument of these new tags being "of no use to any other data consumer" is easily defeated with these two straightforward reasons:
Of course, that all of this is of no use to any data consumer, if there aren't any data consumers to begin with! If you want to join the conversation of this tagging scheme and deposit your opinion or provide feedback or whatever, feel free to come in the forum thread that I've linked above (you can talk in English, no worries, we don't bite) |
| 164056335 | 9 months ago | Bones! Les etiquetes road=ring_road i ring_road=yes les he posat per marcar que aquesta relació és una ronda que encercla la ciutat. He estat cercant per taginfo i per altres relacions de rondes d'OSM i no he trobat cap etiqueta que específicament marqui que certa relació de ruta és una ronda, així que he posat els dos ring_road per indicar-ho. No obstant, cert és que amb un ring_road sol ja és suficient.
Gràcies per l'avís i disculpa les molèsties! |
| 163358970 | 10 months ago | Hello again! This time these signs are properly tagged. The traffic signs added in this commit are using the "Traffic signs_ES" JOSM tag preset by yopaseopor.
This traffic sign tagging scheme is very complex and detailed, but this also causes it to be super verbose and state the obvious in many cases.
The fact of splitting values into different tags, makes them easier to edit and also, if in the future, the system for tagging traffic signs changes (again), then we would be able to easy adapt the current signs into the new system via automated edits; instead of having to potentially redo the signs because all the values were mixed. This explains the new tags, although this commit has added 3 different roundabout destination signs (one of them being the one you've linked), so I'm pretty sure that most of these tags are also in the other signs. The only other (simpler) standard for roundabout destination sign tagging that I know is the Spanish roundabout sign preset from the RoadSigns JOSM plugin (osm.wiki/JOSM/Plugins/RoadSigns).
destination:colour=blue|white|blue
For this sign, this preset works flawlessly. The tags are short and few, and everything fits perfectly. I really like how it looks, it's simple yet effective.
On the same roundabout, on the exit leaving the A-27 and entering the roundabout from the south, there's also this sign: - OSM node (mapped with the same preset as the one sign you've linked): node/12645203477#map=19/41.270094/1.232110&layers=N
You can see that the left roundabout exit has C-37 as the main road reference and Alcover as it's primary destination, but there's also a secondary reference of C-14 with Montblanc.
How would these references be tagged in the RoadSigns plugin? My guess would be "destination:ref=C-37;C-14|A-27|C-37", but such an approach will clash front-facing with other signs that have several primary references. Signs like this one: https://www.bing.com/maps/?cp=41.141731%7E1.233511&lvl=17.0&mo=om.1&pi=0.4&style=x&dir=213.3
This left roundabout exit goes towards Tarragona and has the road references of A-27, A-7 and T-11. This is because after the left roundabout exit, there's a brutally massive junction in which you can go to either A-27 (the main one that this roundabout connects to), the A-7 or the T-11, and you can enter Tarragona through any of these three. Following the RoadSigns plugin, it's destination:ref would look something like this: "destination:ref=A-27;A-7;T-11||A-27", and this tagging makes sense here, but now we still have the question of what to do the C-14 Montblanc case of the previously-mentioned sign.
Do you want another example of a complicated roundabout sign? Here's a big one: https://www.bing.com/maps/?cp=41.279575%7E1.257056&lvl=17.0&mo=om.1&pi=-3.2&style=x&dir=251.5
On this sign, the RoadSigns plugin would have problems rendering the white background of the left exit while being yellow for the secondary destination of Camp de Tarragona with the AVE symbol.
Representing this sign using the RoadSigns plugin would be impossible, or we would have to do a lot of compromises and "tag approximations" that then we would have to "decrypt and unroll" should we want to render this sign into an image or a model or interpret it for whatever reason or propose may arise. The approach of the RoadSigns plugin works well in simple signs, but unfortunately fails on the more complex ones. The current, by being verbose as heck, we have a chance to adapt it better to whatever surrealist painting of a sign comes. I don't know of any other traffic destination sign tagging system other than the one used here and the RoadSigns plugin, but if there is, it'll probably need more tags than normal for specifying these and all the edge cases that may arise, and then the current situation of new tags will also reappear. Sure, this complex tagging scheme is an overkill for simple signs like the one you've linked, but will be useful for better detailing the more complex signs. And there are many other tagging schemes in OSM that are overkill for very small features (for example: a very short bus/metro line that still needs plenty of tags for the ways, stations and relation about names, operators, networks, and such…). Traffic signs are very complex, there are many of them, and very different, so it makes sense that it's tagging system is also complex and detailed. And for your point of the Tarragona pier, plane and AVE symbols being all in different destination symbol tags, sort-of implying that there are all alone in new lines; I agree with you. Due to splitting values into their own tags, this also means placing values like those symbols in independent tags. Although, I suppose that there will be very little confusion; as it is highly unlikely that these symbols will be alone in their lines. I will probably change this in an upcoming commit, because I also don't like it much xD Sorry for such a massive reply. I hope that the examples that I provided help in understanding the logic of this scheme. |
| 163113395 | 10 months ago | I understand your logic behind some of your tag changes and rearrangements, but I disagree on some. The name fits a description better, true, but so are literally all the names of monuments, plaques and memorials. Very few memorials do have a "title" in it that is its official name. Many of those follow a scheme of "type of memorial + short description of it". Look around in OSM and you would see that the vast majority of memorials are mapped with a name, some may come from an official government memorial database. Never heard anything about the -t- thing; but I personally still prefer ":translation:". I think this will be an easier way for applications to drink this data easier, searching for "inscription:translation:XX" tags seems faster than deciphering "XX-t-XX" tags. This also is more clear to a human reading the tags that the contents are a translation to Spanish. About the "source:inscription:es" tag, sorry, my mistake. The "source:inscription:es" tag confused me because the tag ends with a Spanish ":es", but the language in the value is Catalan. Your "source:inscription:es" should be "source:inscription:translation:es", because the original inscription is not in Spanish, only the translation is. I'll revert the translation tag back to "inscription:translation:es", readd the name, move the source of the translation to "source:inscription:translation:es" and move the "inscription:translation:es:description:XX" to "description:XX". I like the sound of "inscription:translation:es:description:ca" xDD and I would like to add it also, but I guess that description will be more used, so I'll go with that for now. |
| 163113395 | 10 months ago | Hello! Your contributions of this changeset make no sense. You've moved the translated inscription to a new tag "inscription:es-t-la"
I've done it with the "inscription:translation:es" because in taginfo there's also previous usage of the inscription:translation tag (https://taginfo.openstreetmap.org/search?q=inscription%3Atranslation; it was used in a "inscription:translation:pl" before my changeset) specifically for "inscription".
Also, you've moved the name value to the description, deleted the multilingual descriptions and moved the Catalan description to the Spanish source (source:inscription:es). May I ask your logic behind these changes? |
| 161690713 | 11 months ago | Buenas! He revertido tus cambios en mi changeset/161710534 (changeset/161710534). Passatge d'en Gassó es una vía privada, cierto.
La página de la wiki "Limitations on mapping private information" (osm.wiki/Limitations_on_mapping_private_information) menciona que limitaciones y restricciones se aplican en el mapeado de propiedades privadas.
- "Mapping private buildings, private roads (including driveways), and private parking is completely acceptable. Add access (access)=private=* (access=private) as appropriate to roads, parking lots, etc. However, annoying artifacts may appear in applications like Pokémon Go with short driveways."
Tu acción de directamente eliminar vías privadas no cumple con estas directivas. Añadir un par de "access=private" y "barrier=fence" no cuesta nada y hace que el mapa este mas completo. |
| 161607477 | 11 months ago | Heyas! Thanks for pointing this out. Your comment has made me aware of how weirdly I mapped this sign.
This sign has nine panels of destinations with different arrows, text and icons each, so it would be impossible to condense all of this into 6-ish or so tags.
Also, looking at the tags it put out, it seems to combine roundabout-like exit with numbered destination panels in a weird way. I'll remove the tags and refactor this sign in an upcoming changeset. |
| 160313899 | about 1 year ago | Buenas! En este changeset has movido el nodo del survey_point NGW79 de Valls (nodo con ID 1142949994; node/1142949994). El problema es que este survey_point tenía highways conectadas y actuaba como intersección; y al mover el nodo, la intersección se ha movido y ha quedado desajustada. He hecho este changeset para arreglarlo (ID 160510112; changeset/160510112), donde he desconectado las vías del survey_point y las he reconectado a un nuevo nodo de intersección en el mismo sitio de antes. La causa de este problema ha estado muy probablemente por el hecho de que antes este survey_point estaba en medio de la calle y al trazar las vías de la zona se ha usado su nodo como nodo de intersección por el mero hecho de que el nodo ya estaba allí (aunque puede que parte de la culpa la tenga yo en base a unos edits de hace unos meses, ups… 😅). No te estoy echando la culpa de esto, ni de lejos. Solo te dejo este comentario para que no te estrañe si luego te sale mi changeset en el historial de dicho survey_point. Salutaciones y felices fiestas |
| 160509554 | about 1 year ago | Bones! Nope, el "hop=yes" es un typo; hauria de ser "shop=yes", disculpes 😅 He arreglat el typo amb aquest commit: changeset/160517321 Poso nodes com a "shop=yes" si no sé quin tipus de local és. En aquest cas hi ha un aparador gegant d'articles, però desconec del cert si és part del basar del costat o una tenda independent, no sembla que estigui retolat. Quan hi tombi per la zona, provaré de completar-ho. Gràcies per l'avís i disculpes! |