[OSM-talk] fuel type suggestions

Jon Burgess jburgess777 at googlemail.com
Sun Aug 19 12:25:52 BST 2007


On Sun, 2007-08-19 at 20:05 +0900, Jeffrey Martin wrote:
> On 8/19/07, Jon Burgess <jburgess777 at googlemail.com> wrote:
> > On Sun, 2007-08-19 at 10:51 +0100, Tom Chance wrote:
> > > On Sunday 19 August 2007 07:13:38 Jeffrey Martin wrote:
> > > > In Korea most LPG fueling stations are separate from the other
> > > > stations that sell gasoline and diesel.
> > > > I'm not really sure how to tag that.
> > > > fueltype=
> > > > If I bothered to look there may be some stations that don't allow large
> > > > trucks.
> > > >
> > > > The only thing I found on the wiki was a set of tags used in Iran.
> > > >
> > > >  amenity=car_wash for car washes.
> > > >  amenity=fuel
> > > >  fuel_diesel=0 or 1
> > > >  fuel_cng=0 or 1
> > > >  fuel_petrol=0 or 1
> > > >  fuel_super_petrol=0 or 1
> > >
> > > Should it not be fueltype=diesel;lpg;petrol? Or just lots of
> > > fueltype=diesel;fueltype=lpg etc.
> > >
> > > There are lots of instances where we need multiple values for tags, it would
> > > make sense to standardise on a method like separation with semicolons or
> > > multiple entries and encourage all apps to support that.
> > >
> > > Better than new keys for every fuel type!
> >
> > Unfortunately there are problems with both suggestions right now:
> >
> > - Several things assumes that there is on a single instance of a given
> > 'key' on an object. (I know both JOSM & Mapnik renderer assume unique
> > keys)
> >
> > - ';' is used as the separator in the main OSM database between multiple
> > key/value pairs so inserting a ; in a value causes things to get
> > confused.
> >
> > The only thing I can suggest at the moment is to use ',' to separate
> > multiple values.
> >
> >         Jon
> >
> >
> >
> > _______________________________________________
> > talk mailing list
> > talk at openstreetmap.org
> > http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
> >
> 
> The Australians are using the semicolon for the ref tag.
> Is this a problem?
> 

Yes, semicolons in values are a problem. For reference, the issue with
was brought up a couple of weeks ago in
http://lists.openstreetmap.org/pipermail/talk/2007-August/016635.html

The relevant bit is below...

> The problem is that what you're looking for isn't really a tag at 
> all - it's part of a value. Looking at one of those nodes in the
> database shows us that the tags field is:
> 
>   source=PGS(could be inacurately;moved according to town brige in Mandal and Åvik(/Åvig) harbor);created_by=almien_coastlines
> 
> now that should be two key value pairs:
> 
>   source=PGS(could be inacurately;moved according to town brige in Mandal and Åvik(/Åvig) harbor)
>   created_by=almien_coastlines
> 
> but because we use semicolon as the separator the semicolon in the
> middle of the first key's value is also being treated as a separator
> and causing an additional key with no value to appear in the output
> of the API and planet etc...
> 
> Tom
> 

	Jon






More information about the talk mailing list