Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Give user abliilty to filter data #1532

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 7 comments
Closed

Give user abliilty to filter data #1532

openstreetmap-trac opened this issue Jul 23, 2021 · 7 comments

Comments

@openstreetmap-trac
Copy link

Reporter: OSM[at]soft-hedgehog.co.uk
[Submitted to the original trac issue database at 1.51pm, Tuesday, 27th January 2009]

For towns with large numbers of data points, firstly there is the annoyance of having to click "load data" every time the map moves, but more importantly there is far more info than one user wants. Some uninteresting data can easily obscure data that is required. Being able to filter out uninteresting categories would help enormously with the usability.

The list of data points is also in (apparently) random order. Sorting alphabetically (or other ways) would help when there is much to scroll through.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 4.06pm, Tuesday, 27th January 2009]

Can you clarify what software and/or interface to OSM you are referring to, so that I know who to assign this to?

@openstreetmap-trac
Copy link
Author

Author: OSM[at]soft-hedgehog.co.uk
[Added to the original trac issue at 4.42pm, Tuesday, 27th January 2009]

I'm simply using OSM :-) Zoom into any town centre, click (+) and []Data and the problems that I mention will appear.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 4.47pm, Tuesday, 27th January 2009]

You shouldn't have to click load data then - it should be reloading automatically as you move - it certainly does for me in Firefox 3.

The only time it doesn't is if you have manually selected an area - in that case it stays locked to the area you chose until you tell it to do other wise by choosing a new area or asking it to go back to displaying data for the current map view.

The other things would I'm sure be very nice but they would be very complicated to implement as they would have to be in Javascript. Certainly not high priority I'm afraid.

@openstreetmap-trac
Copy link
Author

Author: OSM[at]soft-hedgehog.co.uk
[Added to the original trac issue at 5.30pm, Tuesday, 27th January 2009]

There are >100 data points in almost anywhere interesting and whenever I ask for the data it tells me this and I have to click "Load Data". Often if I just click on one of the green circles it reloads some more data (and asks again), and always when I slide the map to see a little more. With more and more data being added this becomes a major stalling point. In its current state the data overlay is largely unusable.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 5.45pm, Tuesday, 27th January 2009]

Ah yes, if there are a lot of points you will have to confirm it - that is to protect you from having your browser grind to a halt.

Yes, I know that Firefox 3 (for example) can manage rather more items than that before dieing in a heap but lots of browsers can't.

@openstreetmap-trac
Copy link
Author

Author: OSM[at]soft-hedgehog.co.uk
[Added to the original trac issue at 9.59am, Wednesday, 28th January 2009]

Which is why I say either allow the user to filter the data so there is no so much and/or allow the user to set the limit relevant to the browser/OS/machine/link capability.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 12.18am, Tuesday, 27th October 2009]

Filtering the data isn't really possible though - it would have to be done in javascript on the client and would be a massive task. If somebody comes forward with something to do it then fine but I don't see any point leaving this open in the hope somebody will suddenly take on such a massive task.

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

No branches or pull requests

1 participant