[OSM-dev] Restrict key names on order to retain reusability of OSM

Artem Pavlenko artem.mapnik at googlemail.com
Fri Feb 15 11:41:02 GMT 2008


Stefan,

What exactly is the problem you're trying to solve ? It seems to me  
you're on a mission:)

Here is what you should do:
A. If you have the skills, get the data and convert it into whatever  
format/schema is good for you.
B. If you haven't got the skills, _fund_ someone to help you to  
convert the data into whatever format is good for you.
C. If none of the above, go and acquire either A or B

Cheers
Artem


On 15 Feb 2008, at 11:28, Stefan Keller wrote:

> > It is no harder for me to add construcción(spanish) to the  
> renderer than
>
> So, you're after a running target? Not so in my example schema of  
> exported OSM data.
> And finally all this just because being reluctant to restrict key  
> names to ASCII without space or so?
> - S.
>
> 2008/2/15, Rob Reid <rob at robreid.co.nz>:
> Stefan Keller wrote the following on 15/02/2008 21:32:
> > That's right, but keep in mind, that I *don't* propose to change the
> > current internal OSM schema and I *won't* restrict the number of key
> > on your side. I propose only to restict the character set of keys.
> >
> > So let's say for my application I'm happy with one attribute
> > (type="shop") or two. You know that in a more application oriented
> > environment you do stick to a schema with a distinct number of
> > attributes and take care of each of them.
> >
> > Rob wrote:
> > > You use building=shop in your examples but there is absolutely  
> nothing
> > > to stop someone using (apologies in advance for my lack of  
> language
> > > skills) construcción=almacén or ??????=?????.
> >
> > Good example: How to make a map of more than one country when you an
> > me can't interpret "construcción" and "??????" being buildings?
> >
> If someone wants to start using construcción as a key and wants to  
> to be
> rendered in the standard maps then the process is no different to from
> any other new key, they have to add it to the rendering rules for the
> various renderers or ask for it to be added and specify how it should
> appear.
> Just because I don't speak spanish does not mean I'm unable to add
> 'construcción' as a rule to one of the renderers and the renderers  
> don't
> care what language it is.
> It is no harder for me to add construcción(spanish) to the renderer  
> than
> it would be to add construktion(german), our current system would  
> allow
> both, your proposal would allow one and not the other.
>
> Cheers
>
> rcr
>
>
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20080215/86db29db/attachment.html>


More information about the dev mailing list