I don't agree that there is no value in address range interpolation like TIGER
uses. As anyone who has edited TIGER data knows, it is not very accurate. So
cleaning that up (address aspects as well as geometry and attributes) is a
valuable thing that we can do in OSM. Getting a viable geocoding
This is a LOT of data to manually add. Is there a simpler way?
Yes, address information is laborious to collect and enter. There is a
JOSM plugin to simplify the repetitive data entry aspect as much as
possible, but it still takes quite a bit of effort.
: [Talk-us] Address Lookup
To: Apollinaris Schoell ascho...@gmail.com
Cc: val...@gmail.com val...@gmail.com, OSM Talk US
talk-us@openstreetmap.org
Message-ID: 04041b59-cecc-4b4f-90ea-1c9ba680d...@gmail.com
Content-Type: text/plain; charset=us-ascii
I don't agree
On Fri, May 21, 2010 at 12:45 AM, Val Kartchner val...@gmail.com wrote:
From what I understand, next to each place where another street
intersects this street I will have to create another node (on each side
of the street) tagged with addr:street and addr:housenumber. I will
need to connect
On Wed, 2010-05-19 at 08:54 -0500, Lord-Castillo, Brett wrote:
If someone were to use OSM for dispatching, dispatching software generally
requires a destination address to be associated with a corresponding street
in order to dispatch to an address point (as opposed to dispatching to an
5 matches
Mail list logo
