[OSM-dev] Data source for robot
ian.dees at gmail.com
Tue Oct 12 15:39:51 BST 2010
On Tue, Oct 12, 2010 at 9:35 AM, Peter Budny <peterb at gatech.edu> wrote:
> 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
> > 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.
Have you checked some representative samples? In the areas I've edited a lot
of the way splitting and parallel way creating has removed or invalidated
the TIGER metadata. Regardless, how do you plan on handling the situation
where a human has to fill in the blanks?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev