<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Awesome Brain. I shall digest and come back with comments.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>What’s the timescale for implementation?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Andy<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Prangle [mailto:bprangle@gmail.com] <br><b>Sent:</b> 16 January 2017 20:53<br><b>To:</b> talk-gb-westmidlands<br><b>Subject:</b> [Talk-gb-westmidlands] Collaboration with TfWM<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hi everyone<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>I had a great meeting with TfWM today . Essentially they're planning a complete revamp of their website and provision of public information and have come to the conclusion that OSM is the base map they need to use.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>I'll be spending half a day a week with their key developers in exploring which data needs to be updated in OSM and which they will keep as their own layer. They are well-advanced in preparing their cartographic style and providing their own tile server.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>We've agreed to use Birmingham City Centre(i.e inside the inner ring road) as a pilot area. Once we've ironed out data and editing issues and how to work with each other and the pilot has been successful, we'll roll out through the major interchanges.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Editing and maintaining public transport data is not an easy task and one we've failed at, despite our best efforts, so there's a potential to do several imports.<o:p></o:p></p></div><div><p class=MsoNormal>1.There's a new opendata NapTAN dataset which is more accurate (<1m now with gps cleardowns from bus sensors) and with more attributes than our previous set which is now over 6 years old and never completed tagging from import. Many of our bus stops surveyed years ago have probably been deleted. Clearing up the partially completed and out-of date data we have with the new data we are never going to do manually so I like the local community's views on using an import in the proposed pilot area<o:p></o:p></p></div><div><p class=MsoNormal>2. Swift Collectors are being installed in bus stations and bus shelters and on bus poles ( these are top-up points not payment points) and we already have the data. Once the tagging schema is sorted out (see separate posts) this would make a great import. Views on this also please.<o:p></o:p></p></div><div><p class=MsoNormal>3. Metro extensions that have secured a funding stream - we can have the data- this is not huge and is manageable with manual editing<o:p></o:p></p></div><div><p class=MsoNormal>4. Electric charge points - import or manual? Might be manageable manually initially but is only going one way and that's up.<o:p></o:p></p></div><div><p class=MsoNormal>5. I also asked TfWM for updates and data on any major upgrades as they take place (bus/railway stations and interchanges)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>This discussion is not about a general import across the UK it's specifically aimed at the West Midlands community where the imports are proposed and is aimed at building a relationship with a key player in the region, taking pressure off key OSM contributors, and improving the map at a rate we can't achieve manually.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>regards<o:p></o:p></p></div><div><p class=MsoNormal>Brian<o:p></o:p></p></div></div></div></body></html>