Skip to content
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

Background map and zooming (still fast) on higher resolution #71

Open
BrunoKestemont opened this issue Jan 28, 2019 · 4 comments
Open

Comments

@BrunoKestemont
Copy link

Hell,
You say in March 2018 that you are working on a new map:
"We are working on a new map. A different map is available at: http://maps.luftdaten.info/belgium/ , maybe this will get the new map soon."
I see the problem with this one: it's much too heavy to zoom in.
However, it's important to get the high resolution when zooming (until the basic OpenStreetMap).

I don't know what's the problem but would a solution be to go and take a new zoomed OpenStreetMap when needed on each zooming. Or to cut the big map in pieces and retrieve only the relevant part of the puzzle when zooming ?

@ricki-z
Copy link
Member

ricki-z commented Jan 28, 2019

We are using the openstreetmap tiles server. So we don't need to cut the map in pieces.
Some of the users won't a higher much higher resolution as someone may find the exact location of the sensor (which we try to prevent by rounding the coordinates).
But I can set the allowed zoomlevel to one level higher and we could test if this is okay.

@ricki-z
Copy link
Member

ricki-z commented Jan 28, 2019

It should be possible now to zoom in two levels more.

@BrunoKestemont
Copy link
Author

Thanks (for zoom 15) but what we really need is to zoom till 17 like here:
https://www.openstreetmap.org/#map=17/50.86853/4.31511
There are schools and we want to be able to set sensors at different places (playing field, outside near the tunnel, outside on the closed street side etc.
Considering confidential sensor location, I suggest 2 alternatives for the once who need this confidentiality (don't round the location at the server side):
a-round the location as an option only (check a box if you want to fuzzy your location) at the client size.
b-when correcting the default location, give an alternate location in the surround if you want to protect the location

@ricki-z
Copy link
Member

ricki-z commented Jan 29, 2019

Or you use the stations that are also transmitting to openstreetmap. There the stations are shown with their exact (and also unverified) location.
Most users wish the location not to be exact.
And option (a) is not really a solution. With that we would publish the exact location of the stations in our data even if the owner wants to fuzzy this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants