Re: GeoSites update


I like the approach of using webservices for this kind of thing,
basically because it means we can display stuff in the dashboard rather
than just display links. This is more in keeping with the idea of
dashboard as something that you can just glance at, rather than
something that demands a lot of attention.

To this end, I'm currently working integrating a weather service into
the GeoSites backend. You make a good point about redistribution though.
I guess you would have to contact e.g. MapQuest and ask.


> I'd be willing to write a mapquest / other map service backend that
> displays location/trip data when this starts working. Does anyone know
> about the legality of such a tool (or a site with a good SOAP/WSDL
> interface to map data)? From first glance, mapquest seems to have a
> clause in their license (one of many) limiting modification and
> redistribution of material from the site, but I'm not definite about
> what dashboard would classify as (my guess would be personal use).
> If someone knows anything about this, I'd love to hear back
> -- Matt Jones
> On Mon, 2004-03-01 at 19:10 +0000, dave wrote:
> > Hi all,
> > 
> > I've rejiggled the geosites updates as per Edd's suggestions. No new
> > functionality; the main change is the introduction of a Locale class
> > (and subclasses) which represent a place, and contain at least a
> > city,region,country. This is used by e.g. the GeoSites backend.
> > 
> > I've incorporated Clement's fix for US two-letter state codes (but I've
> > moved it into the Locale class, since it might be generally useful to
> > code that is interested in Locales).
> > 
> > Finally, the GeoSites backend now chains placenames (as keywords). I
> > think we ought to introduce a "place" cluetype for this kind of thing;
> > nothing else is exactly appropriate.
> > 
> > Feedback appreciated. My next plan is to do some work on the renderer
> > (currently there doesn't seem to be one). Edd, do you have any
> > suggestions (or code - I believe you had this going at one stage) for
> > this one? Ideas welcome.
> > 
> > dave

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]