-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
OSM Tiles show error message while obtaining them from OSM #838
Comments
Sorry I cannot fix this. Seems OSM is broken. Use another map theme or contact https://www.openstreetmap.org or https://en.wikipedia.org/wiki/User:TheDJ Alex |
Ah ok, my assumption was that there is a technical user used by you which was disabled. Thanks for the quick reply! :-) |
Update: This is related to the hillshading. Uncheck the button on the toolbar or in menu "View" -> "Show Hillshading" You can use OpenTopoMap or StamenTerrain map themes which do not require a separate hillshading source since it is included in the map images. Or use these as and alternative: Alex |
Reopening since this is a real issue. I probably have to remove the hillshading soon because there is no alternative available. And thank you for the report! Alex |
Seems that the "DJ" gave up on maintenance of the service since it is something he does "not enjoy". 🤦♂️ 🙄 |
There is no replacement for this service but I added more maps with #85 |
Closes #838 # Conflicts: # src/common/mapflags.h # src/gui/mainwindow.cpp # src/mapgui/mapwidget.cpp
LNM 2.6.17, Win 10 21H2
Started LNM just now centered on airport 2A2 (Holley Mountain), with OpenStreetMap as tile server. Instead of showing the tiles a message is shown on each (uncached?) tile:
Contact [User:TheDJ]] if you want to maintain OSMdb and/or the wmflabs' OSM tiles server.
Crosschecked this on openstreetmap.org with all available six layers: all layers work properly. Possibly a deactivated OSM account?
See also here (screenshot snippet). Logfile from today also attached
abarthel-little_navmap.log
)
The text was updated successfully, but these errors were encountered: