Mapping Languages

Noting that you have latitude and longitude metadata for languages, you can easily plot the languages on a map to show off the world distribution of languages supported.

This adds a dependency, but would help make for an easier way in to discovering languages by region?

In a Jupyter notebook:

import folium

m = folium.Map()

for lang in list(LANGUAGES):
    folium.Marker(location=[LANGUAGES[lang].latitude, LANGUAGES[lang].longitude],
                            popup=f'{LANGUAGES[lang].name} ({lang})').add_to(m)

m

This approach might also be useful just as a quick check to make sure that markers look about right on the map…

[kylepjohnson]

I pulled this code out for a presentation and it worked really well. Recording here for posterity.

from cltk.languages.glottolog import LANGUAGES
import folium

# example tiles:
# https://leaflet-extras.github.io/leaflet-providers/preview/

attribution = 'Map tiles by <a href="http://stamen.com">Stamen Design</a>, <a href="http://creativecommons.org/licenses/by/3.0">CC BY 3.0</a> &mdash; Map data &copy; <a href="https://www.openstreetmap.org/copyright">OpenStreetMap</a> contributors'

_map = folium.Map(location=[32.535164526, 44.41916499], zoom_start=2, 
                  tiles="https://stamen-tiles-{s}.a.ssl.fastly.net/terrain-background/{z}/{x}/{y}{r}.png",
                  attr=attribution,
                 )

for name, lang_obj in LANGUAGES.items():
    folium.Circle(
        radius=400,
        location=[lang_obj.latitude, lang_obj.longitude],
        popup=f"<i>{lang_obj.name}</i>",
        tooltip=f"{lang_obj.name} (\"{lang_obj.iso_639_3_code}\")",
        color="crimson",
        fill=False,
    ).add_to(_map)

_map.save("glottolog-map.html")
_map

[psychemedia]

@kylepjohnson I guess my use case is more related to how cltk can be used to support authoring of simple learning materials, both from authoring and student activity perspective. To that end, the use cases will verge on the “not interesting” to folk developing cltk for research purposes, although they may help provide an on ramp. If there are other simple-but-useful things I’m missing, if you let me know I can try to write examples around them.

(You’re welcome to take the material for use as docs - they should be appropriately licensed. If not, I hereby grant cltk org a CC0 license with the rider that you at least CC-BY (or similar) them with at least a cltk attribution. I’m sorry I can’t commit to adding to your docs directly at the moment; I’m trying to cover a lot of other bases too so I’m working at a “good enough for a demo” rather than “strictly correct” documentation level…)