<div dir="ltr">Hi Jo,<div>I can't say much about the Astun loader as our own MasterMap, including COU's, uses FME - not Open Source, but it works well for us without having any technical requirements not it has been created.</div>
<div><br></div><div>More to the point, I do have MasterMap (and other OS styles) I can share, but they're in SLD's. There are actually two sets of MasterMap styles.</div><div>I'm not sure if there are any tools for converting CartoCSS to SLD (I believe CCSS is translated to SLD for rendering). Do they have to be CartoCSS?</div>
<div>We're using GeoServer, hence SLD's, though CSS styling has just been an extension I believe.</div><div><br></div><div>Examples:<br>
<div class="gmail_extra"><div><br></div><div><img src="cid:ii_141e06ea3b75caa2" alt="Inline images 1"><br></div><div><br></div><div><br></div><div><img src="cid:ii_141e06f0e1a62bd7" alt="Inline images 2"><br></div><div><br>
</div><div>Regards,<br></div><div>Jonathan</div><div><br></div>
<br><br><div class="gmail_quote">On 22 October 2013 13:33, Walsh, Joanna <span dir="ltr"><<a href="mailto:Joanna.Walsh@ros.gov.uk" target="_blank">Joanna.Walsh@ros.gov.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>dear all,<div><br></div><div>I promised to move a Twitter conversation about change-only updates to MasterMap data here to the list. Half-term is over and i am back at the desk. Here goes.</div><div><br></div><div>The story so far. At Registers of Scotland we are setting up a sort of in-house, custom OS On Demand-type service, there is a business requirement to make maps with no internet access if needed. </div>
<div>There is a license for a proprietary software package to handle imports and updates for OS MasterMap. Our architect urged us to use this package if possible, specifically because it claims to automatically handle "change-only updates" to MasterMap. The goals are as much automation as possible and as little technical debt as possible. </div>
<div><br></div><div>We tried it out and i really don't like the look of what it does with the database. It looks like an Oracle Spatial database which someone has minimally ported to Postgres but not really tested for retrieval. The tables are created with *no integer primary keys*, and forcing case-sensitivity with double quotes in table and column names has upset TileMill quite badly :/ It looks like there's going to be lot of analysing and indexing work needed to be done to make that data queryable at decent speed. This is not the behaviour i expect of a package whose marketing pitch is that it takes the pain away - if we frot the data, we lose the seamlessness of the update support anyway.</div>
<div><br></div><div>I downloaded the Astun Loader from github. It Just Worked TM, and because it hands over the PostGIS conversation to OGR, what comes out appears right and doesn't need optimisation.</div><div><a href="https://github.com/AstunTechnology/Loader" target="_blank">https://github.com/AstunTechnology/Loader</a></div>
<div><br></div><div>So what am i asking the list for now?</div><div><br></div><div>- A way to reassure our architect that the open solution WILL lead to much less technical debt in the medium term </div><div>- A straw poll of others in the OSGeo UK community. Some of you will already have in-house processes in place for dealing with change-only updates. If anyone's built that on the Astun Loader, are there any strong reasons that couldn't be contributed to github? (Embedded configuration / no benefit of releasing?) </div>
<div><br></div><div>Politically; i think we could contribute to a project that had started, but i don't think we'd be able to start one. Whoever did would get the benefit of lower maintenance burden and be able to bake in their requirements. </div>
<div><br></div><div>There's a parallel thread here concerning MapBox/TileMill/CartoCSS. I'm sketching out some CartoCSS stylesheets for MasterMap. I am not a cartographer or a designer, just doing the logic.</div>
<div>Anyway, the stylesheet is in part a model of what comes out of the Astun loader, closely tied to the PostGIS schema, so these are two sides of the same coin, right? </div><div>It'd be interesting to see a few common public styles. We may need a minimal Land-Line style and it would be hilarious to see an OSM style. </div>
<div><br></div><div>Thoughts apprec.,</div><div><br></div><div><br></div><div>Jo</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><div><br></div> </div>
<div> </div>
<div><span style="font-size:18pt;color:rgb(0,127,0);font-family:Webdings">P</span><b><font face="Arial" color="#007f00" size="1"><span style="font-weight:bold;font-size:7.5pt;color:rgb(0,127,0);font-family:Arial"> P</span></font></b><font face="Arial" color="#007f00" size="1"><span style="font-size:7.5pt;color:rgb(0,127,0);font-family:Arial">lease consider the environment - do you really need to print this email?</span></font>
</div></div>
<br>_______________________________________________<br>
UK mailing list<br>
<a href="mailto:UK@lists.osgeo.org" target="_blank">UK@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/uk" target="_blank">http://lists.osgeo.org/mailman/listinfo/uk</a><br></blockquote></div><br></div></div></div>
<br>
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;background-color:rgb(255,255,255)">This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.</span>