[OSM-dev] Data source for robot
peterb at gatech.edu
Tue Oct 12 15:35:21 BST 2010
Ian Dees <ian.dees at gmail.com> writes:
> On Tue, Oct 12, 2010 at 8:49 AM, Peter Budny <peterb at gatech.edu> wrote:
> Frederik Ramm <frederik at remote.org> writes:
> > But if, as I suspect, your plan was merely to collect everything
> > tagged ref=<something> and then stuff that into a route relation
> > called <something>, that's not an added value in my book.
> In most cases, these ref=* tags don't exist yet. If we suppose that
> it's decided to forget the relations and rely on ref=* tags for
> identifying roads as part of a network, I could just as easily shift the
> focus to creating the ref=* tags instead.
> How do you plan on determining what ref tags should be applied to a OSM way and/or relation? Are you assuming that
> some key exists in the OSM data that will allow you to reference into the TIGER data? Are you doing spatial
> conflation to match TIGER data with OSM data?
See my other replies in this thread. There's enough metadata in the
TIGER imports that a lot of it can be reasonably automated.
Peter Budny \
Georgia Tech \
CS PhD student \
More information about the dev