-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asia/Shanghai Asia/Taipei overlap #52
Comments
I'll admit I'm not an expert in this border dispute or really any border disputes. I suppose the actual deciding factor for this project should be the actual timekeeping method that is officially used in certain areas. Is it the case that all of these overlapping areas do in fact officially use timezone-boundary-builder/expectedZoneOverlaps.json Lines 71 to 85 in 699b412
|
Yes they use Asia/Taipei |
Ok, so what you're proposing is to have all parts of Taiwan ( |
I would need to know what is the coordinate defined for Taiwan and China in OSM database to say for sure is it the case but I am not sure how to retrieve that using the overpass turbo interface. |
Here is a link to the overpass query for Taiwan: http://overpass-turbo.eu/s/DLk And here is China: http://overpass-turbo.eu/s/DLm |
From the look of it, having all parts of Taiwan (Asia/Taipei) take precedence over any areas where they overlap with China (Asia/Shanghai) appears to be the correct move. There are some problems with the exact area chosen by OSM data but I guess they should be fixed in OSM instead, as in:
|
This is some really good research here! It definitely would be great to have that red line of the forbidden zone be a part of OSM. I'll go ahead and add an operation to the boundary building process that diffs areas considered Taiwan from China. If/when someone adds those water boundaries to OSM, they should get pulled in as part of a future update. |
Those overlap are not necessary. These islands are disputed, but they are just being disputed in the same way as the entire territory of Taiwan is being disputed.
The text was updated successfully, but these errors were encountered: