Hi,

Is this the right place to report possible issues with spellings?

I noticed at around 54.41492988, -3.17074912 the valley is labeled as Moasdale. I thought this should be Mosedale. Are there various spellings for this? Do you get this data from OSM, since I noticed it there as well? If yes, then I am happy to fix it there.

Thanks for this great project!

I've got the geopackage into qgis and applied the QML styles and layers in the correct order. However the styles in this repo don't match those on the OS website, specifically at:

For example there are the following differences:
Fonts - England is in caps on website, lower case in qgis
Font sizes - much smaller on the website
Font colours - pretty sure these are different
Roads - some roads (private?) are dashed on website
Buildings and water - have slight 3d view on website

Is there an update in the works to this repo that will synchronise the styles to match the website version?

Thanks for releasing these stylesheets as open source, they're fantastic resources.

The links to the two Ordnance Survey pages on cartographic design in the repo's various READMEs no longer work.

The first page, http://www.ordnancesurvey.co.uk/resources/carto-design/cartographic-stylesheets.html, returns HTTP 200 but the page only says "The requested URL was rejected. Please consult with your administrator."

The second page, https://www.ordnancesurvey.co.uk/resources/carto-design/, first returns HTTP 302 and redirects to https://www.ordnancesurvey.co.uk/resources/carto-design (no trailing slash). That second page returns HTTP 200 but the page only says "The page you are trying to reach has gone rambling".

QGIS (3.13+) supports vector tiles naively. It will be great to have QML styles for QGIS in addition to Mapbox.

When you import Zoomstack vector tiles into QGIS, the plugin sets a few customProperties for each layer (such as the URL of the remote tile.json, if it's the hosted Zoomstack tiles). If you apply one of these QMLs to one of the layers, it wipes those customProperties.

The adverse affect this has in my specific case is to stop qgis2web working with these layers. The customProperties are how qgis2web knows a layer is a vector tiles layer, so if they are overwritten, it starts trying to export them as GeoJSON.

The simple solution is to delete the whole customProperties section from the QMLs. However, some customProperties are set in that section:

  <customproperties>
    <property value="0" key="embeddedWidgets/count"/>
    <property key="variableNames"/>
    <property key="variableValues"/>
  </customproperties>

They might just be default QGIS properties, in which case I think this solution is correct. However, it would be good if someone else could confirm these sections can safely be deleted. If so, I can happily do a PR.

I'm trying to use the OS_VTS_3857_Open_Outdoor.json in maplibre-js, but get an Object { message: "Unimplemented type: 3", stack: "" } error in te console. The map itself loads correctly, but it prevents any layers on the map from rendering.

My map initialisation code is:

const customStyleJson = '/static/other/OS_VTS_3857_Open_Outdoor.json';

// Initialize the map object.
this.map = new maplibregl.Map({
    container: 'map',
    minZoom: 0,
    maxZoom: 18,
    style: customStyleJson,
    maxBounds: [
        [-10.76418, 49.528423],
        [1.9134116, 61.331151]
    ],
    transformRequest: url => {
        if (! /[?&]key=/.test(url)) url += '?key=' + this.osKey
        return {
            url: url + '&srs=3857'
        }
    }
});

Taken from the example on the OS API site.

A number of the qml files in GeoPackage/QGIS Stylesheets (QML) refer to Source Sans Pro, but in current releases of the font this is now called Source Sans 3:

adobe-fonts/source-sans@411dc97

Worked around with:

find -name *.qml -exec sed -i -e "s:Source Sans Pro:Source Sans 3:g" {} \;