[Qgis-user] Help with Ordnance Survey SLD's for OS Mastermap

[David James]

Thank you.

I'll grab those and see how I get on with them.

David

> You can grab QGIS styles for OSMM here:
>
> https://github.com/mixedbredie/QGIS-styles/tree/master/OSMM
>
> and here:
>
> https://github.com/QGIS-UK/Styles/tree/master/OSMM
>
> The QML and SLDs depend on the schema of the source data (GML, shapefiles)
> and how they are loaded into the database (Loader!, GoLoader, Productivity
> Suite).  Usually descriptiveterm, descriptivegroup and make are used for
> the styles.
>
> These SLD files for OSMM are based on the OS styles but without the
> reference to os_cat field.
>
> https://github.com/mixedbredie/Geoserver-OS-SLDs
>
> hope that helps a bit.
>
> Ross
>
> From: qgis-user-bounces at lists.osgeo.org
> [mailto:qgis-user-bounces at lists.osgeo.org] On Behalf Of Thomas Colley
> Sent: 01 September 2014 09:35
> To: Giuseppe Sucameli; David James
> Cc: qgis-user ML
> Subject: Re: [Qgis-user] Help with Ordnance Survey SLD's for OS Mastermap
>
> os_cat is a field used for styling in OS layers. The complication is (at
> least last I checked) the field doesn’t exist in the data as shipped.
> There are some SQL files on the OS website for creating os_cat (calculated
> from a combination of other fields) in PostGIS, but I’m not sure how
> that would be applied to shapefiles.
>
> I’m sure that OS have released proper QGIS Style Files now as well as
> SLDs. I can’t find them at the minute (too early on a Monday morning)
> but I’ll let you know when I do.
>
> Cheers
>
> Tom
>
> From:
> qgis-user-bounces at lists.osgeo.org<mailto:qgis-user-bounces at lists.osgeo.org>
> [mailto:qgis-user-bounces at lists.osgeo.org]<mailto:[mailto:qgis-user-bounces at lists.osgeo.org]>
> On Behalf Of Giuseppe Sucameli
> Sent: 01 September 2014 08:34
> To: David James
> Cc: qgis-user ML
> Subject: Re: [Qgis-user] Help with Ordnance Survey SLD's for OS Mastermap
>
>
> Hi David,
> IIRC that kind of variables are not supported by QGIS neither by the SLD
> standard.
>
> You must replace it with the correct SVG filename.
>
> Anyway, what is "os_cat" supposed to be? Is it a layer's field name?
>
> Regards.
>
> Sent from mobile. Sorry for being short.
> --
> Giuseppe Sucameli
> Il 01/set/2014 00:01 "David James"
> <david at djames.org.uk<mailto:david at djames.org.uk>> ha scritto:
> I'm very much a beginner with QGIS and I'm trying to run long before I
> can crawl ...
>
> I'm trying to use the Ordnance Survey MasterMap Topography layer SLD's
> (from
> http://www.ordnancesurvey.co.uk/docs/styled-layer-descriptors/topography-sld.zip)
> to style the sample OS MasterMap data.
>
> Initially, I found that when I loaded the SLD file into QGIS, only the
> first rule was being picked up, but eventually I found tjmgis's answer
> in
> http://gis.stackexchange.com/questions/69854/styling-os-vectormap-local-in-qgis
> (that all the <FeatureTypeStyle> and </FeatureTypeStyle> except the
> first and the last in the SLD files need removing) and now I'm making
> progress.
>
> I'm struggling with one problem: there's a rule called
> <Name>Vegetation (pattern) - 1:35 to 1:3,496</Name>
> which specifies the SVG file as
> xlink:href="osmmsymbols/${os_cat}.svg"/>
>
> QGIS is showing me question marks in these areas (which I think means it
> is not finding the SVG file).
>
> Does QGIS support this use of ${os_cat} (and if so, what do I need to do
> to make it work?) or do I have to replicate the rule with explicitly
> named SVG files for all the different vegetation types?
>
> David
>
> --
> David James
> david at djames.org.uk<mailto:david at djames.org.uk>
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org<mailto:Qgis-user at lists.osgeo.org>
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>
> This message is strictly confidential. If you have received this in error,
> please inform the sender and remove it from your system. If received in
> error you may not copy, print, forward or use it or any attachment in any
> way. This message is not capable of creating a legal contract or a binding
> representation and does not represent the views of Angus Council. Emails
> may be monitored for security and network management reasons.  Messages
> containing inappropriate content may be intercepted. Angus Council does
> not accept any liability for any harm that may be caused to the recipient
> system or data on it by this message or any attachment.
>