Modify

Opened 2 weeks ago

Closed 13 days ago

#20509 closed defect (fixed)

Layer rendering improperly in JOSM but works everywhere else

Reported by: anonymous Owned by: team
Priority: normal Milestone: 21.02
Component: Core imagery Version:
Keywords: poland geoportal user-agent wms Cc:

Attachments (2)

Zrzut ekranu 2021-02-20 212447.png (2.3 MB) - added by anonymous 2 weeks ago.
screen1.png (4.9 MB) - added by wiktorn 2 weeks ago.

Change History (16)

comment:1 Changed 2 weeks ago by wiktorn

WMS is not working because entry doesn't contain

 <custom-http-header header-name="User-Agent" header-value="Mozilla/5.0 (JOSM)" />

As other entries for Geoportal. For some reason, Java string in User-Agent is banned at Geoportal.

comment:2 Changed 2 weeks ago by wiktorn

Resolution: fixed
Status: newclosed

comment:3 Changed 2 weeks ago by Don-vip

Component: CoreExternal imagery source
Keywords: poland geoportal user-agent added
Milestone: 21.02
Type: defecttask

Changed 2 weeks ago by anonymous

comment:5 Changed 2 weeks ago by anonymous

Component: External imagery sourceCore
Milestone: 21.02
Resolution: fixed
Status: closedreopened
Type: taskdefect

did not fix the problem:

Try zooming in on any working coordinates you will get this:

Changed 2 weeks ago by wiktorn

Attachment: screen1.png added

comment:6 Changed 2 weeks ago by wiktorn


Works by me right now. Though I've also noticed this problem for some period of time. Cleared the cache, and then problem disappeared. Not sure, if this was something on the server side or on our.

comment:7 Changed 2 weeks ago by anonymous

the bug is still present after deleting all the files in ~/AppData/Local/JOSM/cache

comment:8 Changed 2 weeks ago by anonymous

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-12-28 22:03:23 +0100 (Mon, 28 Dec 2020)
Build-Date:2020-12-30 02:30:55
Revision:17428
Relative:URL: ^/trunk

Identification: JOSM/1.5 (17428 pl) Windows 10 64-Bit
OS Build number: Windows 10 Education 2009 (19042)
Memory Usage: 871 MB / 1820 MB (550 MB allocated, but free)
Java version: 1.8.0_281-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 1920×1080 (scaling 1,00×1,00) \Display1 1920×1080 (scaling 1,00×1,00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→32×32, 32×32→32×32
VM arguments: [-Djava.security.manager, -Djava.security.policy=file:<java.home>\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=%UserProfile%\Downloads\josm (1).jnlp, -Djnlpx.remove=false, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.heapsize=NULL,2048m, -Djnlpx.splashport=61425, -Djnlpx.jvm=<java.home>\bin\javaw.exe]

Plugins:
+ PicLayer (2a9aa7a)
+ imagery-xml-bounds (35640)
+ indoorhelper (eca65b2)

Map paint styles:
- <josm.pref>\styles\sit.mapcss

comment:9 Changed 2 weeks ago by anonymous

To me honest for me even the "GetCapabilities" link (https://mapy.geoportal.gov.pl/wss/service/PZGIK/ORTO/WMS/HighResolution?service=WMS&request=GetCapabilities&version=1.3.0) dose not work in JOSM. When trying to get the available layers I get the error:

javax.xml.stream.XMLStreamException: PraseError at [row,col]:[1,1]
Message: Premature end of file

comment:10 Changed 2 weeks ago by wiktorn

Resolution: fixed
Status: reopenedclosed

In 17502/josm:

Check current tile projection when querying WMS server.

Add same logic as in WMSEndpointTileSource to check, whether coordinates needs
to be switched or not. Before this change, switch was calculated only when
adding the layer, so changing map projection was ignored.

Also it was using JOSM map projection settings instead of the projection that
was chosen to query the server and this could result in replaced X and Y
coordinates.

Closes: #20509

comment:11 in reply to:  9 Changed 2 weeks ago by wiktorn

Replying to anonymous:

To me honest for me even the "GetCapabilities" link (https://mapy.geoportal.gov.pl/wss/service/PZGIK/ORTO/WMS/HighResolution?service=WMS&request=GetCapabilities&version=1.3.0) dose not work in JOSM. When trying to get the available layers I get the error:

javax.xml.stream.XMLStreamException: PraseError at [row,col]:[1,1]
Message: Premature end of file

This is usual message if you haven't customized User-Agent in case of this server. Turn on Expert mode (e.g. in preferences windows, bottom left checkbox), then start adding WMS, but first set in the table with "custom HTTP headers" header name and value as I mentioned in comment:1

comment:12 Changed 2 weeks ago by wiktorn

Component: CoreCore imagery
Keywords: wms added
Milestone: 21.02

comment:13 Changed 13 days ago by anonymous

Resolution: fixed
Status: closedreopened

This WMS doesn't work for me either in JOSM with default settings but works fine in QGIS. As far as I can tell JOSM automatically adds custom user agent like "Mozilla/5.0 JOSM" or something so that shouldn't be an issue.
JOSM version 17428

I tested it with projection 3857 (which this WMS doesn't support and is the default projection for JOSM) and projection 2180 (supported by wms).
With 2180 it works fine, with 3857 tiles are completely wrong.
Changing projection after adding WMS layer doesn't work. Only if I change the projection first then load WMS layer.

It seems like a bug with JOSM reprojection algorithm.

comment:14 Changed 13 days ago by wiktorn

Resolution: fixed
Status: reopenedclosed

If this is the same problem that you've reported earlier, this was fixed in version 17502. Please test it with version 17502 or later.

Your description matches exactly the bug that was fixed in version 17502.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.