[MapProxy-dev] Integration of new features in mapproxy

Denis Rykov rykovd at gmail.com
Sun Mar 20 18:02:58 PDT 2022


Hi Jean-Christophe,

I've made a PR which I believe should fix the issue. Could you please take
a look: https://github.com/mapproxy/mapproxy/pull/572

On Wed, Mar 9, 2022 at 1:47 PM Malapert Jean-Christophe <
Jean-Christophe.Malapert at cnes.fr> wrote:

> Dear All,
>
>
>
> My name is Jean-Christophe Malapert and I am engineer in CNES and also the
> co-chair of the Planetary DWG at OGC (
> https://www.ogc.org/projects/groups/planetarydwg).
>
>
>
> Currently, I am setting up a Surfaces Planetary data center in France with
> all scientific laboratories in Planetology.  My community (in general
> planetology) is divided in two parts :
>
> -        Scientific/engineers coming from Astronomy world and using IVOA
> standards (https://ivoa.net)
>
> -        Scientific/engineers coming from Geosciences world and using OGC
> standards
>
>
>
> Each world uses its own clients (e.g leaflet for OGC ; Aladin for IVOA)
> and no one wants to implement the access protocols of the other world. In
> this context, we have realized a study and a prototype to map the access
> standards from OGC/IVOA for images. Thanks to this prototype, QGIS/leaflet
> can access to astronomical data and Aladin can access to data distributed
> by WMS/WMTS servers.
>
>
>
> It would be great if :
>
> ·        1/ the contribution could be integrated in mapproxy. I am
> attaching the study report (
> https://docs.google.com/document/d/1fJJYVNYg2uWhCaN3fxlBLg09vFND0YLLUiGRJ_fCh5c/edit?usp=sharing)
> .
>
> ·        2/ the Integration of the IAU CRS in mapproxy can be done
>
> services:
>
>   wms:
>
>     srs: ['IAU:1000']
>
> sources:
>
>   test:
>
>     type: wms
>
>     supported_srs: ['IAU:1000']
>
>     req:
>
>       url: https://....
>
>       layers: blah
>
>
>
> The statement srs: ['IAU:1000'] at the service level passes (if I don't
> put which, I see it as a possible CRS in the GetCapabilities, but without
> an associated BoundingBox), but not supported_srs: ['IAU:1000'] at the
> source level, which crashes with:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *  File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/mapproxy/config/loader.py",
> line 804, in source     supported_srs=self.supported_srs(),   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/mapproxy/config/loader.py",
> line 578, in supported_srs     supported_srs = [SRS(code) for code in
> self.conf.get('supported_srs', [])]   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/mapproxy/config/loader.py",
> line 578, in <listcomp>     supported_srs = [SRS(code) for code in
> self.conf.get('supported_srs', [])]   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/mapproxy/srs.py", line 96, in
> SRS     srs = _srs_impl(srs_code)   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/mapproxy/srs.py", line 320,
> in __init__     self.proj = CRS.from_epsg(epsg_num)   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/venv/lib/python3.8/site-packages/pyproj/crs/crs.py",
> line 370, in from_epsg     return
> cls.from_user_input(_prepare_from_epsg(code))   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/venv/lib/python3.8/site-packages/pyproj/crs/crs.py",
> line 479, in from_user_input     return cls(value, **kwargs)   File
> "/home/even/spatialys/cnes/2021/hips/mapproxy/venv/lib/python3.8/site-packages/pyproj/crs/crs.py",
> line 326, in __init__     self._local.crs = _CRS(self.srs)   File
> "pyproj/_crs.pyx", line 2352, in pyproj._crs._CRS.__init__
> pyproj.exceptions.CRSError: Invalid projection: epsg:1000: (Internal Proj
> Error: proj_create: crs not found)*
>
>                At some point MapProxy assumes that the CRS is an EPSG
> apparently.
>
>
>
> *IAU CRS*
>
> IAU (International Astronomical Union) CRS is based on the report of this
> group https://astrogeology.usgs.gov/groups/IAU-WGCCRE. Based on this
> report, the WKT-crs group (https://www.ogc.org/standards/wkt-crs)  from
> OGC has modified (a simple addition) its standard in order to be compliant
> with the CRS defined in IAU. In addition, we are working at OGC to
> integrate the IAU crs within the OGC standards (e.g :
> https://github.com/opengeospatial/NamingAuthority/issues/113)
>
> In addition, proj has now IAU CRS definition :
> https://github.com/OSGeo/PROJ/pull/2876 . Same thing for GDAL :
> https://github.com/OSGeo/gdal/pull/5287. Based on this pull request,
> mapserver can also accept SRS=IAU:xxxx as input parameter for WMS requests
> https://github.com/MapServer/MapServer/pull/6484 . The last version of
> QGIS also integrates the IAU CRS.
>
> Please let me know if you could integrate these 2 features in your roadmap
> and if you need any help from CNES to help you
>
>
>
> Best regards,
>
> Jean-Christophe
>
>
>
>
>
> *Jean-Christophe MALAPERT*
>
> *Expert Dev. Segments Sols Scientifiques *
>
> DTN/CD/SC
>
> 18 avenue Edouard Belin 31401 Toulouse Cedex 9
>
> [image:
> http://publi.portail.cnes.fr/sites/CNES_Pratique/DocumentsCNES/signature%20version%20finale/signature_cnes_fr_externe_fichiers/phone.png]
>  +33 (0)5 61 28 14 45 /  +33 (0)6 42 94 63 10
>
> [image:
> http://publi.portail.cnes.fr/sites/CNES_Pratique/DocumentsCNES/signature%20version%20finale/signature_cnes_fr_externe_fichiers/email.png]
>  jean-christophe.malapert at cnes.fr
>
> [image:
> http://publi.portail.cnes.fr/sites/CNES_Pratique/DocumentsCNES/signature%20version%20finale/signature_cnes_fr_externe_fichiers/web.png]
>  cnes.fr
>
> [image:
> http://publi.portail.cnes.fr/sites/CNES_Pratique/DocumentsCNES/signature%20version%20finale/signature_cnes_fr_externe_fichiers/facebook.png]
> <https://www.facebook.com/CNESFrance/>  [image:
> http://publi.portail.cnes.fr/sites/CNES_Pratique/DocumentsCNES/signature%20version%20finale/signature_cnes_fr_externe_fichiers/instagram.png]
> <https://www.instagram.com/cnes_france/>  [image:
> http://publi.portail.cnes.fr/sites/CNES_Pratique/DocumentsCNES/signature%20version%20finale/signature_cnes_fr_externe_fichiers/twitter.png]
> <https://twitter.com/cnes>
>
>
>
>
> _______________________________________________
> MapProxy-dev mailing list
> MapProxy-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapproxy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 12736 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 668 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 788 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 745 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 764 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1108 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 1169 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.png
Type: image/png
Size: 1149 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/mapproxy-dev/attachments/20220321/7fa225a4/attachment-0015.png>


More information about the MapProxy-dev mailing list