#17411 closed enhancement (wontfix)
support "!=" operator in JOSM filters
Reported by: | mkoniecz | Owned by: | team |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Attempt to show, say, only
boundary=administrative
- Add exclusion filter
boundary!=administrative
- Become confused
What is the expected result?
It works
What happens instead?
One needs to use -boundary=administrative
.
Please provide any additional information below. Attach a screenshot if possible.
!= operator is fairly standard for "not equals to"
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2019-02-23 17:46:51 +0100 (Sat, 23 Feb 2019) Build-Date:2019-02-24 02:30:49 Revision:14802 Relative:URL: ^/trunk Identification: JOSM/1.5 (14802 en) Linux Ubuntu 16.04.5 LTS Memory Usage: 445 MB / 869 MB (203 MB allocated, but free) Java version: 1.8.0_201-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: :0.0 1920x1080 Maximum Screen Size: 1920x1080 Dataset consistency test: No problems found Plugins: + OpeningHoursEditor (34867) + buildings_tools (34867) + continuosDownload (82) + imagery_offset_db (34867) + measurement (34867) + reverter (34867) + todo (30306) Validator rules: + ${HOME}/Desktop/tmp/test.validator.mapcss Last errors/warnings: - W: Already here java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out - W: Already here java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out - E: org.openstreetmap.josm.io.OsmApiException: ResponseCode=400, Error Header=<You requested too many nodes (limit is 50000). Either request a smaller area, or use planet.osm> - E: Bad Request - org.openstreetmap.josm.gui.widgets.HtmlPanel[,0,0,0x0,invalid,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=] - W: java.net.SocketTimeoutException: Read timed out
Attachments (0)
Change History (5)
follow-up: 2 comment:1 by , 6 years ago
follow-up: 5 comment:3 by , 6 years ago
Replying to Don-vip:
Who's speaking?
An enthusiastic JOSM user with developer mind, behind many bug reports who not yet registered, but he is thinking to do so in the future. We don't know each other :)
comment:4 by , 6 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:5 by , 6 years ago
Replying to anonyme:
Replying to Don-vip:
Who's speaking?
An enthusiastic JOSM user with developer mind, behind many bug reports who not yet registered, but he is thinking to do so in the future. We don't know each other :)
Please register if you plan to help us. Speaking to anonymous users is really confusing and brain-overloading for me.
Using more than one operator for the same thing is not a good idea in my opinion. I would get even more confused if I could use
!=
and-
as well. Can't they decide which one wanted to use and included both? Why? Are there any differences?JOSM is already enough complex. And after all, you have the help just two lines below the search field.