-
Notifications
You must be signed in to change notification settings - Fork 4
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
add ALKIS s/w map #13
Conversation
Hi @karlbeecken we could do that, yes. I am a bit hesitant since both versions are super similar and will use up the same resources (disc space, processing time). Would your usecase allow to apply a grayscale css effect on the colored layer, which should result in a similar result. For example like this https://github.com/zlant/parking-lanes/search?q=mapnik_gray |
Hi, my usecase is using the tiles as a base layer in uMap, so as far as I can tell that isn't easily possible. Also the gray layer provided by the FIS Broker has better contrast than just grayscaling the colored one (e.g. the trees are a very light green, that would result in a light gray grayscaled version – the native gray map however has the trees black). How many ressources would you estimate to be needed? Maybe I can just host it myself? |
We can add the layer and see how it goes.
There is probably a way to calculate that but I don't know how. It depends on your bbox and how many zoom levels you want to support. You could try setting up this project locally https://github.com/codeforberlin/mapproxy-config#install and do a test. That would also help with testing the zoom 20-issue. I don't never had a local instance running. |
It should be relatively easy to set up locally if you have Linux, a Mac or the subsystem for linux on a Windows machine. |
I tried setting it up on an Ubuntu 20.04 server yesterday according to the manual in the README, and it runs without error messages, but every tile returned is just a white png. Instance is running under https://umap.dmho.de/proxy/ |
It does work (now), looking at https://supaplexosm.github.io/strassenraumkarte-neukoelln/mapproxy_demo_map.html?url=https://umap.dmho.de/proxy/tiles/1.0.0/alkis_30/mercator/{z}/{x}/{y}.png#18/52.48209/13.44155 and an example image at https://umap.dmho.de/proxy/tiles/1.0.0/alkis_30/mercator/18/140860/86018.png. In case you only looked at the demo URL https://umap.dmho.de/proxy/demo/ – that does not work out of the box, no idea why. It would be great if you played around with more settings to see if you get the zoom issue solved! There are a few debugging tips at https://github.com/codeforberlin/mapproxy-config#remeber-to-delete-the-file-system-cache. |
Should we still merge this PR or are you planning on using your own instance? |
Hi, I managed to get my instance working with the s/w version and even zoom up to level 24 (apparently mapproxy needs a bit of time to be able to serve previously unconfigured tiles). So I can run my own instance, no merge required. What could be interesting for #14 and #11 is the fact that mapproxy doesn't immediately respect changes in configuration, so @tordans attempt with just setting the |
@karlbeecken could you share your config at https://github.com/karlbeecken/mapproxy-config/; I would then try again getting the zoom fixed.
So I would restart the proxy with the new config, delete the cache and then wait for a night (~10 h) before testing? |
See karlbeecken@7d9a796 for my config. I installed the proxy wednesday evening and apparently today in the morning it worked – but I installed the whole proxy, changing the num_levels shouldn't take that long. I think your plan looks fine |
This worked at #13 (comment), so it really should for us as well… I change the default grid this time, which will affect all layer. Lets see if that makes other trouble along the way.
fixes #12
Adds the ALKIS s/w (black & white) version to the config