Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 11:01, Chris Hunter chunter...@gmail.com wrote:
 Moving back to one of my original questions, I think Nakor was the only one
 to respond to the 2 relations per state (1 relation each way) vs 1 relation
 with rolls per state question.

Why does there need to be 2 relations for this?

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread Apollinaris Schoell
On Mon, Feb 8, 2010 at 5:07 PM, John Smith deltafoxtrot...@gmail.comwrote:



 Why does there need to be 2 relations for this?

 besides editing convenience a relation is directed and sorted since API 0.6
You can see it as a route to follow from start to end. For bus routes this
is a must. 2 relations may use the same road in different directions. on a
highway ref one can argue this is not needed but it's still a good idea.


 ___
 talk mailing list
 talk@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread Chris Hunter
On Mon, Feb 8, 2010 at 8:21 PM, Apollinaris Schoell ascho...@gmail.comwrote:



 On Mon, Feb 8, 2010 at 5:07 PM, John Smith deltafoxtrot...@gmail.comwrote:



 Why does there need to be 2 relations for this?

 besides editing convenience a relation is directed and sorted since API
 0.6 You can see it as a route to follow from start to end. For bus routes
 this is a must. 2 relations may use the same road in different directions.
 on a highway ref one can argue this is not needed but it's still a good
 idea.



Another thing to remember is that the relation analyzer and relation
browsers don't support super-relations *yet*.  My gut feeling is that if we
start using super-relations in a consistent manner, it's more likely that
the analyzer (and hopefully the API) will begin supporting them
consistantly.

In the long run, using super-relations to create relation hierarchy would
allow us to separate physical attributes of a way (or node) from the logical
attributes of a route.

 ___
 talk mailing list
 talk@openstreetmap.org

 http://lists.openstreetmap.org/listinfo/talk



___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 11:21, Apollinaris Schoell ascho...@gmail.com wrote:
 besides editing convenience a relation is directed and sorted since API 0.6
 You can see it as a route to follow from start to end. For bus routes this
 is a must. 2 relations may use the same road in different directions. on a
 highway ref one can argue this is not needed but it's still a good idea.

So apply roles, I don't see why this needs to be 2 relations, you can
still sort them properly now regardless.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread Apollinaris Schoell
what is wrong with 2 relations?
I didn't say 2 are needed but why do you think 2 is bad?

On Mon, Feb 8, 2010 at 5:38 PM, John Smith deltafoxtrot...@gmail.comwrote:

 On 9 February 2010 11:21, Apollinaris Schoell ascho...@gmail.com wrote:
  besides editing convenience a relation is directed and sorted since API
 0.6
  You can see it as a route to follow from start to end. For bus routes
 this
  is a must. 2 relations may use the same road in different directions. on
 a
  highway ref one can argue this is not needed but it's still a good idea.

 So apply roles, I don't see why this needs to be 2 relations, you can
 still sort them properly now regardless.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 12:20, Apollinaris Schoell ascho...@gmail.com wrote:
 what is wrong with 2 relations?
 I didn't say 2 are needed but why do you think 2 is bad?

It creates redundant data, and makes it easier to get conflicting data
if both aren't updated consistently.

It also gives people the opportunity to merge them, possibly incorrectly.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread Apollinaris Schoell

On 8 Feb 2010, at 18:28 , John Smith wrote:

 On 9 February 2010 12:20, Apollinaris Schoell ascho...@gmail.com wrote:
 what is wrong with 2 relations?
 I didn't say 2 are needed but why do you think 2 is bad?
 
 It creates redundant data, and makes it easier to get conflicting data
 if both aren't updated consistently.
 
 It also gives people the opportunity to merge them, possibly incorrectly.

1) theory: tags on the super relation will always supersede tags lower in 
hierarchy. conflicting tags don't matter. 

2) practical editing: we are talking about a relation hierarch consisting of 
thousands of members. they have to be split for many reasons. editing speed, 
upload speed, query speed …
some have been created when Potlatch worked in live mode only and josm speed 
exponentially decrease with the size of a relation, uploads didn't finish 
because of network/server interrupts
as an example relation 94043 has 1512 members and 937 versions. this only one 
direction. other direction has 1525 members. It is not possible to get the 
history from the server Sorry, the data for the relation with the id 94043, 
took too long to retrieve.
any split of any road segment for a bridge, speed limit change … requires a new 
version and increases the number of members. 
do you still think a potential inconsistency has any relevance compared to this?


___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 13:47, Apollinaris Schoell ascho...@gmail.com wrote:
 1) theory: tags on the super relation will always supersede tags lower in 
 hierarchy. conflicting tags don't matter.

Actually this is disjointed, ways should override relations and
relations should override super relations.

 2) practical editing: we are talking about a relation hierarch consisting of 
 thousands of members. they have to be split for many reasons. editing speed, 
 upload speed, query speed …
 some have been created when Potlatch worked in live mode only and josm speed 
 exponentially decrease with the size of a relation, uploads didn't finish 
 because of network/server interrupts
 as an example relation 94043 has 1512 members and 937 versions. this only one 
 direction. other direction has 1525 members. It is not possible to get the 
 history from the server Sorry, the data for the relation with the id 94043, 
 took too long to retrieve.
 any split of any road segment for a bridge, speed limit change … requires a 
 new version and increases the number of members.
 do you still think a potential inconsistency has any relevance compared to 
 this?

Yes, all you are doing is coming up with work arounds to current
issues, the issues should be fixed properly.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
 Yes, all you are doing is coming up with work arounds to current
 issues, the issues should be fixed properly.

Apart from the obvious you aren't uploading/download every single
object referenced by the relation every time you edit it, and the
references to objects in the relation should still be reasonbly small
so I don't see what the fuss is all about.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 14:00, John Smith deltafoxtrot...@gmail.com wrote:
 Yes, all you are doing is coming up with work arounds to current
 issues, the issues should be fixed properly.

 Apart from the obvious you aren't uploading/download every single
 object referenced by the relation every time you edit it, and the
 references to objects in the relation should still be reasonbly small
 so I don't see what the fuss is all about.


Sorry, the fuss is about too many changes, not the relation itself,
this is an issue in and off itself, but isn't the same thing as
bundling 3000+ objects into a relation.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread Apollinaris Schoell

On 8 Feb 2010, at 20:03 , John Smith wrote:

 On 9 February 2010 14:00, John Smith deltafoxtrot...@gmail.com wrote:
 Yes, all you are doing is coming up with work arounds to current
 issues, the issues should be fixed properly.
 
 Apart from the obvious you aren't uploading/download every single
 object referenced by the relation every time you edit it, and the
 references to objects in the relation should still be reasonbly small
 so I don't see what the fuss is all about.
 
 
 Sorry, the fuss is about too many changes, not the relation itself,
 this is an issue in and off itself, but isn't the same thing as
 bundling 3000+ objects into a relation.

see the difference is I have done such edits and many others have done it. We 
know what we are talking about.
do it and you will never write something ignorant and stupid as this.
___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 14:14, Apollinaris Schoell ascho...@gmail.com wrote:
 see the difference is I have done such edits and many others have done it. We 
 know what we are talking about.
 do it and you will never write something ignorant and stupid as this.

As I said, the problem seems to be too many changes, not too many objects.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread John Smith
On 9 February 2010 14:14, Apollinaris Schoell ascho...@gmail.com wrote:
 see the difference is I have done such edits and many others have done it. We 
 know what we are talking about.

Then why didn't you report a bug so less information is attempted to
be returned? You still have the problem, breaking it up into 2
relations didn't fix it, and as time passes even more changes will
occur, the number of objects isn't the main problem.

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] Fwd: [Talk-us] [Warning: Potential Flamewar] Clarifying InterstateRelations

2010-02-08 Thread Liz
On Tue, 9 Feb 2010, Apollinaris Schoell wrote:
 see the difference is I have done such edits and many others have done it.
  We know what we are talking about. do it and you will never write
  something ignorant and stupid as this.
 
flamewar commences

and this comment is extremely unhelpful
so you suggest that someone like myself makes up some massive relations just 
to see what happens??

___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk