Skip to content
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

Merged
merged 5 commits into from
Dec 5, 2019
Merged

Improve sea maps #176

merged 5 commits into from
Dec 5, 2019

Conversation

aplaice
Copy link
Collaborator

@aplaice aplaice commented Nov 22, 2019

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

before

after

ug-map-aegean_sea.png

before

after

ug-map-arabian_sea.png

before

after

ug-map-baltic_sea.png

before

after

ug-map-bay_of_bengal.png

before

after

ug-map-bay_of_biscay.png

before

after

ug-map-black_sea.png

before

after

ug-map-caribbean_sea.png

before

after

ug-map-caspian_sea.png

before

after

ug-map-denmark_strait.png

before

after

ug-map-english_channel.png

before

after

ug-map-gulf_of_california.png

before

after

ug-map-gulf_of_mexico.png

before

after

ug-map-hudson_bay.png

before

after

ug-map-labrador_sea.png

before

after

ug-map-mediterranean_sea.png

before

after

ug-map-norwegian_sea.png

before

after

ug-map-persian_gulf.png

before

after

ug-map-red_sea.png

before

after

ug-map-white_sea.png

before

after

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.

@aplaice aplaice changed the title Improve seas near the Atlantic and Indian Oceans Improve sea maps [WIP] Nov 22, 2019
@ohare93
Copy link
Member

ohare93 commented Nov 23, 2019

Fantastic work mate! 😁 they all look excellent!

@axelboc
Copy link
Collaborator

axelboc commented Nov 23, 2019

OMG - that's all I have to say... 💯

@axelboc axelboc added the content Content changes, map improvements, translation fixes, etc. label Nov 23, 2019
@axelboc axelboc added this to the v3.3 milestone Nov 23, 2019
@aplaice
Copy link
Collaborator Author

aplaice commented Nov 23, 2019

Thanks for the kind words!

In that case, I'll continue with:

  1. The "Pacific-adjacent" seas, once I figure out how to re-cut the shapefiles at a different longitude, most cleanly (so that the map can be centred at a different longitude, to avoid the distortion present near the "edges" of the Winkel III projection).

  2. The Aral sea, for which I think it would be nice to have its current area superimposed on the historic one. (Natural Earth Data's "historic lakes" contains the necessary data, so it should be straightforward.)

@mighty-cthulhu
Copy link

Great improvements, many fixes. Also I'm glad that the map of the White Sea no longer contains spoilers.

@axelboc
Copy link
Collaborator

axelboc commented Nov 24, 2019

@aplaice
Copy link
Collaborator Author

aplaice commented Nov 30, 2019

Some further updates. Comparisons below the fold (to avoid clogging up space):

ug-map-coral_sea.png

before

after

ug-map-east_siberian_sea.png

before

after

ug-map-gulf_of_carpentaria.png

before

after

ug-map-gulf_of_thailand.png

before

after

ug-map-philippine_sea.png

before

after

ug-map-sea_of_japan.png

before

after

ug-map-south_china_sea.png

before

after

ug-map-tasman_sea.png

before

after

ug-map-yellow_sea.png

before

after

I'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:

  1. Philippine Sea. According to the IHO 1953 "specification" (and also the latest, still unaccepted draft from 2002) all the inland Philippine seas (e.g. Bohol Sea, Sibuyan Sea etc.) are part of the Philippine Sea. Wikipedia disagrees, unambiguously placing only the Leyte Gulf and Dinagat Sound within the Philippine Sea. Wikipedia is not clear on whether the Davao Gulf belongs to the Philippine Sea, but I included it, anyway as it makes the map look nicer. (For the record, Britannica seems to agree with Wikipedia.)

  2. Sea of Japan. It's not clear whether the Tsugaru Strait is part of the sea of Japan. IHO says that it is, Wikipedia isn't clear, so I included it.

  3. South China Sea. IHO (1953) includes all of Taiwan Strait, Gulf of Tonkin, Qiongzhou Strait and Natuna Sea within the South China Sea. IHO (1986 (draft) and 2002 (draft)) don't. Wikipedia hedges, quoting both. I followed the (approved) 1953 version.

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:

  1. Aral Sea map (with historical and current extent) — should be relatively straightforward as Natural Earth contains the needed data.

  2. (?) Celtic Sea — not in Natural Earth, so will try to pull in from here (though my previous experience with this source wasn't great). The current map is quite nice, if inconsistent.

  3. (?) Bering Strait — not in any of the shapefiles I had looked at until now, so would have to do it from scratch (but a strait with two straight edges should be doable). The current map isn't bad.

  4. (?) Oceans — these should be straightforward, but I'm not sure whether they need replacing and what style would be best. Perhaps something analogous to the current continent maps (e.g. Asia) would work?

  5. (?) The island areas of the Pacific Ocean. Perhaps since the style would have to be different from everything else we have, anyway (we don't have a style for highlighting areas containing both seas and land) the maps found by @OldOxygen in Vectorized ocean maps #136 could be used. (Polynesia, Micronesia and Melanesia.) The single best "upstream" Wikimedia source seems to be here. Though if we do do that, it should probably be in a separate pull request as it's partially unrelated.

  6. Get things upstream to Wikimedia (ideally I should get in contact with somebody at the Map Workshop so that I know what norms to follow before dumping tens of huge SVG maps onto Wikimedia...) Merging this pull request probably shouldn't have to wait on this step, though.

@axelboc
Copy link
Collaborator

axelboc commented Dec 1, 2019

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!

@aplaice
Copy link
Collaborator Author

aplaice commented Dec 1, 2019

I have no idea why the latest commit failed the checks (and what the third mysterious check actually is...). src/data.csv does not indeed follow quote normalisation, but that was also the case for the previous commits, as well as the-then master (and the relevant check is the "index" one, anyway).


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

git diff-index --quiet HEAD -- || echo "You need to run \`composer index\`"

will always return an exit code of 0. (If git diff-index ... returns a code of 1, then echo ... is run, which will always succeed, giving a code of 0.) If having the check fail when src/data.csv isn't normalised was the intention then perhaps we could have something like:

git diff-index --quiet HEAD -- || (echo "You need to run \`composer index\`"; exit 1)

(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)).

@aplaice
Copy link
Collaborator Author

aplaice commented Dec 1, 2019

Oh, and for easy reference the Aral Sea maps:

before

after

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.

@axelboc
Copy link
Collaborator

axelboc commented Dec 1, 2019

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.

@mighty-cthulhu
Copy link

The dotted line in Kazakhstan delineates the Baikonur Cosmodrome which is an area leased out to Russia.

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.

@aplaice
Copy link
Collaborator Author

aplaice commented Dec 1, 2019

Perhaps a rebase would make that third check go away?

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 do feel the border of the Baikonur Cosmodrome does not need to be there, given the context.

I found this interesting, but only if this info is added to the card, otherwise it's confusing.

I don't think the info could be added to the Aral Sea card, so I'll remove the border.

Sadly, Aral Sea looks even drier now in Google Maps (2019) than on Natural Earth map - I think they last updated it in 2012.

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.

@mighty-cthulhu
Copy link

mighty-cthulhu commented Dec 1, 2019

I don't think the info could be added to the Aral Sea card, so I'll remove the border.

Remove it if you want. I thought that "Country Info" field could be used for this info.

@axelboc
Copy link
Collaborator

axelboc commented Dec 2, 2019

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.

@mighty-cthulhu
Copy link

mighty-cthulhu commented Dec 2, 2019

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.

@ohare93
Copy link
Member

ohare93 commented Dec 2, 2019

Aral Sea doesn't have a capital or a flag

Yet 😉

@ohare93
Copy link
Member

ohare93 commented Dec 2, 2019

I prefer removing the Baikonur Cosmodrome border info from the map, I don't think it adds anything useful.

@axelboc
Copy link
Collaborator

axelboc commented Dec 2, 2019

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.
@aplaice
Copy link
Collaborator Author

aplaice commented Dec 2, 2019

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).)
@aplaice
Copy link
Collaborator Author

aplaice commented Dec 5, 2019

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:

before

after

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 sources.csv appropriately once I do, in another, future pull request.

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.

@aplaice aplaice changed the title Improve sea maps [WIP] Improve sea maps Dec 5, 2019
@axelboc
Copy link
Collaborator

axelboc commented Dec 5, 2019

I much prefer the new Celtic map!

I take it you're ready for me to click the Merge button!?

@aplaice
Copy link
Collaborator Author

aplaice commented Dec 5, 2019

I much prefer the new Celtic map!

Great! :)

I take it you're ready for me to click the Merge button!?

Yes! (I've just briefly re-checked the whole pull-request, just in case, and didn't see any issues.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Content changes, map improvements, translation fixes, etc.
Development

Successfully merging this pull request may close these issues.

4 participants