-
Notifications
You must be signed in to change notification settings - Fork 82
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
Improve sea maps #176
Improve sea maps #176
Conversation
Fantastic work mate! 😁 they all look excellent! |
OMG - that's all I have to say... 💯 |
Thanks for the kind words! In that case, I'll continue with:
|
Great improvements, many fixes. Also I'm glad that the map of the White Sea no longer contains spoilers. |
Some further updates. Comparisons below the fold (to avoid clogging up space): ug-map-coral_sea.pngug-map-east_siberian_sea.pngug-map-gulf_of_carpentaria.pngug-map-gulf_of_thailand.pngug-map-philippine_sea.pngug-map-sea_of_japan.pngug-map-south_china_sea.pngug-map-tasman_sea.pngug-map-yellow_sea.pngI'm not quite sure about the East Siberian Sea — the old one, while inconsistent with the style of our remaining maps, is really quite nice. As before, feedback regarding cropping and zoom are very welcome. On the topic of the extent of the seas (which areas to highlight) I made the following decisions where the IHO 1953 Limits of Oceans and Seas didn't completely agree with Wikipedia, generally erring in favour of Wikipedia, if possible:
As you'll probably notice, the Bering Strait map hasn't been updated as Natural Earth Data doesn't describe it in the relevant shapefile. Remaining tasks:
|
Outstanding! 🎉🎉🎉 I feel like the ocean maps are satisfactory for the time being. They have their own style, but they're clean and consistent. So don't worry about them, I reckon 😉 The maps of the Pacific regions would indeed have to be replaced in another PR. Gosh... Looking forward to merging this. Good luck with the remaining items! |
I have no idea why the latest commit failed the checks (and what the third mysterious check actually is...). As an aside, in case this wasn't a deliberate choice (in order not to scare away new contributors, but have the relevant information somewhere under the hood — though access isn't exactly great), the "index" check will always succeed, irrespective of quote normalisation, since
will always return an exit code of 0. (If
(though I'm not sure whether having the check fail even in case of lack of normalisation is a good idea — if there were a "warning" status then it'd be great, but a failing build without particularly visible error messages (since GitHub doesn't seem to have the option) isn't very helpful)). |
Oh, and for easy reference the Aral Sea maps: The dotted line in Kazakhstan delineates the Baikonur Cosmodrome which is an area leased out to Russia. I think it's worth having, (I had deliberately not filtered it out from the Natural Earth dataset, as I had for some others (we don't need all the different borders between North and South Korea)) as it's a special, weird sort-of-border, but I'm also open to removing it, if it's undesirable/potentially confusing. |
I pushed a commit to fix a syntax issue in the workflow file last week. Perhaps a rebase would make that third check go away? I wasn't sure how to get the command to fail, so thanks for the tip! But I eventually thought it might as well not, as you suggest. In regard to the Aral sea map, I do feel the border of the Baikonur Cosmodrome does not need to be there, given the context. My first thought was that it was an old part of the sea, which didn't make sense but was nonetheless confusing. |
I found this interesting, but only if this info is added to the card, otherwise it's confusing. Sadly, Aral Sea looks even drier now in Google Maps (2019) than on Natural Earth map - I think they last updated it in 2012. |
I'll do a rebase (perhaps not today — probably tomorrow), though why didn't the third check come up after yesterday's commit? (I'm not expecting an answer :) — if I cared enough I'd e-mail github support as suggested in the check details, but hopefully it's just a one-off issue.)
I don't think the info could be added to the Aral Sea card, so I'll remove the border.
Yeah, you're right, but I don't have any easily accessible, fresher shapefiles. (According to the changelog the latest change is from 2018, and it did touch the lake shapefile, but it's quite likely they didn't update the Aral Sea border.) I think the cost-benefit analysis is definitely in favour of sticking with the existing one than trying to make a new one myself. |
Remove it if you want. I thought that "Country Info" field could be used for this info. |
Unfortunately, the Country info field appears on cards that don't have maps (e.g. Country > Capital), in which case the information would not make sense. |
Aral Sea doesn't have a capital or a flag so the only card is Map -> Country. Besides, the extra info could be added into the Map field right after the image. |
Yet 😉 |
I prefer removing the Baikonur Cosmodrome border info from the map, I don't think it adds anything useful. |
Haha true, silly me. Yeah, still think the information is not relevant anyway. |
See #1. Data from https://www.naturalearthdata.com/ was used. The intention was to follow the style of the location map scheme "X in its region" country maps as closely as possible.
The historical extent of the sea is hatched.
0027c99
to
7a9cb12
Compare
Rebased and Baikonur Cosmodrome border removed (from all the maps). I agree with you @mighty-cthulhu that the presence of the Baikonur Cosmodrome border is a fun fact. However, there are many possible interesting facts about the surroundings of the Aral Sea (any one of which might have been useful for remembering the Aral Sea), they can't be all included and there's no objective way of choosing only one of them, so we err on the side of not providing any. The Baikonur Cosmodrome border could only have been kept on the map if it could stand on its own, without explanation, like the border between China and Hong Kong's new territories (leased from China in 1898) definitely could have until 1997, or like the border between Panama and the Panama Canal Zone (leased out to the USA) arguably could have until 1979/1999, but the consensus here is that it can't. |
This results in better conformance with the IHO definition (and the "common sense" one, as well). https://doi.pangaea.de/10.1594/PANGAEA.777975 (This source wasn't used for most of the other sea maps, since: a) Converting from KML to SHP (or geojson) was messy. b) The limits of seas usually extended beyond the coast, in-land (which was not visible in the SVG and had no effect on the output PNG, but was still felt slightly "wrong"). c) Some of the seas had "incorrect" limits (e.g. Coral Sea, if I remember correctly).)
I'm not sure that the Celtic Sea map should be updated, as the old one is really nice and detailed (though FWIW according to the IHO the south-western limit is supposed to be a straight line). For easy comparison see here: I've also updated the English Channel map using the same source as used for the Celtic Sea map, so that it's slightly more accurate. (The Natural Earth Data was non-existent for the Celtic Sea and slightly wrong for the English Channel, so I used this. I explained the rationale for not using it for all the maps in a slightly over-long commit message.) I don't think that I'll have time to do the Bering Strait map properly in the next week or so, so I think it would make most sense for me to include it in a later, separate pull request. I also won't have time to "upstream" the SVGs from which the PNGs are being made, in the very near future, so I'll update Just in case anybody is curious here's the extremely messy spaghetti-code-like set of scripts for generating both the SVGs and the PNGs. Hopefully nobody other than me will ever need to look at the code. |
I much prefer the new Celtic map! I take it you're ready for me to click the Merge button!? |
Great! :)
Yes! (I've just briefly re-checked the whole pull-request, just in case, and didn't see any issues.) |
See #1.
Data from https://www.naturalearthdata.com/ was used.
The intention was to follow the style of the location map scheme "X in its region" country maps as closely as possible.
Comparison of maps before and after below the fold:
ug-map-adriatic_sea.png
ug-map-aegean_sea.png
ug-map-arabian_sea.png
ug-map-baltic_sea.png
ug-map-bay_of_bengal.png
ug-map-bay_of_biscay.png
ug-map-black_sea.png
ug-map-caribbean_sea.png
ug-map-caspian_sea.png
ug-map-denmark_strait.png
ug-map-english_channel.png
ug-map-gulf_of_california.png
ug-map-gulf_of_mexico.png
ug-map-hudson_bay.png
ug-map-labrador_sea.png
ug-map-mediterranean_sea.png
ug-map-norwegian_sea.png
ug-map-persian_gulf.png
ug-map-red_sea.png
ug-map-white_sea.png
As already mentioned in the linked issue, I used comparisons with data from the 1953 IHO publication, via visual comparison with the shapefiles from marineregions.com rendered with
mapshaper-gui
, and by reading the publication itself, in order to ascertain which sub-seas and bays were parts of "parent" seas. I usually double-checked with Wikipedia's pages for the relevant bodies, in case of doubt.Please point out all and any improvements, regarding style, cropping (choice of surrounding area to be displayed) or any other issues, since I now have an automated workflow, making modifications straightforward.
Ideally and ultimately, I'd like to "upstream" the source SVGs to Wikimedia, though I'll only do that once I've finished improving/modifying the maps, in order to avoid unnecessarily clogging up Wikimedia's servers with several versions of multiple ~ 5 MB files.