Re: [Tagging] Bus relation - circular route - report says not closed

2017-05-19 Thread Martin Koppenhoefer


sent from a phone

> On 19. May 2017, at 11:44, Warin <61sundow...@gmail.com> wrote:
> 
> So there is some setting that prevents me adding a duplicate, probably a very 
> good feature that helps for most things ..


I believe by default in JOSM there is a popup asking whether you really want to 
add another instance of the object to the relation, maybe you have checked 
"don't ask me again" some time in the past. Somewhere there's a "reset 
warnings" button in preferences.

cheers,
Martin 
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Bus relation - circular route - report says not closed

2017-05-19 Thread Jo
Hi George,

Did you watch the accompanying screencast as well? I'm practicing for
SOTM-FR, so I started recording what I'm doing. I'm also planning to do
regular Google Hangouts (on Air) on the subject of PT. Those would be on
European 'evenings', I'm not sure what time it would be in NSW then, but
you would be welcome to join in.

Regarding the stop_area relations, there is a setting to disable those
tests, which should be 'enabled' by default. So those warnings should not
appear for most use cases.

I'll create a ticket for it, then Giacomo can take care of it, when coding
for GSoC starts.

Regarding the settings, Open JOSM, press F12, switch on expert mode in the
lower left, go to the Setting Preferences Entries directly pane and search
for 'add', set "message_add_primitve_to_relation" to false".

I hope that's the one that's influencing that behaviour.

Cheers,


Jo

2017-05-19 11:44 GMT+02:00 Warin <61sundow...@gmail.com>:

> Thanks Jo + George
>
> On 19-May-17 03:18 PM, Georg Feddern wrote:
>
>> Am 19.05.2017 um 04:21 schrieb Warin:
>>
>>>
>>> P1) JOSM validator reports that the relation is not closed. Yet all
>>> elements appear and they are connected.
>>>
>>
>> I cannot verify/reproduce the first part/sentence with JOSM (11639 /
>> 12039).
>>
>>
> Think you got it after Jo modified it. :)
>
> Thank you Jo that makes sense. I am use to forming circular ways for other
> relations ... but they don't contain duplicated members.
> I would have formed something similar ... if I could add duplicated
> members to the relation.
>
> And that is where my problem lies! Any time I try to add a way that is
> already part of the relation .. it does not happen.
> No error message.
> Chose to add at the end or begin of the listed members, or above or below
> the selected member ... not added.
>
> So there is some setting that prevents me adding a duplicate, probably a
> very good feature that helps for most things ..
> but it would be even better in this instance if it simply gave a warning
> message and  allowed a selection of options.
> Perhaps in the past I have turned this setting off?
>
> Humm Control C and V works ... so I'll use that
> The present route is not absolutely correct.. but better than the original
> I had!
> At least now it goes in a circular mode. Just needs an added repetition.
>
> Ok - now it has the correct route! Phew.
>
> I do get a warning - PT: Stop position or platform is not part of a stop
> area relation... 9 of them.
>
>
>> P2) Roles forward/backward are apparently no longer used, and a role to
>>> indicate that both directions does not exist. Yet these may assist to have
>>> these kinds of roles?
>>>
>>
>> Not necessary - see above. 'Used' direction is always defined by order.
>>
>> P3) stop_position ... left side or right side of the way? On a train line
>>> this probably works well .. on a road that has traffic in both directions
>>> with parking on both sides .. stop_position does not have all that much
>>> information.
>>>
>>
>> Yep, thats the way of OSM - the information is in the order of the
>> relation and the platforms.
>>
>> Thoughts?
>>>
>>
>> Done. ;-)
>>
>> Georg
>>
>>
>> _
>>
>
> Ok .. I have some more reading to do on these 'platforms'. Want to get rid
> of that warning.
> And resolve the 'bus stops' too.
>
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Bus relation - circular route - report says not closed

2017-05-19 Thread Warin

Thanks Jo + George

On 19-May-17 03:18 PM, Georg Feddern wrote:

Am 19.05.2017 um 04:21 schrieb Warin:


P1) JOSM validator reports that the relation is not closed. Yet all 
elements appear and they are connected.


I cannot verify/reproduce the first part/sentence with JOSM (11639 / 
12039).




Think you got it after Jo modified it. :)

Thank you Jo that makes sense. I am use to forming circular ways for 
other relations ... but they don't contain duplicated members.
I would have formed something similar ... if I could add duplicated 
members to the relation.


And that is where my problem lies! Any time I try to add a way that is 
already part of the relation .. it does not happen.

No error message.
Chose to add at the end or begin of the listed members, or above or 
below the selected member ... not added.


So there is some setting that prevents me adding a duplicate, probably a 
very good feature that helps for most things ..
but it would be even better in this instance if it simply gave a warning 
message and  allowed a selection of options.

Perhaps in the past I have turned this setting off?

Humm Control C and V works ... so I'll use that
The present route is not absolutely correct.. but better than the 
original I had!

At least now it goes in a circular mode. Just needs an added repetition.

Ok - now it has the correct route! Phew.

I do get a warning - PT: Stop position or platform is not part of a stop 
area relation... 9 of them.




P2) Roles forward/backward are apparently no longer used, and a role 
to indicate that both directions does not exist. Yet these may assist 
to have these kinds of roles?


Not necessary - see above. 'Used' direction is always defined by order.

P3) stop_position ... left side or right side of the way? On a train 
line this probably works well .. on a road that has traffic in both 
directions with parking on both sides .. stop_position does not have 
all that much information.


Yep, thats the way of OSM - the information is in the order of the 
relation and the platforms.



Thoughts?


Done. ;-)

Georg


_


Ok .. I have some more reading to do on these 'platforms'. Want to get 
rid of that warning.

And resolve the 'bus stops' too.

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Bus relation - circular route - report says not closed

2017-05-18 Thread Georg Feddern

Am 19.05.2017 um 04:21 schrieb Warin:


P1) JOSM validator reports that the relation is not closed. Yet all 
elements appear and they are connected.


I cannot verify/reproduce the first part/sentence with JOSM (11639 / 12039).
As the relation editor indeed does verify and show the 'circular' aspect 
of the relation it could anyway be only a validator bug.


P2) Roles forward/backward are apparently no longer used, and a role 
to indicate that both directions does not exist. Yet these may assist 
to have these kinds of roles?


Not necessary - see above. 'Used' direction is always defined by order.

P3) stop_position ... left side or right side of the way? On a train 
line this probably works well .. on a road that has traffic in both 
directions with parking on both sides .. stop_position does not have 
all that much information.


Yep, thats the way of OSM - the information is in the order of the 
relation and the platforms.



Thoughts?


Done. ;-)

Georg


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Bus relation - circular route - report says not closed

2017-05-18 Thread Jo
Hi Warin,

I created a screencast on how I reworked the route relation:

https://www.youtube.com/watch?v=7xY966xwEH0

It's a bit clumsy :-) I should have downloaded more data around the stops.
Then I would have noticed the nodes with highway=bus_stop.

What I wanted to show is that the PT_Assistant plugin can help out a lot
when creating bus route relations.

Were the stops in the relation in the correct order?

On your questions:

1. you get visual feedback from the route relation editor, both on
continuity and on whether the ways in a route form a closed loop/roundtrip.

2. All the ways in PT v2 relations from a long string of connected ways. If
the vehicle passed them more than once, they are also in the relation more
than once.

3. stop_position nodes are nodes that are part of the ways. For buses they
are not extremely useful. The highway=bus_stop nodes had already been
mapped before and one of them had a name and information about the bus
lines that serve it. I moved this to route_ref. These are the nodes that
contain such details, so as far as I'm concerned these are the nodes that
should be added to the route relations. For PT v2 they get a
public_transport=platform tag.

If there are actual platforms, they also get the public_transport=platform
tag, but those are mapped as ways or areas. If you like them to be
rendered, you can give them additional highway=platform (or
railway=platform for tram and train lines) tags.

I don't see any need to add such platform ways to the route relations. If
you like you can add them to public_transport=stop_area relations, along
with the corresponding platform and stop_position nodes and shelters,
waste_baskets and benches.

Polyglot

2017-05-19 4:21 GMT+02:00 Warin <61sundow...@gmail.com>:

> Hi,
>
> I have made a new relation: 7258397 - a bus route 686 that is 'circular'
> in that it returns back to the same start position and then repeats the
> same route.
>
> Some of the route travels in both directions on the same ways, while other
> parts only use a way in one direction.
>
> P1) JOSM validator reports that the relation is not closed. Yet all
> elements appear and they are connected.
>
> P2) Roles forward/backward are apparently no longer used, and a role to
> indicate that both directions does not exist. Yet these may assist to have
> these kinds of roles?
>
> P3) stop_position ... left side or right side of the way? On a train line
> this probably works well .. on a road that has traffic in both directions
> with parking on both sides .. stop_position does not have all that much
> information.
>
>
> Thoughts?
>
>
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


[Tagging] Bus relation - circular route - report says not closed

2017-05-18 Thread Warin

Hi,

I have made a new relation: 7258397 - a bus route 686 that is 'circular' 
in that it returns back to the same start position and then repeats the 
same route.


Some of the route travels in both directions on the same ways, while 
other parts only use a way in one direction.


P1) JOSM validator reports that the relation is not closed. Yet all 
elements appear and they are connected.


P2) Roles forward/backward are apparently no longer used, and a role to 
indicate that both directions does not exist. Yet these may assist to 
have these kinds of roles?


P3) stop_position ... left side or right side of the way? On a train 
line this probably works well .. on a road that has traffic in both 
directions with parking on both sides .. stop_position does not have all 
that much information.



Thoughts?



___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging