[Data-modeling] "area" property of "/location/location" type

[Jeff Prucher]

> -----Original Message-----
> From: data-modeling-bounces at freebase.com 
> [mailto:data-modeling-bounces at freebase.com] On Behalf Of 
> Kirrily Robert
> Sent: Wednesday, April 02, 2008 10:04 AM
> To: Freebase data modeling mailing list
> Subject: Re: [Data-modeling] "area" property of 
> "/location/location" type
> 
> 
> ----- "Jonathan W. Lowe" <jlowe at giswebsite.com> wrote:
> > The "/location/location" type has an "area" property that accepts 
> > multiple values.  Should this property instead be restricted to one 
> > value?
> > 
> > Unless someone can identify a location having more than one valid 
> > area, I recommend a schema change that restricts 
> > /location/location/area to one value.
> 
> Time series!  Uhhh... forget I said that.  Please.  PLEASE?

Well, that and the fact that different sources can have different, equally
valid, area measurements for the same location at the same time, depending
on methodology. But neither of those reasons is why the current property is
non-unique; the real reason is that I forgot to check the box. Me, I'm
tempted to just make it unique until we actually have some time-series data
to input. Right now, it's practically all WP infobox loads, which implies
reasonably current area.  (There are 24 locations with multiple values, all
of which appear to be differences in rounding, conversion, or using the
different measurement units, which will have to be cleaned up before we can
make the property unique.)

Jeff P