- From: Michael(tm) Smith <mike@w3.org>
- Date: Fri, 14 Nov 2008 10:22:47 +0900
- To: Greg Bolsinga <bolsinga@apple.com>
- Cc: public-geolocation <public-geolocation@w3.org>
Greg Bolsinga <bolsinga@apple.com>, 2008-11-13 16:41 -0800: > If the civic address were a part of the spec, the web developer will not > have to create their own lat/long to civic address lookup. Also, there could > be less network traffic and latency waiting for results. A web developer > coding to the spec will have less to implement as well. > > What are the use cases for lat/long only? If I'm understanding what you're asking, as far as use cases that are listed in the Use Cases section[1] of the current draft, I'd think the "Turn-by-turn route navigation" use case is one big one for lat/lon only. [1] http://dev.w3.org/geo/api/#usecases_section I would think that in general, lat/lon-only data is useful in particular for "non-city" use cases where there is no possibility at all of getting any kind of relevant civic address. For example, here in Japan, I use a location-aware app that provides annotated maps of mountain-hiking/biking routes, showing maps along with real-time turn-by-turn directions and points of interest (e.g., scenic vistas marked). So the "Find points of interest in the user's area" would also be a relevant use case for lat/lon-only in the "non-city" context. All that said assuming I'm understanding what you're asking by "What are the use cases for lat/long only?" Apologies in advance if I misunderstood the context in which you're asking. --Mike -- Michael(tm) Smith http://people.w3.org/mike/
Received on Friday, 14 November 2008 01:23:22 UTC