I have not been able to follow the large number of posts on this group in
recent weeks - but I can confirm that stopareas are an important part of
NaPTAN data in the UK, and are an important aspect of the way that stops
data are used in journey planning applications. It would be a pity if OSM
On 01/22/2011 11:04 PM, Richard Fairhurst wrote:
Dominik Mahrer (Teddy) wrote:
IMHO not related to the proposal:
- potlatch can not handle the proposal/nested relations correctly:
The latest version of Potlatch (Potlatch 2) handles nested relations
excellently. About 10 seconds' research
Am 24.01.2011 10:00, schrieb Dominik Mahrer (Teddy):
On 01/22/2011 11:04 PM, Richard Fairhurst wrote:
Dominik Mahrer (Teddy) wrote:
IMHO not related to the proposal:
- potlatch can not handle the proposal/nested relations correctly:
The latest version of Potlatch (Potlatch 2) handles nested
On 01/22/2011 08:38 PM, Michał Borsuk wrote:
On 01/22/2011 09:32 AM, Dominik Mahrer (Teddy) wrote:
- stop_area is not needed/too complicated:
[...]And it does not seam to be too complicated,
And as for not needed: can we have a *separate discussion* on how
routing works? There had already
On 01/24/2011 10:10 AM, Michał Borsuk wrote:
As far as I understand the issue, stop areas are used to tie different
stops into one transferring area.
No, you did not understand correct. stop_area_group is (was?) for that.
Teddych
___
Talk-transit
Am 24.01.2011 10:39, schrieb Dominik Mahrer (Teddy):
On 01/24/2011 10:10 AM, Michał Borsuk wrote:
As far as I understand the issue, stop areas are used to tie different
stops into one transferring area.
No, you did not understand correct. stop_area_group is (was?) for that.
Then what is the
On Mon, Jan 24, 2011 at 9:10 AM, Michał Borsuk michal.bor...@gmail.comwrote:
Am 24.01.2011 09:39, schrieb Roger Slevin:
I have not been able to follow the large number of posts on this group in
recent weeks - but I can confirm that stopareas are an important part of
NaPTAN data in the UK,
On 01/24/2011 11:00 AM, Michał Borsuk wrote:
Am 24.01.2011 10:39, schrieb Dominik Mahrer (Teddy):
On 01/24/2011 10:10 AM, Michał Borsuk wrote:
As far as I understand the issue, stop areas are used to tie different
stops into one transferring area.
No, you did not understand correct.
Frankie, I think you have mentioned some good examples.
For simple pairs or even small clusters of stops then a stoparea often can be
defined by rules – and indeed the systems I am working with in the UK uses such
rules to define an “implicit” stoparea – the rules we use are that the
On 23.01.2011 13:18, Michał Borsuk wrote:
On 01/23/2011 12:57 PM, Vincent Privat wrote:
2011/1/23 Michał Borsuk michal.bor...@gmail.com
mailto:michal.bor...@gmail.com
Could you please explain what you mean, because I'm not sure. The
links provided show bus routes with nothing
On Mon, Jan 24, 2011 at 11:40 AM, Christian christ...@balticfinance.com wrote:
but it also includes people ... who would like to map also
physical path a bus takes on the street.
I think there's a logic in encouraging the use of ordered relations to
show the paths of bus/etc routes - because
Michał Borsuk michal.borsuk at gmail.com writes:
Continuing on How routing software works (and why OSM as-is is not
ready for routing):
Hello,
makes perfect sense, assuming OSM is mapping, not routing project and some other
layer will be needed for the routing.
Just a small set of
On 01/24/2011 12:40 PM, Christian wrote:
On 23.01.2011 13:18, Michał Borsuk wrote:
No, this can't be done in such detail, but it's not necessary as of
2011. All you need to know is where is the bus stop for the direction
you're interested in, or whether the bus stop you found serves you
On 01/24/2011 02:09 PM, Richard Mann wrote:
On Mon, Jan 24, 2011 at 11:40 AM, Christianchrist...@balticfinance.com wrote:
but it also includes people ... who would like to map also
physical path a bus takes on the street.
I think there's a logic in encouraging the use of ordered relations to
On 01/24/2011 03:04 PM, Oleksandr Vlasov wrote:
Michał Borsukmichal.borsukat gmail.com writes:
Just a small set of questions:
1. As I can see, currently stop-on-a-way is the preferred approach for mapping
tram stops. Do you propose to map tram stops like bus ones, i.e. beside the way?
I'd
On 01/24/2011 12:40 PM, Christian wrote:
On 23.01.2011 13:18, Michał Borsuk wrote:
No, this can't be done in such detail, but it's not
necessary as of
2011. All you need to know is where is the bus stop for
the direction
you're interested in, or whether the bus stop you found serves
On 01/24/2011 07:24 PM, Michał Borsuk wrote:
On 01/24/2011 03:04 PM, Oleksandr Vlasov wrote:
3. bus_stop already defines `ref' tag, will proposed `stop_id' be
something
different?
ref= on a bus stop? That's news to me (sadly). I used stop_id=, but the
mess probably comes from the fact that
On 01/24/2011 10:16 AM, Dominik Mahrer (Teddy) wrote:
On 01/22/2011 08:38 PM, Michał Borsuk wrote:
On 01/22/2011 09:32 AM, Dominik Mahrer (Teddy) wrote:
The more exact the OSM map is, the
more likely it is that the two directions do not share the same way for
the both directions (the lines
On 01/25/2011 12:19 AM, Michał Borsuk wrote:
On 01/24/2011 11:38 PM, Christian Krützfeldt wrote:
If disagree then please attack my arguments with
counter-arguments. I stand by what I wrote.
Well, I could agree with you that your proposal is fine for most usage
cases. But below you say it
On 01/24/2011 11:22 AM, Dominik Mahrer (Teddy) wrote:
By the way, I have removed stop_area_group from the proposal.
In essence this is good. I tried to implement this concept in OSM, but
could not find (come up with) a sensible standard.
Then what is the exact difference between
On 01/24/2011 11:06 AM, Frankie Roberto wrote:
[...] I don't think you'd consider Embankment and
Charing Cross stations to be part of the same stop area, even though
they're very close to each other? On the other hand, some stop areas
(Waterloo perhaps) may be huge, even though it may take you
On Tuesday, January 25, 2011 at 00:23 CET,
Michal Borsuk michal.bor...@gmail.com wrote:
On 01/25/2011 12:19 AM, Michal Borsuk wrote:
Graphically lost, so no arrows (that didn't work anyway, because
there are streets in which bus A runs one-way north, bus B runs
one-way south, and
22 matches
Mail list logo
