<font size="2"><span style="font-family: arial,helvetica,sans-serif;">Hi All</span><br style="font-family: arial,helvetica,sans-serif;"><br style="font-family: arial,helvetica,sans-serif;"><span style="font-family: arial,helvetica,sans-serif;">I've added to Thomas's initial work and completed what I think we should import and what the tagging scheme should look like in <a href="http://wiki.openstreetmap.org/wiki/NaPTAN/Tag_mappings">http://wiki.openstreetmap.org/wiki/NaPTAN/Tag_mappings</a>. Please take a look and shoot down in flames/agree/amend: particularly inclusion/exclusion proposals</span><br style="font-family: arial,helvetica,sans-serif;">
<br style="font-family: arial,helvetica,sans-serif;"><span style="font-family: arial,helvetica,sans-serif;">Generally if the text of the proposed tag following the naptan: preamble is in the format "word1_word2" it is our substitute for an ambiguous or verbose NaPTAN field name, otherwise it's a copy (complete with CapitiLisation) of the NaPTAN field name</span><br style="font-family: arial,helvetica,sans-serif;">
<br style="font-family: arial,helvetica,sans-serif;"><br style="font-family: arial,helvetica,sans-serif;"><span style="font-family: arial,helvetica,sans-serif;">Three questions:</span><br style="font-family: arial,helvetica,sans-serif;">
<br style="font-family: arial,helvetica,sans-serif;"></font><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link style="font-family: arial,helvetica,sans-serif;" rel="File-List" href="file:///C:%5CUsers%5CBrian%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link style="font-family: arial,helvetica,sans-serif;" rel="themeData" href="file:///C:%5CUsers%5CBrian%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link style="font-family: arial,helvetica,sans-serif;" rel="colorSchemeMapping" href="file:///C:%5CUsers%5CBrian%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:1;
mso-generic-font-family:roman;
mso-font-format:other;
mso-font-pitch:variable;
mso-font-signature:0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-1610611985 1073750139 0 0 159 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-fareast-language:EN-US;}
.MsoPapDefault
{mso-style-type:export-only;
margin-bottom:10.0pt;
line-height:115%;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<p style="font-family: arial,helvetica,sans-serif;" class="MsoNormal"><font size="2">Hail and ride section of route, with a linear footprint.</font></p>
<p style="font-family: arial,helvetica,sans-serif;" class="MsoNormal"><font size="2">Flexible zone, with an area footprint.</font></p>
<p style="font-family: arial,helvetica,sans-serif;" class="MsoNormal"><font size="2">1.Presumably these are represented for HAR with 2 nodes (start
and end) and for FLX with multiple nodes (min 3) for which we would have to
draw a way between them and add a tag to the way. (naptan:HAR=yes and
naptan:FLX=yes)</font></p>
<p style="font-family: arial,helvetica,sans-serif;" class="MsoNormal"><font size="2">2.Thomas- <span style=""> </span>how easy is
this to add the way and tag it within the import process or should drawing the way and tagging it be left
to manual intervention? Roger – how many of these are there?</font></p><p style="font-family: arial,helvetica,sans-serif;" class="MsoNormal"><font size="2">3. If we can agree the entire tagging and import scheme would we get any extra benefit from offering it for discussion on talkgb or should we just get on with it?<br>
</font></p><p style="font-family: arial,helvetica,sans-serif;" class="MsoNormal"><font size="2"><br></font></p><p class="MsoNormal"><font size="2"><span style="font-family: arial,helvetica,sans-serif;">An observation</span></font>:</p>
<p class="MsoNormal">With about 30 fields to be imported are editor screens going to look too cluttered for the average OSMer? TIGER data takes up a lot of screen real estate and there's a lot less fields. Should we (can we) cull the fields to be imported?<br>
</p><p class="MsoNormal"></p>