On 11/30/05, boblq <[EMAIL PROTECTED]> wrote:
> On Wednesday 30 November 2005 06:46 am, Tracy R Reed wrote:
> > Wade Curry wrote:
> > > similar effect for an open map database. How would you keep it
> > > open and still mitigate against errors, innocent or malicious?
> >
> > Wikipedia info can be very subjective and difficult to verify. I suspect
> > that an open map database would be far simpler. If someone places the
> > lat/long for the Eiffel Tower in San Diego, something's up. More subtle
> > position errors are more difficult to detect but because people would
> > actually be using this info for navigation and incorrect data would be a
> > real problem you can bet people would notice unlike some questionable
> > info which gets included in someones school report which the teacher
> > probably would not notice as incorrect either.
> >
> > --
> > Tracy R Reed
> > http://copilotconsulting.com
> > 1-877-MY-COPILOT
>
> I see two different problems:
> 1) Getting raw map data
> 2) Annotating the maps.
>
> I don't see a lot of reason in the long term (wireless
> Internet everywhere) to do 1). Use either Google or
> Yahoo to provide the maps. Then use their APIs to
> annotate the maps.
>
> Here are the APIs:
> http://www.google.com/apis/maps/
> http://developer.yahoo.net/maps/index.html
>
There's a lot of "everywhere" to cover, even if you restrict yourself
to dry land.
Much of it does not have cellphone coverage, let alone wireless internet.
But GPS is genuinely worldwide.
Of course, you can build the maps you need _before_ you set off into
the wilderness. Then go there and see if the map agrees with the
terrain.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
