Opened 13 years ago

Closed 13 years ago

#83 closed task (fixed)

API support for ways (collections of segments)

Reported by: Immanuel Scholz Owned by: steve@…
Priority: major Milestone: OSM 1.0
Component: api Version:
Keywords: xml api streets segments Cc:


Add tracks to the API as described in the XML Schema in wiki.

Change History (4)

comment:1 Changed 13 years ago by Tom

Keywords: xml api streets segments added
Milestone: OSM 1.0
Summary: API support for tracksAPI support for tracks (collections of segments)

I don't think they should be called Tracks as described on the wiki:

Better that they be called Streets or Ways or something which doesn't confuse them with GPS/GPX tracks/traces/trk elements.

Some thought should be put into whether segments automatically inherit properties of the streets they are in, whether a segment can be in more than one street, etc.

My vote would be that streets don't have tags, but that clients offer to apply tags to all elements contained in a particular street. Street properties can be inferred from the properties of their tags.

Similar notes added here:

comment:2 Changed 13 years ago by Immanuel Scholz

Let's call them ways. Since people start creating slopes, the name "street" does not really fit! "track" is reserved for GPS tracks, I agree.

But please, let ways have properties! This is an important distingtion to have several different ways over the same segments. As example a way that define a bus route can have completly different properties than several of the ways that define the streets of this bus route, which in turn have different attributes from the a-road spanning the whole stuff.

It would be a really mess, if you try to fiddle that into segment's properties only!

comment:3 Changed 13 years ago by Immanuel Scholz

Summary: API support for tracks (collections of segments)API support for ways (collections of segments)

comment:4 Changed 13 years ago by Immanuel Scholz

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.