Layers identification

Resources harmonized name

The main layers are identified by the following codes :

Layer nameLayer title
ADMINISTRATIVEUNITS.BOUNDARIESAdministrative boundaries
BUILDINGS.BUILDINGSBuildings
CADASTRALPARCELS.PARCELSCadastral parcels
ELEVATION.SLOPESColored DTM
GEOGRAPHICALGRIDSYSTEMS.MAPSScanned maps whatever the map scale is (out of INSPIRE' scope)
GEOGRAPHICALNAMES.NAMESGeographical names
HYDROGRAPHY.HYDROGRAPHYHydrography networks
ORTHOIMAGERY.ORTHOPHOTOSOrtho-photographies whatever the resolution is
ELEVATION.LEVEL0Sea level 0
TRANSPORTNETWORKS.RAILWAYSRailway networks
TRANSPORTNETWORKS.ROADSRoad networks
TRANSPORTNETWORKS.RUNWAYSAirports runways
UTILITYANDGOVERNMENTALSERVICES.ALLGovernmental buildings

The search engine resources are identified by the following codes :

Layer nameLayer title
ADDRESSES.CROSSINGSCrossing begin-end addresses
TOPONYMS.ALLGeographical names

These codes are based on the European INSPIRE Directive, Annexes I to III themes names. Within the INSPIRE Directive implementation, the names will be standardized and the API will provide services using these harmonized names. The objective is to have homogeneous layer names throughout Europe in order to ease geographical data services access.

Layer names are added/updated with the Geoportal's updates. To be informed about available layers, one have to get the capabilities of the relevant services (for instance, WMS-C capabilities are there, and WMS capabilities are there). These names are prefixed by the territory code for WMS layers.

These names are transported with the license key. Depending on your license, not all the names are available.

Services types

The API gives or will give access to the following types of services :

TypeAccess serviceServices URL
WMSCWMS-CGeoportal's Tiled WMS  
INSPIRE view service  
Ministry of Education Tiled WMS
WMTSWMTS 1.0.0N/A
WMSWMS 1.1.1Geoportal's WMS  
INSPIRE view service
WMSWMS 1.3.0Geoportal's WMS  
INSPIRE view service
WFSWFS 1.0.0N/A
WFSWFS 1.1.0N/A
WFSWFS 2.0.0N/A
OLSOLS 1.0.0Geoportal's address location utility service  
Geoportal's geoname location utility service

2D Web Javascript API

They can be retrieved through the instance.allowedGeoportalLayers array in the Javascript API. The following code snippet shows how to display the maps layers without transparency and not displaying the orthophotos :

if (myMap.getMap().allowedGeoportalLayers) {
    for (var i= 0; i<myMap.getMap().allowedGeoportalLayers.length; i++) {
        var overloaded_options= null;
        var layer= myMap.getMap().allowedGeoportalLayers[i];
        if (layer.match(/^GEOGRAPHICALGRIDSYSTEMS.MAPS/)) {// maps
            overloaded_options= {
                                    opacity: 1.0
            };
        } else if (layer.match(/^ORTHOIMAGERY.ORTHOPHOTOS/)) {// orthophotos
            overloaded_options= {
                                    visibility: false
            };
        }
        myMap.addGeoportalLayer(layer,overloaded_options);
    }
}

Have a look at the Javascript documentation Catalogue.js to get the default values of opacity, visibility for the layers.

Starting with 1.0beta4 version, layers names are suffixed by ':' followed by the service's type.

Scales and zoom levels

The Geoportal API supports 21 different zoom levels, amongst which 12 are currently activated. Zoom levels are managed through the setCenter*() API's functions. The following table shows for the activated zoom levels their mapping with scales :

ZoomScaleMap's projection
0WorldIGNF:MILLER
1WorldIGNF:MILLER
2WorldIGNF:MILLER
3WorldIGNF:MILLER
4WorldIGNF:MILLER
5StateIGNF:GEOPORTAL*
6StateIGNF:GEOPORTAL*
7StateIGNF:GEOPORTAL*
8CountryIGNF:GEOPORTAL*
9CountryIGNF:GEOPORTAL*
10CountryIGNF:GEOPORTAL*
11CountryIGNF:GEOPORTAL*
12TownIGNF:GEOPORTAL*
13TownIGNF:GEOPORTAL*
14TownIGNF:GEOPORTAL*
15TownIGNF:GEOPORTAL*
16StreetIGNF:GEOPORTAL*
17StreetIGNF:GEOPORTAL*
18StreetIGNF:GEOPORTAL*
19StreetIGNF:GEOPORTAL*
20HouseIGNF:GEOPORTAL*

The IGNF:GEOPORTAL* projections are compatible with plate-carre projections. The Geoportail API stretches/squizes the images to allow overlaying (OpenLayers extension by IGNF). Unofficial EPSG codes can be used in remplacement of IGNF codes, more information there.

Layer's distributor setting up :

For any layers that can be added to the map, the API exposes a mechanism for advertising the layer's originator. Where OpenLayers uses the attribution parameter, the API use an array of originator with the following properties for each originator object :

  • logo : a string identifying the distributor logo. See pictureUrl for more information ;
  • pictureUrl : if defined, it is the image's URL. if not defined, the logo property is used to construct the URL to the image as follows : http://www.geoportail.fr/legendes/logo_ + logo + .gif ;
  • url : the distributor's URL. The web page is opened in a new window ;
  • extent : the geographic extent of the dataset ;
  • attribution : a short text describing the data owner.