[Openstreetmap-dev] key/value system question and broken osmServerHandler.getFeatureValues
steve at asklater.com
Sat Sep 17 11:04:03 BST 2005
The docmentation is old :-(
The current system is over-engineered and XML-RPC is deprecated. I
almost have the applet talking to the REST interface.
I have to pop out now, but I'll document the key/val stuff and email a
link to it this weekend.
* @ 17/09/05 12:29:57 AM immanuel.scholz at gmx.de wrote:
> Can someone please acknowledge my understanding of the key/value system?
> If I understand
> http://www.openstreetmap.org/wiki/index.php/Key_Value_System correctly
> (I never heard of "del.icio.us/flickr" before ;), then:
> - Keys exist independend from any other stuff in osm. There is a list of
> all keys in the server, regardless of whether they are used or not.
> - A key can be assigned to any object. "Object" means all
> - node
> - point of interest (crippled node)
> - segment (line)
> - street (several lines)
> - area (several nodes)
> - other keys (e.g. displayLogo assigned to motorway)
> - when a key is assigned, a "value" describes the key<->object
> connection. So the trippel (key, value, object) is stored.
> - keys and value both are strings. Interpretation of these strings are
> application dependend (something like "please use sane values")
> While I am on it: What's broken with
> osmServerHandler.getFeatureValues(int nFeatureType,
> java.lang.String sAreaUID,
> java.lang.String sToken)
> The first parameter is an object type descriptor, missing some types
> (only area, poi, street and segment seems to be supported. How to ask
> for "node" and "key" values?). The second parameter is an uid, but the
> wrong type: String instead of the usual int. And the last is the token,
> which used to be the first parameter in all other functions...
> Ciao, Imi.
> Openstreetmap-dev mailing list
> Openstreetmap-dev at vr.ucl.ac.uk
SteveC steve at asklater.com http://www.asklater.com/steve/
More information about the dev