Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

Users on iShare v5.8 are eligible to use only the custom OS Maps API WMS base maps via ADS as iShare v5.8 does not support WMTS and OS Maps API is currently available only via WMTS.

To configure the available base maps in iShare (either Maps or GIS) you need to first obtain an API key from OS Data Hub. You can see how to do so here: How to create a Project and generate an API key in OS Data Hub.

Once you have your API key

You are now ready to configure the custom OS WMS base maps in Studio as described below. Please note that the process is the same whether you use Maps or GIS.

To make this process smoother for you we have already prepared the MapSources and a basic Mapfile ready to be loaded into iShare. All you need to do is place the MapSources and the corresponding MapFile in the correct directories, import the MapSources into Studio, and enter your customer name and API key in the appropriate places, which we have highlighted in the guide.

In the zip folder that is attached to this guide, you will find several MapSources and a Mapfile. Below you will find detailed steps on how to set up an OS Maps API WMS base map via the Astun Data Services as well as the zip folder at the end of the page.

Steps

  1. From the zip folder grab the MapFile called base_osmapsapi.map and place it under E:\iShareData\LIVE\_MapServerConfig\

  2. From the zip folder MapSources v5_8 grab the OS Road MapSource called base_osmapsapi_road_wms.xml and place it under D:\Astun\iShareGIS\LIVE\WebApps\WebService\config\mapsources

  3. After placing the files into the correct destinations, open Studio and import the MapSource under the BaseMaps node:

    1. Right-click on the BaseMaps node and select Import MapSource

      mstsc_VBm2djSnzQ.png

       

    2. Navigate to the directory in which you placed the OS Road MapSource, open it, and give it an appropriate name such as OS Road in Studio:

      mstsc_kddI4MmseS.png

      mstsc_lA8Ei8ZYr3.png

       

  4. After the import, you will notice that everything is prefilled for you. All you have to do is add your API key and your organisation's name in the correct places:

    1. Navigate to the Details node and examine the URI field. The URI field is pointing to the WMS Astun Data Services endpoint https://map.services.astuntechnology.com/your-organisation-goes-here/osmaps/service?key=your-API-key-goes-here. In the URI, you will see two placeholders, one that says your-API-key-goes-here and one that says your-organization-goes-here. Replace those placeholders with your alpha-numeric OS Data Hub Project API Key and organisation name, and don't forget to save your changes. If you are unsure of your organisation name, please contact us via support.

      mstsc_X6rlmBlKM9.png

  5. Add the base map to a MyMaps MapSource, save and test that the base map is displaying correctly:

    mstsc_IFHFBKGlXK.png

    chrome_vjNmZIEZu2.png

  6. Follow the same procedure for the rest of the direct basemap MapSources:

    1. base_osmapsapi_leisure_25k_wms.xml

    2. base_osmapsapi_leisure_50k_wms.xml

    3. base_osmapsapi_leisure_grayscale_wms.xml

    4. base_osmapsapi_leisure_wms.xml

    5. base_osmapsapi_light_grayscale_wms.xml

    6. base_osmapsapi_light_wms.xml

    7. base_osmapsapi_outdoor_grayscale_wms.xml

    8. base_osmapsapi_outdoor_wms.xml

    9. base_osmapsapi_road_grayscale_wms.xml

MapSources available here:

Please note the below:

  • Leave the Scales section unchanged.

  • The High DPI option should be disabled for all the base maps except the OS Leisure 50k & 25k. Check out why here Why not to print OS Maps API basemaps in High DPI

  • Keep the Boundary Settings under Start up as is.

  • No labels