<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
Regarding this, I have updated <a
href="http://www.papou.byethost9.com/maps/mapproxy/">my Mapproxy
distribution</a> for even greater simplicity.<br>
<br>
<br>
On 2013-11-19 22:15, � wrote :<br>
</div>
<blockquote cite="mid:528BD4E8.3080504@fastre.info" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">Le 15/11/13 22:03, André Pirard a
écrit :<br>
</div>
<blockquote cite="mid:52868C39.90307@gmail.com" type="cite">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 2013-11-13 20:35, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:julien@fastre.info">julien@fastre.info</a>
wrote :<br>
</div>
<blockquote
cite="mid:e49432c1961c6daaa62802330e62c0d2@fastre.info"
type="cite">
<p>As far as I understand, the main usage of tiles projeted in
Lambert72 or Lambert 2008 is to be mixed with data from AGIV
or Walloon Regio, which doesn't support 900913 (nor 3857) in
their WMS services. We are developping an app today and this
is a problem to mix information from Walloon Regio and OSM
because the need of projectio.</p>
<p>QGIS user doesn't need this, but they are advanced user. We
target people who are not GIS user there. </p>
<p>Right ?</p>
</blockquote>
Hi,<br>
<br>
How was Arlon, Julien?<br>
<br>
What I understood is that AGIV uses applications that can get
data only from EPSG:31370 WMS and hence not from OSM. And so
that they need TMS 4326 -> WMS 31370 conversion.<br>
<br>
After reading Ben's message, I added 14 characters to my local
Mapproxy configuration (4 if I copy & paste from Ben) and I
had on my PC exactly what AGIV need, tested later with JOSM.<br>
And so, I recommended Mapproxy once again.<br>
BTW, there are a good 20 references to Mapproxy on
wiki.openstreetmap.org and I just discovered<br>
among them a page <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://wiki.openstreetmap.org/wiki/MapProxy">http://wiki.openstreetmap.org/wiki/MapProxy</a>
dedicated to Mapproxy which contains the installation procedure,
including the configuration that Ben needs.<br>
Just in case somebody would read what I wrote, I added a DEB
remark for Ubuntu/Debian install.<br>
<br>
Anyway, I decided to stop speaking of Mapproxy repeatedly and to
write a Web page instead.<br>
I hope to finish it tonight and it will contain a super simple
procedure with a guaranteed-to-work simple configuration for OSM
(I have doubts about the config in the OSM wiki page).<br>
<br>
I'll let you know, of course.<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</blockquote>
Hi,<br>
<br>
The "board" of Champs Libres (my society founded one month ago)
had a meeting this afternoon and we decided that it was very
important to give help to osm-be. So, we agree with setting up a
server for tiles or WMS if you think this may be useful.<br>
<br>
As a I understand, the use case is "to be able to mix WMS layer
from AGIV / Région Wallonne with openstreetmap". </blockquote>
As I understand it, "WMS for OSM using EPSG:31370" means
"reprojecting OSM's TMS 4326 to WMS 31370" for handicapped
applications that can only use 31370. Hey there, tell me if I'm
right or wrong !!!<br>
<blockquote cite="mid:528BD4E8.3080504@fastre.info" type="cite">This
is not possible until :<br>
<br>
1. AGIV / RW serve WMS layers with projection EPSG:3857 or 900913
;<br>
</blockquote>
EPSG:4326 is the most important to serve (read AGIV below).<br>
<br>
AFAIKS, the only SPW servers providing WMS are cartopro1 (ortho) and
cartopro2 (base map) in 31370.<br>
I have explained that they should serve 4326 too (at least).<br>
The other (new) servers do not use WMS but ArcGIS REST and 31370.<br>
I have explained that they should serve WMS 4326 as well (at least).<br>
<br>
I seem to have been misunderstood.<br>
They seem to have removed cartopro2 instead.<br>
So, except for BING like orthos, we have <b>NO WMS</b> and <b>NO
4326</b> at the SPW.<br>
<br>
And what would be great is if you could reproject all their ArcGIS
layers to WMS 4326 at least.<br>
<br>
AFAIKS, AGIV serves WMS:<br>
CRS:84, EPSG:4326, EPSG:4258, EPSG:31370, EPSG:3812, EPSG:3043,
EPSG:32631 and EPSG:25831. <br>
Generally, all non handicapped applications can use 4326 and I see
that JOSM, which is not supposed to reproject, can make 4326
requests when its screen is configured as Mercator 3857.<br>
That's because the sole difference is the simple vertical
transformation y = R ln tan (PI/4 + phi/2).<br>
But, if needed, AGIV might agree to add EPSG:3857 and 900913 more
easily than SPW.<br>
<blockquote cite="mid:528BD4E8.3080504@fastre.info" type="cite"> 2.
We have tiles in those projections ;<br>
<br>
So, we may reproject WMSs into 900913/3857 (1) or serve tiles (2).<br>
</blockquote>
Why tiles and why in those projections?<br>
I have just explained that <a
href="http://www.papou.byethost9.com/maps/mapproxy/">Mapproxy</a>
and others can transform any TMS or WMS server in any projection to
TMS or WMS in any projection. Except that if a cache is used, TMS
can only be served in the projection of the cache.<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<blockquote cite="mid:528BD4E8.3080504@fastre.info" type="cite">For
1, this will force us to "capture" every WMS and serve it again. I
am afraid that we might have a delay before inserting WMS. I
wonder also about the legality of such use (I may ask RW for
authorization).<br>
<br>
For 2, we know how OSM goes, and an advantage I see is that we
might have other styles later, if we need it.<br>
<br>
What are other advantages of every answer to those question ?<br>
<br>
Julien<br>
<br>
NB: our server's provider have some problems those days... We will
have to wait their new products to be available. This should be
done within end of this year.<br>
<br>
@André & others :<br>
<br>
Arlon was great. I spoke about OSM as a community project, how we
works, what we do, what are the value of the community, ...<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Talk-be mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-be">https://lists.openstreetmap.org/listinfo/talk-be</a>
</pre>
</blockquote>
<br>
</body>
</html>