#10867 closed defect (fixed)
notes are download with a limit of 1000 without telling the user about reaching this limit
Reported by: | aseerel4c26 | Owned by: | ToeBee |
---|---|---|---|
Priority: | minor | Milestone: | 15.04 |
Component: | Core notes | Version: | latest |
Keywords: | Cc: |
Description
apparently (judging from my terminal log which shows an GET parameter of "limit=1000") notes are download with a limit of 1000 without telling the user about this (and the user also did not set this limit). If the API then returns 1000 hits it is very likely that some notes from the selected area are missing (because there will be more than 1000). The user will not know about this (no error message, note even in the terminal) and would think that he got all notes in this area.
Suggestion (and easy fix): If a limit is needed, then the user should be told (in such a unobstrusive popup bubble thingy at the bottom left corner) about reaching the limit (1000 downloaded notes). Something like this: your notes API request was limited to 1000 notes. There seem to be more notes than this in your area. You may want to choose a smaller area.
JOSM Version 7819.
Attachments (0)
Change History (17)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
A number limit reached warning would be good in any way, I think. Maybe, in addition to the advice of a smaller area, the warning popup could offer to increase the limit or simply provide a link to the docu (where the advanced pref is mentioned).
Regarding the default limit: I do not know. What is the danger of 10000? First, the user needs to select an area which is really that big to contain that many notes. Then: The user gets an out of RAM? Not sure how much notes need. But since the API defaults to 100 I think we should not default to the max. 1000 may be fine until we know better.
comment:3 by , 10 years ago
Component: | Core → Core notes |
---|
Moving notes tickets to their own component
comment:4 by , 10 years ago
Keywords: | notes removed |
---|
comment:6 by , 9 years ago
Milestone: | → 15.04 |
---|
follow-up: 10 comment:8 by , 9 years ago
Was the osm api hard limit changed from 10k to 50k? edit: ok, answered myself. now I see, you changed the nodes download limit and not the notes download limit.
comment:10 by , 9 years ago
Replying to Klumbumbus:
Was the osm api hard limit changed from 10k to 50k?edit: ok, answered myself. now I see, you changed the nodes download limit and not the notes download limit.
I confused node with note while looking for the constant in the source … I set it back to the correct 10k in r8230. Thank you!
Anyway, the API would have told when loading 30k notes … ;-)
comment:11 by , 9 years ago
The warning if the download limit is reached (tested with 500 and 1000) seems to work fine, thanks simon04! :-)
follow-up: 14 comment:13 by , 9 years ago
This has been done in r8230?
10k is correct according to the source code of openstreetmap-website …
comment:14 by , 9 years ago
Replying to simon04:
This has been done in r8230?
Don't think so:
BoundingBoxDownloader.java line 214
The OSM API defaults to 100 if no limit is given and has a hard upper limit of 10,000. (It was actually 9,999 in the code and 10,000 in the documentation until I discovered this discrepancy while writing the notes plugin and submitted a patch to the rails port :)
I limited JOSM to request 1,000 by default although this value is based on the osm.notes.downloadLimit preference so you can set it higher which is what I would suggest doing for right now. Eventually this should be configurable in a UI somewhere instead of having to dig in the advanced preferences list. And maybe I should just default to 10,000? Not sure on that.
But either way, your suggestion of popping up a warning if the download limit is reached is probably a good idea.