• 46 Posts
  • 625 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • It definitely shows lake names, it’s just limited to specific zoom levels, e.g. here you should see all the names of the Great Lakes: https://www.openstreetmap.org/#map=7%2F45.064%2F-81.758

    The source code of the renderer is here: https://github.com/gravitystorm/openstreetmap-carto

    And there is an issue about displaying sea and ocean names: https://github.com/gravitystorm/openstreetmap-carto/issues/2278

    Some comments from the issue:

    Rationale from @gravitystorm@m.gravitystorm.co.uk as an issue comment:

    We need to be careful with these labels, for a few reasons. Using a single point to represent an ocean is quite an oversimplification! These points are also arbitrarily placed, so mappers could get into endless edit wars about where to put them. Many mappers will use them as “labelling positions” rather than ensuring the position has some kind of geographic basis.

    The Arctic Ocean label is a good example. From the overpass screenshot I assume the node is outwith the range we render. Do we want just the bottom half of the label showing?

    Normally oceans and sea labels are “hand placed” by cartographers, since the challenge of automating the label placement is so high. But we can solve the technical challenges here; while doing so lets remember not to end up rendering “labelling nodes” by mistake.

    Another good reason why it’s a complex topic:

    The problem with mapping oceans and seas is verifiability - mapping them as nodes is the simplest way to have the tags, in particular the names in various languages, in the database (which are verifiable). The coordinates are essentially meaningless.

    Summary here:

    I think we have already established in the above discussion and in #2345 that we do not want to render sea and ocean labels based on mapper placed geometries from the OSM database (either nodes or polygons) and thereby have the map painted by mappers based on subjective preferences and the specifics of the labeling style here and the mercator projection.

    IMO there are two decent options:

    • render by combining the tagging from place nodes in OSM with hand placed labeling geometries based on cartographic considerations for this style (like done by Label oceans and large seas from a static file #2345). This is feasible for oceans but not for seas due to the number of features. Special consideration should be given to avoiding vandalism in combination with slow low zoom update cycles.
    • auto-generate labeling geometries based on place nodes and the (simplified) coastline geometry. This is more challenging but would scale better.

    In both variants i would only use place nodes to specifically discourage mappers from pointless polygon drawings. There is simply no case where for a sea or ocean a polygon is the most suitable way to map in OSM.




  • Koumbi Saleh, or Kumbi Saleh, is the site of a ruined ancient and medieval city in south east Mauritania that may have been the capital of the Ghana Empire.

    The discovery in 1913 of a 17th-century African chronicle that gave the name of the capital [of Ghana] as Koumbi led French archaeologists to the ruins at Koumbi Saleh. Excavations at the site have revealed the ruins of a large Muslim town with houses built of stone and a congregational mosque but no inscription to unambiguously identify the site as that of capital of Ghana.

    In recent years, the identification of Koumbi Saleh with the ‘city of Ghana’ described in the sources has been increasingly disputed by scholars.

    https://en.wikipedia.org/wiki/Koumbi_Saleh













  • Yeah, because it works? https://www.youtube.com/watch?v=nn2FB1P_Mn8

    Today I fixed a carrier’s router by simply rebooting it, something was messed up with port forwarding, everything looked good on the webui, but it didn’t worked correctly. Reboot, bam, works.

    As more things become “smart” (for the better or worse) and filled with microprocessors, it will become more common. Also it’s not just digital I remember some analog things could be helped by a reboot, the extra surge after a switch on can help some electrical components, waiting for capacitors to loose current can help.

    And electric toothbrushes are much older, the first patent was filed in 1937. 40 years ago it was 1985, cordless electric toothbrushes are with us since 1960s…

    And 40 years ago we couldn’t chat about an article with people on the other side of the planet, so I don’t really understand the comparison. Yes, Mr. Chen you are becoming older, as everyone else, wow, nice observation… The common workflows to fix your medieval daily things back in the day were different, obviously, we have different workflows now. I guess you couldn’t help your great-grandparent troubleshoot an issue with the gadgets of their time.

    An actual problem is in the last sentence of the blog post, and nor the author of the article, nor Mr. Chen thinks of this as a much more bigger problem:

    Oh, by the way, my attempts to reboot the electric toothbrush were unsuccessful. I had to replace it.

    That shouldn’t be a solution. ONLY AFTER RESTARTING SOME TIME? No other ways were tried to fix it? Did he tried too take it apart an look for some clear problems? You should be able to fix it. Maybe just the battery died? or if the battery is alright, you can reuse that in your next toothbrush. I would restart a thing a million times instead of throwing it out. They are yelling at the wrong thing, and ignore the elephant.