<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.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=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Google take a feed of NaPTAN stop point data – and hence
something like Piccadilly Gardens in Manchester is a mass of them.<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'>NaPTAN does have the facility to hold stoparea data – but the
data is not fully populated (as it is not useful when presenting journey
itineraries to the public – or local information systems have their own way of
creating such stopareas on the fly without requiring the data to be held
explicitly in NaPTAN records).<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'>We did experiment with using stopareas with Google – but the
need to link the data to Google Transit for specific journey planning meant
that you were told to catch a  bus at, say, Piccadilly Gardens – rather than
from stop 10 at Piccadilly Gardens ... and for itineraries to be useful, the “stop
10” bit is quite important!<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'>Roger<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>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>

<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"'> talk-transit-bounces@openstreetmap.org
[mailto:talk-transit-bounces@openstreetmap.org] <b>On Behalf Of </b>Frankie
Roberto<br>
<b>Sent:</b> 01 June 2009 08:34<br>
<b>To:</b> talk-transit@openstreetmap.org<br>
<b>Subject:</b> Re: [Talk-transit] Public transport workshop in Germany<o:p></o:p></span></p>

</div>

<p class=MsoNormal><o:p> </o:p></p>

<p class=MsoNormal><o:p> </o:p></p>

<div>

<p class=MsoNormal>On Mon, Jun 1, 2009 at 8:05 AM, Peter Miller <<a
href="mailto:peter.miller@itoworld.com">peter.miller@itoworld.com</a>>
wrote:<o:p></o:p></p>

<div>

<p class=MsoNormal> <o:p></o:p></p>

</div>

<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>

<div>

<div>

<p class=MsoNormal style='margin-bottom:12.0pt'>> The current situation with
bus stops is more messy. (Just see<br>
> Birmigham which seems to entirely consist of bus stops.) While<br>
> stop places in the new schema allow to clean this up a bit, again,<br>
> the renderer only has the choice to either paint two many<br>
> symbols (all access points or all stopping points) or badly<br>
> guess where to put the single point.<o:p></o:p></p>

</div>

</div>

<p class=MsoNormal>Which rendering view are you using? for the main Mapnik view
on<br>
openstreetmap there are no bus stops until one zooms in to zoom 17 at<br>
which point there are certainly lots of bus stops (accesses).<o:p></o:p></p>

</blockquote>

</div>

<p class=MsoNormal><br>
It's good to see that we're not the only ones with this problem, though. 
Google Maps seems to render a huge number of bus stops now that they've
imported public transit data for the uk. See <a
href="http://www.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=manchester,+uk&sll=37.579413,-95.712891&sspn=30.958234,75.234375&ie=UTF8&ll=53.479797,-2.239387&spn=0.005708,0.018368&z=16">http://www.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=manchester,+uk&sll=37.579413,-95.712891&sspn=30.958234,75.234375&ie=UTF8&ll=53.479797,-2.239387&spn=0.005708,0.018368&z=16</a>
for instance.<br>
<br>
That view contains two bus stations (by Piccadilly Gardens and the coach
station by Chorlton Street), and yet both a rendered simply as a mass of access
points, rather than a singular named node (which would be more useful).<br>
<br>
So if we can solve this problem, we'll be one up on Google! :-)<br>
<br>
Frankie<br>
<br>
P.S It's good to see that platforms are now rendering on Mapnik (see <a
href="http://www.openstreetmap.org/?lat=53.477811&lon=-2.243247&zoom=18&layers=B000FTF">http://www.openstreetmap.org/?lat=53.477811&lon=-2.243247&zoom=18&layers=B000FTF</a>),
however I note that it's not coping well with platforms that are areas (as
closed ways with area=yes).  Having blue arrows on the tramlines that are
marked with oneway=yes is also a little odd.<br clear=all>
<br>
-- <br>
Frankie Roberto<br>
Experience Designer, Rattle<br>
0114 2706977<br>
<a href="http://www.rattlecentral.com">http://www.rattlecentral.com</a><br>
<br>
Sent from Manchester, Greater Manchester, United Kingdom <o:p></o:p></p>

</div>

</body>

</html>