CAM-Gerlach's Comments
| Changeset | When | Comment |
|---|---|---|
| 183949992 | Reverted adding a building >1000x times in the ~same spot in changeset/183961542 |
|
| 183949992 | > there should only be one object per building for the most part. for more info see osm.wiki/Buildings and osm.wiki/One_feature,_one_OSM_element for more info. NB, it's all but certain that it was some sort of process or tooling error rather than a mapper deliberately doing this (assuming its not intentional vandalism). Perhaps maybe something related to an import of the descriptively named "unknown.geojson" mentioned in the "imagery_used". |
|
| 183950140 | Reverted adding a building >1000x times in the ~same spot in changeset/183961490 |
|
| 175706279 | Cleaned up remaining SEO spam and fixed tagging for POI in changeset/183950799 |
|
| 163755012 | That said, I don't go around changing it willy nilly unless I'm already editing a POI for other more substantive reasons, usually cause my autofixer catches it. So probably not worth another changeset here unless you really want. |
|
| 183942256 | See comment on the previous changeset: changeset/163755012#c1606407 |
|
| 163755012 | Thanks! Oops, I missed the other dash as I don't have my NANP phone number validators/autofixers enabled in my Revert profile in JOSM since I clean up SEO spam all over the world. However, it is _still_ not quite correct, actually 😅. I used to use `+1 NNN-NNN-NNNN` myself because it was mentioned on a wiki page and it was (accordingly) the default for the JOSM phone number plugin, but it turned out that wiki mention was just one mapper misinterpreting the consensus of an old discussion, and last year the wiki was updated to reflect the actual consensus of that discussion for `+1-NNN-NNN-NNNN` phone=*#United_States , and that is what most tools use/enforce now (e.g. confusedbuffalo's site and bot, watmelon's JOSM validators/autofixers, etc; JOSM phone number plugin hasn't released a new update yet). See also the canonical community discussion https://community.openstreetmap.org/t/phone-tag-formatting-in-the-us-1-nxx-nxx-xxxx-vs-1-nxx-nxx-xxxx-vs/104117 and specifically https://community.openstreetmap.org/t/proposed-automated-edit-of-phone-numbers-in-the-usa/138163/53 |
|
| 134017574 | Cleaned up remaining SEO spam tags for Underwood Law Firm - Oakland POI in changeset/183767400 |
|
| 134162331 | Cleaned up remaining SEO spam tags for Underwood Law Firm - Oakland POI in changeset/183767400 |
|
| 183725431 | No worries, thanks for the response--just wanted to give you a heads up. Cheers! |
|
| 183725431 | Hi Ygramul, thanks for refining the geometry here. Unfortunately, it seems like the way the turning loop was attached to, correctly tagging this as a private driveway, was completely removed, and instead this was tagged as part of the public right of way of Heritage Lane. In fact, VBMP aerial imagery, VGIN property lines and street-level imagery all confirm that this turning circle is in fact part of the private driveway of the house at 2804 Heritage Lane, as it was tagged previously. I went ahead and restored the removed way and tagging, as well as further refined the way's tags and geometry, in changeset/183757424 , so this should be fixed now. Just wanted to give you a heads up about that. Happy mapping! |
|
| 182550231 | Hmm, I see--thanks for explaining. As far as I'm aware, craft=* is considered a top-level tag on its own osm.wiki/Top-level_tag#For_standalone_elements and I normally see it used as such, with only <20% of uses worldwide featuring another top-level "classification" type tag (including 5% having shop=* and 1% having office=*) https://taginfo.openstreetmap.org/keys/?key=craft#combinations Checking AUS specifically, the overall proportions are only a little higher at ~20%, with 7.9% having shop=* and 2.8% having office=* https://taginfo.geofabrik.de/australia-oceania:australia/keys/craft#combinations . I can see some benefit in this case if you also choose to use a tag like craft=rug_cleaner with only 2 uses worldwide, given it seems highly unlikely any data consumer would ever support it unless it sees at least a few orders of magnitude more uptake, so they could still fall back to something. Wouldn't be how I'd personally choose to map, but ATYL of course. > For you business > render your company Err, I'm just the mapper that reverted the addition of this SEO spam POI, not the SEO spam operation sockpuppet that added this 😅 ( @CAM-Gerlach is my main mapping account, @CAM-Gerlach_Revert is for reverting SEO spam changesets like this) |
|
| 183691922 | Looks good to me, modulo any Swiss local convention on POIs/addresses that I'm unaware of. Thanks! |
|
| 182550231 | Thanks @nevw ! Just curious--is office=company redundant with craft=cleaning as a top-level tag? Or is there a reason one might add both? |
|
| 183534285 | Its not "my" map, I'm just a community volunteer like everyone else (and not a local mapper like yourself). Unlike the big Western mapping companies, the data in OpenStreetMap is created and edited by the local community who live in and work in each place, so if you see something that could be improved, like I've said before you are more than welcome to leave a note for local mappers, or even fix it directly yourself (after checking with the local community). |
|
| 177215275 | Dale, pero como es que tu respondiste solo cuado yo hice un revert de tus cambios, y no en los cinco mesas desde cuando Dani te pido que pongas una tag superior en tu POI? Sin una tag superior, tus cambios son sin sintido para usarios de OpenStreetMap y no le serve nada pero el "SEO spam". Puedes hacer tus cambios otra vez, pero necesitas incluir una tag superior como amenity=dentist (y tambien healthcare=dentist ), y no el description=*, o sera reverted otra vez. Gracias. |
|
| 183534285 | Given most of your claims don't make any sense given what either of us actually changed, I suspect you have somehow confused my changes here with something else entirely. I highly recommend the Better-OSM-org user script that shows much more clearly what changed, or if not using OSMCha to view this changeset: https://osmcha.org/changesets/183534285 > Thứ nhất: Theo Nghị quyết số 202/2025/QH15, sau khi sắp xếp, cả nước có 34 đơn vị hành chính cấp tỉnh (gồm 28 tỉnh và 06 thành phố trực thuộc Trung ương) thì tỉnh Bình Thuận không còn trên bản đồ. Sorry, but how does that have anything to do with either your changesets or this changeset reverting them? Nothing in your changes so much as referred to "Bình Thuận" anywhere I can see, much less changed anything to do with provincial naming. Of course, if there are other changes you want to see on the map, you are welcome to update it accordingly, after consulting with the local Viet Namese mapping community and carefully following all OSM guidelines, conventions and good practices. If you don't want to make the changes yourself, you are welcome to leave an OSM note describing them in detail and linking to sources, for otherm mappers to reference in teh future. > Thứ 2: Đường mà mấy ông ghi là đường ven biển là hoàn toàn sai, nó là đường ĐT716B Again, neither your changesets nor mine reverting them touched any roads whatsoever, nor even changed the addr:street=* tag on existing objects, so your claim that "I" somehow labeled some road as such doesn't make sense. Furthermore, I see the road running through this area is already tagged according to what you said, as ref=ĐT.716 . If you believe the name=* does not match either signage, addresses or widespread usage and have sources to support that, you are free to update it or at least add a note describing it in detail (though I would strongly recommend consulting with other local mappers first before such major changes). > Thứ 3: Tôi định vị vị trí của "Công ty" tôi trên bản đồ nhằm mục đích chỉ đường chứ không phải SEO như ông nói. SEO spam on OSM is defined by its characteristics, not by intent. Your account was issued an official warning by the OSM administrators due to promotional SEO spam on its profile, More directly relevant to this changeset, both the description=* tag and the note=* tag contained rather blatant SEO self-promotion, which is strictly prohibited on OSM and was one reason for it being reverted per OSM policy. See e.g. osm.wiki/Spam#SEO_Spam : > Often the Changeset Description and Description tag contain marketing hype. Marketing hype is not objectively verifiable and breaks one of OSM's key criteria of verifiability. Unverifiable claims should be deleted And description=* description=*#No_advertising : > The description should only include neutral and factual information about the object. It should not include subjective evaluations, e.g. "the best restaurant in town", "modern, comfortable hotel, in the heart of the city". Do not use description=* for advertising messages. They will be removed as spam and may also have further consequences for your OSM account. > Thứ 4: Hiện tại chỉ có google maps họ mới cập nhật lại và đúng với Quy định về tên đường địa chỉ của Nhà nước Việt Nam theo Nghị quyết mới. Once again, neither your changes, this revert or the reasons for it involved anything to do with road names nor addresses. If you believe they should be updated and have independent, allowable sources for that information (e.g. official government documents/websites), you can leave a detailed OSM Note, or update them yourself after consulting with your local community. Do note that copying from Google Maps (or other maps or sources that aren't explicitly license-compatible with OSM) to update them is strictly prohibited and may be a violation of local and international copyright law. The issue that is relevant here is the fact that your changeset directly references Google Maps and appeared to be at least partially based on Google Maps data, judging from the image=* tag as well as your comments referencing it and directly alluding to that fact. Therefore, per copyright law and OSM policy it had to be immediately reverted (in addition to the promotional content). > Fifth: You should familiarize yourself with these recent changes—particularly the updated road names—to ensure accuracy and provide correct information to users. Unlike yourself, I am not a local mapper this area, so I neither have the responsibility to nor would it be appropriate for me to make such changes, I just go around the world cleaning up spam and promotion. You, on the other hand, are once again more than welcome to make such changes after consultation with the Viet Namese mapping community, or leave a note for other local mappers describing in detail what you think should be changed, why, and links to appropriate allowable sources. Best of luck. |
|
| 183534285 | Indeed, that's great advice for other SEO accounts like yours. And yup, exactly--as the changeset message states, this revert was performed due to likely copying data off Google Maps, as you verified now. Thanks for understanding! |
|
| 182304334 | Hi, so instead of adding the restaurant as a POI (i.e. a node) inside of the ice rink building, as your description=* describes it to be, this changeset instead inexplicably removed the leisure=ice_rink tag from the entire building (as well the also-valid nysgissam:nysaddresspointid=MONR016200 import tag used for future update tracking), and instead tagged the entire building as just your restaurant, which is of course not correct and which I fixed for you in my changeset by splitting the tags for your restaurant to a separate node. See also osm.wiki/One_feature,_one_OSM_element Additionally, the description=* tag contained rather blatant SEO spam self-promotion, which is strictly prohibited on OSM, so I removed it. See e.g. osm.wiki/Spam#SEO_Spam : > Often the Changeset Description and Description tag contain marketing hype. Marketing hype is not objectively verifiable and breaks one of OSM's key criteria of verifiability. Unverifiable claims should be deleted And description=* : > The description should only include neutral and factual information about the object. It should not include subjective evaluations, e.g. "the best restaurant in town", "modern, comfortable hotel, in the heart of the city". Do not use description=* for advertising messages. They will be removed as spam and may also have further consequences for your OSM account. I considered at least trimming down the SEO spammy list of many different cuisine=* s, but perhaps against my better judgment decided to leave it. Also, the building was unsquared and the service road intersected with it, so I fixed those issues for you as well. For full details on exactly what I changed, see the above-linked changeset--if you don't have the recommended Better-OSM.org user script installed osm.wiki/Better-osm-org the default OSM.org changeset view is pretty useless, but you can browse it on OSMCha instead: https://osmcha.org/changesets/183533993 Additionally, the added phone=* was malformed (which a bot fixed for you), and this changeset inexplicably added your restaurant to the Erie Canal Water Trail relation (an not-uncommon SEO spammer tactic), breaking it. Fortunately, @scarapella generously fixed it for you in changeset/183533993 changeset/183533993 ( https://osmcha.org/changesets/183533993 ). Normally, any one of the major issues above by a SEO account would have been grounds for a wholesale revert per OSM DWG guidance, but as the relation damage (and phone number) had already been fixed and your other tags were valid I went ahead and fixed everything else for you this time. Happy mapping. |
|
| 181990922 | Thanks, but I see you still haven't removed the copious promotional marketing copy on your user profile as you were required to do as a condition of your block osm.org/user_blocks/20488 |