From: YoYo Siska <yoyo@gl.ksp.sk>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] GPS board
Date: Sun, 15 Apr 2012 13:15:29 +0200 [thread overview]
Message-ID: <20120415111528.GA5570@ksp.sk> (raw)
In-Reply-To: <4F89C86A.70602@tampabay.rr.com>
On Sat, Apr 14, 2012 at 02:56:42PM -0400, wireless wrote:
> On 04/14/12 14:38, Peter Stuge wrote:
> > wireless wrote:
> >> I have not formally researched open source mapping efforts, so
> >> any feedback on that issue is keenly welcome.
> >
> > Start with http://openstreetmap.org/
> > //Peter
>
> EXCELLENT!
>
> OK so to help create maps, I'm think of designing (cobbling together
> initially) a gps, and a (water) depth reading output, so in a boat, I
> can begin mapping the near shore environment.
>
> How does open street map data get created and are there existing
> open source embedded boards one can buy, install in a car and help
> extend/enhance the data collected? Or, roll your own?
Most people around openstreetmap are software / geography people, so
they mostly use what's readilly awailable (GPS loggers, JavaME phones
some time ago, smartphones now). I've seen hardware projects on the
level "how to make a bike holder for XYZ" or "how to get a PDA and
logger work together and with a large battery". There's a hardware page
on the wiki [1] (if you haven't found it already), but it seem pretty
outdated. As osm is opensource centered, there are/were people playing
with open hardware / technologies stuff (openmoko phones, beagle/panda
board with a gps receiver etc...)
There's also a foss-gps mailing list [2], though IIRC there are mostly
software guys who talk about how to work with lower level GPS data.
> It seem they already have the land methodologies developed, what
> about near-shore marine? Any open source software efforts for that
> yet?
There are basically two distinct activities in OSM: the collection of
GPS logs/tracks and then the creation of the map/database itself based
either on those logs or any other freely available sources. For land
based information the elevation doesn't really get entered into the
database, mostly because it would be realy sparse and there is SRTM data
that's much better. I remeber some talk about an initiative to somehow
process the elevation data from the logs, but I'm not sure where it
ended.
Anyway I guess it would be different for marine data, which might be
more usefull... I guess you have to get in contact with people from
openstreet map interested in that. The OpenSeaMap page on osm wiki [3]
mentions even some mailing lists...
yoyo
[1] http://wiki.openstreetmap.org/wiki/Hardware
[2] http://lists.osgeo.org/mailman/listinfo/foss-gps
[3] http://wiki.openstreetmap.org/wiki/OpenSeaMap
next prev parent reply other threads:[~2012-04-15 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 18:34 [gentoo-embedded] GPS board wireless
2012-04-14 18:38 ` Peter Stuge
2012-04-14 18:56 ` wireless
2012-04-14 21:21 ` Mike Frysinger
2012-04-15 11:15 ` YoYo Siska [this message]
2012-04-16 12:42 ` Ed W
2012-04-16 14:57 ` wireless
2012-04-16 15:27 ` Peter Stuge
2012-04-17 9:15 ` Ed W
2012-04-17 13:17 ` wireless
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120415111528.GA5570@ksp.sk \
--to=yoyo@gl.ksp.sk \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox