<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2013-03-18 19:53, Jo wrote :<br>
</div>
<blockquote
cite="mid:CAJ6DwMDndUQTxyGdN_T=jaymjLpfOQeMxVLTsWk2Nhjjq-tPkQ@mail.gmail.com"
type="cite">zoom in on the area of interest on this site:<br>
<br>
<a moz-do-not-send="true"
href="http://ogc.beta.agiv.be/gdiviewer/?simple=true">http://ogc.beta.agiv.be/gdiviewer/?simple=true</a><br>
</blockquote>
That viewer issues requests like this:<br>
<a class="moz-txt-link-freetext" href="http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/tms/1.0.0/orthoklm@BPL72VL/13/4828/3716.png">http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/tms/1.0.0/orthoklm@BPL72VL/13/4828/3716.png</a><br>
(for some beta time anyway)<br>
<br>
The zoom goes up to 15, but the maximum resolution it at 13 (as
shown) after which the server stretches the image (scales it).<br>
These are nonstandard zoom levels to which JOSM's zoom level should
be adjusted.<br>
JOSM configuration should be<br>
tms:<a class="moz-txt-link-freetext" href="http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/tms/1.0.0/orthoklm@WGS84VL/">http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/tms/1.0.0/orthoklm@WGS84VL/</a>{zoom-<b>z</b>}/{x}/{y}.png<br>
But I was unable to find a working <b>z</b>. That's always the
problem with TMS when it's not standard.<br>
x and y could be swapped or x be bottom up, etc... A puzzle if it's
not documented.<br>
The advantage of TMS is that the images (tiles) are not modified by
the server.<br>
<br>
Anyway, the corresponding WMS configurations are:<br>
<br>
wms:<a class="moz-txt-link-freetext" href="http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/?FORMAT=image/jpeg&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&STYLES=&SRS=">http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/?FORMAT=image/jpeg&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&STYLES=&SRS=</a>{proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox}&LAYERS=orthoklmx<br>
<br>
It seems to me to have fairly the same resolution as the viewer.<br>
Don't forget to right-click-change resolution on the layer,
especially after you zoomed in.<br>
<br>
wms:<a class="moz-txt-link-freetext" href="http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/?FORMAT=image/png&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&STYLES=&SRS=">http://grb.agiv.be/geodiensten/raadpleegdiensten/geocache/?FORMAT=image/png&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&STYLES=&SRS=</a>{proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox}&TRANSPARENT=YES&LAYERS=grb_bsk,grb_gbg,grb_sel,grb_adp<br>
<br>
png is (much) better for the grb_* and jpeg for the orthos
(equivalent but smaller images).<br>
Unfortunately, the grb images are not transparent (as in Wallonie).<br>
I still used &TRANSPARENT=YES in case they would.<br>
Play with the layers' transparency if you need so.<br>
<blockquote
cite="mid:CAJ6DwMDndUQTxyGdN_T=jaymjLpfOQeMxVLTsWk2Nhjjq-tPkQ@mail.gmail.com"
type="cite">compare the maximum resolution after you<br>
Install a wms layer on JOSM:<br>
I used this uri, but maybe it can be 'optimised':<br>
<br>
wms[12]:<a moz-do-not-send="true"
href="http://wms.agiv.be/ogc/wms/omkl?FORMAT=image/jpeg&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&LAYERS=Ortho&STYLES=&SRS=%7Bproj%7D&WIDTH=%7Bwidth%7D&HEIGHT=%7Bheight%7D&BBOX=%7Bbbox%7D">http://wms.agiv.be/ogc/wms/omkl?FORMAT=image/jpeg&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&LAYERS=Ortho&STYLES=&SRS={proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox}</a><br>
<br>
The 12 between [] stands for the maximum zoom level. I tried with
values of 19, 21, 25, but it doesn't seem to have any effect. So I
guess one could also simply omit it.<br>
</blockquote>
The zoom limit prevents querying servers that return blank or error
images when the resolution limit is exceeded.<br>
If you can determine the JOSM zoom level corresponding to the
resolution limit (13 for TMS) you can use it.<br>
This will prevent uselessly getting stretched images from the server
when JOSM itself can stretch them to the screen.<br>
<blockquote
cite="mid:CAJ6DwMDndUQTxyGdN_T=jaymjLpfOQeMxVLTsWk2Nhjjq-tPkQ@mail.gmail.com"
type="cite">I also tried to use it as tms layer, but no luck with
that either.<br>
</blockquote>
Did you have the same problem as I did (no image at any speed) or
another?<br>
Tell me how you could get TMS working, anyone.<br>
<blockquote
cite="mid:CAJ6DwMDndUQTxyGdN_T=jaymjLpfOQeMxVLTsWk2Nhjjq-tPkQ@mail.gmail.com"
type="cite">
<br>
Thanks for having a look at it.<br>
<br>
It's great to have 2 imagery sources. For some places it works
like a time machine. For others sometimes Bing is clearer, ofthen
AGIV is more revealing, as they had the good sense to shoot
pictures in wintertime, when there is less foliage on the trees.<br>
</blockquote>
It's even greater to have more ;-) All sorts of maps can help
figuring what one sees on a photo :-)<br>
Beware of Bing's error offset. Always zoom out to check or... check
with another map.<br>
<blockquote
cite="mid:CAJ6DwMDndUQTxyGdN_T=jaymjLpfOQeMxVLTsWk2Nhjjq-tPkQ@mail.gmail.com"
type="cite">
At the maximum possible resolution it would be just about perfect.<br>
</blockquote>
I hope it will. Tell me. Have fun.<br>
<br>
Cheers, <br>
<br>
<table>
<tbody>
<tr>
<td valign="top">Rambo.</td>
</tr>
</tbody>
</table>
<br>
<blockquote
cite="mid:CAJ6DwMDndUQTxyGdN_T=jaymjLpfOQeMxVLTsWk2Nhjjq-tPkQ@mail.gmail.com"
type="cite">Jo<br>
<br>
<div class="gmail_quote">Op 18 maart 2013 19:18 schreef
A.Pirard.Papou <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:A.Pirard.Papou@gmail.com" target="_blank">A.Pirard.Papou@gmail.com</a>></span>
het volgende:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
2013-03-12 08:13, Jo wrote :
<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Anderzijds is het wel wat vreemd dat wat JOSM in de
WMS-laag laat zien duidelijk een lagere resolutie heeft,
dan wat er op de website van AGIV zelf zichtbaar is. Het
klinkt misschien wat ondankbaar, maar weten dat er betere
kwaliteit beschikbaar is en het dan met minder duidelijke
beelden moeten doen, is toch wat frustrerend.<br>
<br>
Het zou wel kunnen dat de URI die we gebruiken niet
geoptimaliseerd is. Ik zal dit ook eens op josm-dev posten
en dan vraag ik tegelijk hoe we ervoor kunnen zorgen dat
JOSM deze laag zelf voorstelt aan mappers die data voor
Vlaanderen afhalen/bewerken.<br>
<br>
</blockquote>
</div>
I may have a look if you say which are the URLs you're
comparing.<br>
<br>
The ranter.<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>