[Openstreetmap-dev] metadata, getAllKeys not found

[Jo Walsh]

On Sun, Jun 05, 2005 at 10:04:22AM +0100, Ben Gimpert wrote:
> Looks like your (Python?) client-side should be passing a boolean as 
> the second argument to getAllMaps(). That method's proper getAllKeys() 
> signature takes a String first (token) and then a boolean (visible?), 
> not an integer (1) passing as a boolean. 

ah thanks, that's better! doh; i'm still relatively new to python.
i see a handful of keys that look like this:

11
accessibleToHorse
nick at hogweed.org
1112537736104
12
accessibleToBike
nick at hogweed.org
1112537759038
14
name
steve at fractalus.com
1116083093933

- are there key names which you would like to propagate... certainly
  it would be easier when combining different peoples' streets to be
  relatively sure about the existence of certain properties... of 
  which 'name' is the one super-obvious candidate.

i would use a getKeyByName() type method if there was one.

Steve, you've talked of not wanting to impose one vocabulary or
schema, i see the decency in that, still i look for ways to establish
a mapping between different peoples' vocabularies that other people
can use.

perhaps there are some very common properties - particularly 'name' -
that could be auto-instantiated with a null value when an object of
the appropriate type is created, so that it comes out by default,
waiting to be set, when someone looks for an object's metadata.

names - on street segments or streets, do you have a strong feeling
about this? when i was playing with the bristol data i went for a very
simple TIGER-like model in which segment was named separately and the
only way they related was by physical contiguity, there was no
'street' meta-collection, just a lot of intersecting segments sharing
a name. 

the case where a street is physically the same 'street' but changes
names, sometimes changing back, along its length - eg Shoreditch High
Street / Kingsland Road / Stoke Newington Road / Stoke Newington High
Street - that's always bothered me a little. (the dumb driving
directions scenario; "continue along Kingsland Road for 200M; continue
along... etc"). you almost want a StreetCollection. i back away.

i wonder why there's no getStreets() method, just because you have to
dig around for the geometry afterwards, you might as well start from
the nodes?


-jo