<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:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
<
--
/* Font Definitions */
@font-face
{Cambria Math"}
p.MSONORMAL
{mso-style-unhide:no;
mso-style-qformat:yes;
"
Calibri"
"
sans-serif"
mso-ascii-theme-font:minor-latin;
mso-fareast-theme-font:minor-latin;
mso-hansi-theme-font:minor-latin;
Times New Roman"
mso-bidi-theme-font:minor-bidi;}
li.MSONORMAL
{mso-style-unhide:no;
mso-style-qformat:yes;
"
Calibri"
"
sans-serif"
mso-ascii-theme-font:minor-latin;
mso-fareast-theme-font:minor-latin;
mso-hansi-theme-font:minor-latin;
Times New Roman"
mso-bidi-theme-font:minor-bidi;}
div.MSONORMAL
{mso-style-unhide:no;
mso-style-qformat:yes;
"
Calibri"
"
sans-serif"
mso-ascii-theme-font:minor-latin;
mso-fareast-theme-font:minor-latin;
mso-hansi-theme-font:minor-latin;
Times New Roman"
mso-bidi-theme-font:minor-bidi;}
.MSOCHPDEFAULT
{mso-default-props:yes;
mso-ascii-theme-font:minor-latin;
mso-fareast-theme-font:minor-latin;
mso-hansi-theme-font:minor-latin;
Times New Roman"
mso-bidi-theme-font:minor-bidi;}
-->
/* Font Definitions */
@font-face
{font-family:Batang;
panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@Batang";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
line-height:115%;
font-size:11.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
p.quot, li.quot, div.quot
{mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;
font-weight:normal;
font-style:normal;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</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=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;line-height:115%;font-family:Arial;color:navy'>Brian<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;line-height:115%;font-family:Arial;color:navy'>Stoptype HAR has
sub-records which contain two pairs of coordinates, one representing the entry
point to the linear footprint, and the other representing the exit point. If
guidance has been followed, then the linear footprint should stay on a road
link with the same name along its length (but evidence indicates that the rules
are not always followed strictly, either because they have been overlooked, or
because the creator of the data hasn’t appreciated where a road name changes
takes effect). An HAR stop is a three point linear feature, anchored on the “central”
point of the three.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;line-height:115%;font-family:Arial;color:navy'>Stoptype FLX has
sub-records which contain three or more pairs of coordinates which represent
the boundary of the zone which is being described. The guidance indicates that
the polygon formed by linking the points with straight lines should cover the
relevant area – but of course it does not have to be precise, The points
should be in sequence within the sub-records – and generally will be points
where the boundary intersects roads entering/leaving the zone, plus additional
points that pull the boundary so that it completely bounds the zone. In this
process the inclusion of non-significant territory is normally ignored – the test
is “does the zone cover all the roads that could be used by the Demand
Responsive Transport service, and does it not cover any sections of road that
are not to be used by the DRT service?”<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;line-height:115%;font-family:Arial;color:navy'>I don’t have an easy way
to check on the number of HAR and FLX stops there are across the country. HAR
is quite common across the whole country. FLX exist in relatively few very
rural areas – with <st1:City w:st="on"><st1:place w:st="on">Lincolnshire</st1:place></st1:City>
being one county which has a lot of them. There are few if any, however, in
the whole of the South East region at present. Peter from Ito may be able to
check more easily on the totals than I can.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;line-height:115%;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<p><font size=2 color=navy face=Arial><span lang=EN-US style='font-size:10.0pt;
font-family:Arial;color:navy'>Roger</span></font><font color=navy><span
lang=EN-US style='color:navy'> </span></font><o:p></o:p></p>
</div>
<div>
<div class=MsoNormal align=center style='margin-bottom:0cm;margin-bottom:.0001pt;
text-align:center;line-height:normal'><font size=3 face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman"'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal style='margin-bottom:0cm;margin-bottom:.0001pt;line-height:
normal'><b><font size=2 face=Tahoma><span lang=EN-US style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span lang=EN-US style='font-size:10.0pt;font-family:Tahoma'>
talk-transit-bounces@openstreetmap.org
[mailto:talk-transit-bounces@openstreetmap.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Brian Prangle<br>
<b><span style='font-weight:bold'>Sent:</span></b> 28 February 2009 10:11<br>
<b><span style='font-weight:bold'>To:</span></b> talk-transit@openstreetmap.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Talk-transit] NaPTAN bus
stop database import</span></font><font size=3 face="Times New Roman"><span
lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt;
line-height:115%'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:0cm;margin-bottom:.0001pt;line-height:
normal'><font size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Hi
All<br>
<br>
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<br>
<br>
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<br>
<br>
<br>
Three questions:<br>
<br>
<br>
</span></font><font size=3 face="Times New Roman"><span style='font-size:12.0pt;
font-family:"Times New Roman"'><o:p></o:p></span></font></p>
<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">
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
line-height:115%;font-family:Arial'>Hail and ride section of route, with a
linear footprint.</span></font><font face=Arial><span style='font-family:Arial'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
line-height:115%;font-family:Arial'>Flexible zone, with an area footprint.</span></font><font
face=Arial><span style='font-family:Arial'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
line-height:115%;font-family:Arial'>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)</span></font><font face=Arial><span
style='font-family:Arial'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
line-height:115%;font-family:Arial'>2.Thomas- 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?</span></font><font face=Arial><span style='font-family:Arial'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
line-height:115%;font-family:Arial'>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?</span></font><font face=Arial><span
style='font-family:Arial'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:11.0pt;
line-height:115%;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
line-height:115%;font-family:Arial'>An observation</span></font>:<o:p></o:p></p>
<p class=MsoNormal><font size=2 face=Calibri><span style='font-size:11.0pt;
line-height:115%'>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?<o:p></o:p></span></font></p>
</div>
</body>
</html>