You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi danielsnider, I encountered a problem similar to rocklinsuv:, ,but I cannot use the same steps to solve the problem.
When I tried to run "sudo docker run -p 8080:8080 -d -t -v ~/mapproxy:/mapproxy danielsnider/mapproxy", it initially downloaded the docker image, and then returned a series of numbers and characters for the second time. For example, "5d23e78...". Then I checked the MapProxy demo http://127.0.0.1:8080/demo, but I could not get the picture of the map when I opened the webpage normally. I also currently live in a country without Google.. (><) Is there a solution to use topographic maps instead of Google Maps instead of WTMS?
The text was updated successfully, but these errors were encountered:
Hi danielsnider, I encountered a problem similar to rocklinsuv:, ,but I cannot use the same steps to solve the problem.
When I tried to run "sudo docker run -p 8080:8080 -d -t -v ~/mapproxy:/mapproxy danielsnider/mapproxy", it initially downloaded the docker image, and then returned a series of numbers and characters for the second time. For example, "5d23e78...". Then I checked the MapProxy demo http://127.0.0.1:8080/demo, but I could not get the picture of the map when I opened the webpage normally. I also currently live in a country without Google.. (><) Is there a solution to use topographic maps instead of Google Maps instead of WTMS?
The text was updated successfully, but these errors were encountered: