On Fri, 2009-11-20 at 06:07 +, talk-us-requ...@openstreetmap.org
wrote:
Heh, I didn't even know we had Oregon data available.
We didn't at the time. I checked. Metro had (still has) restrictive
licensing, and the state did not have any clearing house at the time.
- Alan
I hate to step into this flamefest, but:
Having traveled around the US, I've been really glad the tiger data is
there. Often it seems like there have not been a lot of edits, and
it's way better than nothing.
I heard about OSM long ago, and I think noticed the map was blank in
mass,
On Thu, 2009-11-19 at 13:29 -0800, Paul Johnson wrote:
Used state data instead, if I were to do a mass import. Oregon GEO
knows what they're doing, the US Census (along with the rest of the
federal government) barely acknowledges we exist. Which would you
rather trust?
1) Known good data
Christopher Covington wrote:
On Sun, 2009-11-15 at 10:59 -0800, Paul Johnson wrote:
Dave Hansen wrote:
2) The TIGER import violates one of the most basic principals of OSM:
Abbreviations: DO NOT DO IT.
I really don't understand this. If the United States Postal Service and
the Census
On Mon, 2009-11-16 at 16:24 -0500, Matthias Julius wrote:
IMHO it is unfortunate this was not
done during the TIGER import. It would have been easy enough.
Sure. But, there were 50 other things that were easy enough to do.
Joining county borders, eliminating motorway overpass intersections,
On Sun, 2009-11-15 at 10:59 -0800, Paul Johnson wrote:
Dave Hansen wrote:
2) The TIGER import violates one of the most basic principals of OSM:
Abbreviations: DO NOT DO IT.
I really don't understand this. If the United States Postal Service and
the Census Bureau have been abbreviating names
David Lynch djly...@gmail.com writes:
Agreed. I can understand not wanting to abbreviate words that don't
have a standard abbreviation, but the USPS is the de-facto arbiter of
how addresses (and therefore street names) are written in the United
States, and they have a well-defined list of
Dave Hansen wrote:
If we can come up with a scheme for getting the addressing imported in a
sane fashion and the consensus is that people want it done that way,
it'll get imported. There are still quite a few squeaky wheels that
like to grumble about TIGER, but I haven't heard a single
Paul Johnson wrote:
Dave Hansen wrote:
If we can come up with a scheme for getting the addressing imported in a
sane fashion and the consensus is that people want it done that way,
it'll get imported. There are still quite a few squeaky wheels that
like to grumble about TIGER, but I haven't
On Sun, 2009-11-15 at 10:59 -0800, Paul Johnson wrote:
Dave Hansen wrote:
If we can come up with a scheme for getting the addressing imported in a
sane fashion and the consensus is that people want it done that way,
it'll get imported. There are still quite a few squeaky wheels that
like
On Sun, 2009-11-15 at 14:25 -0800, Sam Vekemans wrote:
1 - A few people (we can call the data conversion team) are in charge
of taking the data in it's source form (in this case SHP) We use the
tools availble (shp-to-osm.jar and/or shp2osm.py) and are the ones who
create a set of 'rules'
On Sun, 2009-11-15 at 14:33 -0800, Dave Hansen wrote:
Yeah, and that does sound like a really nice way to do it, especially
when there is existing data.
Anybody want to be on the USA conversion team? :)
-- Dave
___
Talk-us mailing list
12 matches
Mail list logo
