Peter Miller <peter.mil...@itoworld.com> schrieb: > > On 1 Aug 2009, at 22:51, Thomas Wood wrote: <snip> > > Ooops, I linked the wrong changeset! > > http://api06.dev.openstreetmap.org/browse/changeset/389 was my > > intent. > > A couple of comments. > > Firstly, the locality field is an important part of the name in > NaPTAN. The stop name can be constructed in a number of ways > depending on how much precision is needed and what the geographic > context is. > > For example, let's take this stop outside a pub called 'The > Woodman' (which is in Ashteed). > http://api06.dev.openstreetmap.org/browse/node/396115 > > If the context for the enquiry was Ashteed itself, then one could > say 'The Woodman (Adj)'. If the context was wider and one still > needed to be precise one would say: 'Ashteed, The Woodman (Adj)'. > > Localities themselves are not always unique so there is the > possibility for a locality to have a qualifier in NaPTAN. The full > description for a bus stop called 'Long Road' in Cambridge in > Cambridgeshire (rather than the one in Gloucestershire) would be > 'Cambridge (Cambs), Long Road (opp)'. If the context was east anglia > then one could drop the qualifier and it would become 'Cambridge, > Long Road (opp)'. If the context was Cambridge itself then one could > use 'Long Road (opp)'. > > So... what to do. I suggest we need a naptan:locality field which > should contain the naptan locality name or possibly also > naptan:natgazid as a unique reference for the place (to accommodate > multiple localities with the same name). > > I am not clear what we do, but we need to do something.
To me the functionality of the naptan:locality tag appears to be similar to the one of the is_in tag on places. With the introduction of boundaries these tags become less important in my opinion as you can easily find out the location of a feature by looking in which areas it is in. I think, putting the NaPTAN data in OSM is similar to drawing them on a map: The map (i.e. OSM) provides a rich context from which much information wich was stored as properties of the bus stops before can be derived. Cheers, Christoph > > Regards, > > > > Peter > > > > > > > > >> > >>> We're then ready to begin uploading to the main database. > >> > >> Cool :-) > >> > >> Cheers, > >> Christoph > >> > >> _______________________________________________ > >> Talk-transit mailing list > >> Talk-transit@openstreetmap.org > >> http://lists.openstreetmap.org/listinfo/talk-transit > >> > > > > > > > > -- > > Regards, > > Thomas Wood > > (Edgemaster) > > > > _______________________________________________ > > Talk-transit mailing list > > Talk-transit@openstreetmap.org > > http://lists.openstreetmap.org/listinfo/talk-transit > > > _______________________________________________ > Talk-transit mailing list > Talk-transit@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-transit _______________________________________________ Talk-transit mailing list Talk-transit@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-transit
