Opened 6 years ago
Last modified 6 years ago
#16753 new enhancement
wikipedia plugin's viewport bounding box setting
Reported by: | katpatuka | Owned by: | floscher |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Plugin wikipedia | Version: | tested |
Keywords: | wikipedia plugin bounding box setting | Cc: |
Description
I'd appreciate an advanced setting for the allowed bounding box size of the current viewport for the wikipedia plugin.
In areas where not many wikidata links are to be expected it would be nice if the allowed bounding box size would be more flexible set.
The current setting is that the limit is seemingly at 2.0 km zoom; if one zooms out to 4.0 km this message shows up when clicking on Wikidata items in viewport:
Downloading entries with geo coordinates failed: Bounding box is too big
I don't know if the default setting is so low to reduce the expected server traffic but a warning like Are you sure (yes/cancel) when exceeding the 2.0 km limit would be enough in my eyes...
Please provide any additional information below. Attach a screenshot if possible.
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2018-08-22 19:44:25 +0200 (Wed, 22 Aug 2018) Build-Date:2018-08-22 17:46:33 Revision:14178 Relative:URL: ^/trunk Identification: JOSM/1.5 (14178 en) Windows XP 32-Bit OS Build number: Microsoft Windows XP (1.511.1 () (Obsolete data - do not use)) Memory Usage: 185 MB / 185 MB (48 MB allocated, but free) Java version: 1.8.0_151-b12, Oracle Corporation, Java HotSpot(TM) Client VM Screen: \Display0 1360x768 Maximum Screen Size: 1360x768 Dataset consistency test: No problems found Plugins: + FastDraw (34510) + PicLayer (34544) + apache-commons (34506) + ejml (34389) + ext_tools (34509) + geotools (34513) + jts (34524) + measurement (34529) + opendata (34576) + reverter (34552) + utilsplugin2 (34506) + waydownloader (34569) + wikipedia (v1.1.1)
This is not a limitation created by the plugin, but by the Wikidata API from where the data is queried. I'm also not sure where exactly the cut-off is (there's no limit mentioned in the documentation).
We could probably only realize this by splitting the API query into multiple queries when the bbox is too big.