What's up with that

  • invalidusernamelol [he/him]
    ·
    2 years ago

    This is actually just a bug in Google's data, the OSM boundaries are fine. Google is probably using river boundary shapes and merging improperly them together creating this issue

      • invalidusernamelol [he/him]
        ·
        2 years ago

        Hell yeah, what's great is that the local GIS services there are probably all totally conflicting