#14074 closed defect (fixed)
Error when trying to display imagery at JOSM website
| Reported by: | Klumbumbus | Owned by: | stoecker |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Trac | Version: | |
| Keywords: | Cc: |
Description
There are some, which don't work:
Trac hat einen internen Fehler festgestellt: ValueError: need more than 1 value to unpack
e.g.
Attachments (0)
Change History (8)
comment:1 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 8 years ago
Beside this, these WMS aren't displayed correctly from the web. If someone can tell my why, I'll fix it. Found it.
follow-up: 6 comment:3 by , 8 years ago
So we should simply change all ?& to ? if used as first parameter in imagery urls?
follow-up: 5 comment:4 by , 8 years ago
One more thing. I added a shape to https://josm.openstreetmap.de/wiki/Maps/Belgium#SPWalloniePICCnumericalimagery
It is displayed in JOSM but not in the browser view.
comment:5 by , 8 years ago
Replying to Klumbumbus:
One more thing. I added a shape to https://josm.openstreetmap.de/wiki/Maps/Belgium#SPWalloniePICCnumericalimagery
It is displayed in JOSM but not in the browser view.
Now it works.
comment:6 by , 8 years ago
Replying to Klumbumbus:
So we should simply change all
?&to?if used as first parameter in imagery urls?
Yes. The ampersand is a record separator. It should not be at the beginning.
One more thing. I added a shape to https://josm.openstreetmap.de/wiki/Maps/Belgium#SPWalloniePICCnumericalimagery
It is displayed in JOSM but not in the browser view.
There was an second boundary there. JOSM takes the second one, the web view the first one. I removed it.
The XSD for validation has some limitations. Detecting such issues is one of them :-)
follow-up: 8 comment:7 by , 8 years ago
Hey, let me at least finish my text before you answer to me...
Fixed the error in Trac.
The reason was a bad URL. The services have "?&", but the first parameter should not start with a "&". The "&" directly after a "?" is wrong and should be removed from all URLs which have it.