The first ones I noticed were originally mapped with the “Go map!” editor. So it seems likely that’s the curlpit.

They’re also very recent, so the bug likely is still around.

@arnielsewhere, what timing do you propose?

I believe the time has mainly been chosen to suit Europe and California. As OSM is still European for a big part, while most big tech companies are based in California.

When you’d take global population per time zone into account, it seems however that you need to focus on East-Asian, Indian en West-European/Central-African time zones.

If you consider those three regions, you indeed have a reasonable time frame to plan a meeting (from 6:00 to 13:00 UTC is acceptable for all involved).

However, if you still want to add the US at all, adding the eastern time zone leaves you with just one hour that’s feasible for all (13:00 UTC). If you want to add California (which is a valid request IMO, due to the amount of big-tech companies, even though the overall population isn’t that high), there are no common times to be found.

Compare times in timezones: https://www.timeanddate.com/worldclock/meetingtime.html?iso=20201214&p1=195&p2=176&p3=33&p4=179&p5=137

Oh, your name is Paul… right, sorry

I’m not sure what you mean by “Field number”. But if you think it’s valuable information, you can go ahead and map it. You shouldn’t be afraid to add stuff. I listed the only hard rules above, apart from that, it’s all just conventions we try to follow (without conventions, it would be very hard for data users).

If features have verifiable names or references, you can always slap on a generic name=*or ref=* tag (note that a name is not a description).

You may receive suggestions from other mappers in the region on how you’d better map something this or that way for this or that use case. But we’re normally very happy with any added information.