That seems like an arbitrary rule that you just made up.

That sounds like a silly idea. This changeset groups the change topically. +1 for topic grouped changesets.

I feel like this is a pretty focused changeset: Aldis. It's silly to break it up geographically, when it's grouped topically. -1 to smaller changest area suggestion.

Thanks!

Thanks!

Hey SekeRob,

Sorry that I came off confrontational. I have been dealing with a lot of mailing list people who are "no global edits" ever kind of people which really rubs me the wrong way. Not an excuse but a frame of reference.

I agree with you that global edits should be carefully considered. I think we shouldn't be so scared of them... but that doesn't mean we should forgo caution as you highlight. If they are annoying to rollback, then we should improve our rollback software.

Also as you say we need to attack these kind of edits from two places. One from the dataset side, and one from the generation side. "Why is ID still recommending these tags".

Additionally, you raise an excellent point that we should get consumers in on the loop. If we could focus our effort on items which are annoying for data consumers that could help. Although to be honest for a new data consumer, the less variation we have the less the initial hurdle.

In summary, I think we don't actually have such differing opinions, and I apologize again for coming off in an accusatory manner.

Blame the changeset viewing representation not the edit.

Global edits need to happen sometimes, and it a ridiculous request to split them up into arbitrary units to make people who hate big boxes happy.

File a issue with whatever software you use's github asking them to allow you to hide global edits if you don't want to see them.

Regarding the actual tag. Payments:debit_card, is more precise than nothing. It means that they at least accept some debit cards. Without that tag you could assume that no debit cards are supported. One could conjecture that local debit cards could be used if they saw a "yes" flag.

Does payment:coins need to say "No 10 cent coins allowed" to be useful, no. It would be great, but it's not the bar for adding information.

Is this correct? 日本 is not a "county" as far as I know, it is a Country.

Hello ymrunali,

Thanks for your prompt response! Yes I understand these kind of things can take time. I hope you're able to find the license, as this data would be great to have if we're allowed.

Kind regards,
Zaneo

Sorry can you cite the license for this? I mean specifically, not generally. Where is the linked waiver or license that allows this to be utilized in OSM which may be used commercially.

Hey your source says survey... that usually means visiting the places. Or utilizing a survey performed at that location (with a link to said report). Is it correct that you've visited these places?

Net error ate this changeset.

Are there any reliable tools for determining which "state" a node belongs too? (On a global level).

Or is it something like:
Query all the administrative boundaries. Find out what level is state in each country. Find if the node is enclosed in the polygon of the administrative boundary?

Specifically addressing this point:

>Just because people don't comment on your changesets doesn't mean they completely approve of you making giant multi-continent bounding boxes.

If people don't raise issues they have, then they can't be upset when those issues aren't considered.

About large bounding boxes. Taking the max and min lat/long of changes and drawing a box is not the greatest way to highlight area affected. Using a rotated rect could show very differently results for a long thin diagonal edit.

Or within the changeset box, highlighting some areas where change was actually affected.

My opinion about large bounding box issues is that they are a problem of the tools, not the act. Review tools that don't properly highlight the changes are causing mappers to get freaked out.

This changeset is a little large in area. If possible it's better to commit changesets in the local area affected. The clinic in the top left is unrelated to the edits in Tokyo, so it creates a very large edit bounding box.

少し大きいですね。関係ない物は別々での方が良いと思います。

I'd like to help update Toyama. I don't want to accidentally affect work you've done. Would it be possible for you to consider slightly more descriptive changeset comments?

Thanks! Sorry I made such a mistake.

Out of curiosity is way/327062054 supposed to be something?

Why does this edit a node in Japan on a storage tank?