2011/3/4 Alan Mintz :
> Is this data really worth importing?
I agree with all of your points. After checking my local area I
decided not to import this data, because some was apparently wrong,
the rest seemed not very detailed and might have been wrong at least
inaccurate. As the quantity was mini
On 3/3/2011 11:16 PM, Alan Mintz wrote:
Is this data really worth importing?
With the required amount of review, I wouldn't classify them as a
data import so much as a requested work list. These addresses are
important to the owners in some way: historically GPS's have gone to the
wrong
The source tag is included in the two Python scripts included in this
thread.
All I know, is that it is very time consuming to add this data. Looking up
what the address may refer to. Checking whether it's next to the street it
was intended, etc.
And, of course, if there are no other house number
At 2011-03-03 11:23, Jo wrote:
I used mapquest_critical_addresses for the source tag.
Why not add that to the Python conversion script so we at least have some
consistency there?
Is this data really worth importing?
I have to say that, from the comments so far, quality seems quite low, and
I used mapquest_critical_addresses for the source tag.
Jo
2011/3/3 Toby Murray
> Is there any particular source or maybe source:addr tag being used
> when mapping things based on this data?
>
> Out of the two nodes in my city, one was spot on - maybe 5 feet from
> the front door of the fraterni
Is there any particular source or maybe source:addr tag being used
when mapping things based on this data?
Out of the two nodes in my city, one was spot on - maybe 5 feet from
the front door of the fraternity house that it belongs to. And it
hasn't been mapped yet so I guess I should get on that.
One thing that I noticed about the data is that there are several
Canadian addresses in the US file.
There is at least one typo in the California data: Squaw peak rd
ended up at -12 degrees instead of -120.
___
talk mailing list
talk@openstreetm
Here's my modifications to the code... The original code will fail on
lines like this:
critical_address_file_us.csv:"3424 Peachtree Rd,
NE",US,GA,Atlanta,30326,3424,3424,33851200,-84363500
critical_address_file_us.csv:"3424 Peachtree Road,
NE",US,GA,Atlanta,30326,3424,3424,33851200,-84363500
Bec
I look up what it is the address for, sometimes we already have a
node/building, so it can be merged. Sometimes it's a garage/gas pump so not
too hard to guess. Usually it's a car rental and I simply hope for the best
and count on the next guy/gal to put it where it really belongs...
It's certainl
2011/3/3 Jo :
> When importing these, I tend to drag them onto the nearest building...
On which one? Usually the streets have 2 sides...
cheers,
Martin
___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
To put it in context in Ottawa, a city of roughly one million people, we
currently have 120,000 "addr:housenumber" or addresses, this would give us
an additional three.
I'd much prefer them to add in the footpaths that are in the OSM map of
Ottawa so their walking and public transport routing work
On 3/3/2011 6:39 AM, M∡rtin Koppenhoefer wrote:
Yes, in the 7 addresses I checked for Rome there was also one
seriously wrong (several km away on a completely different road). I do
not recommend to import these addresses automatically without
verifying them manually one by one.
Of the 6 I loo
When importing these, I tend to drag them onto the nearest building...
2011/3/3 M∡rtin Koppenhoefer
> I have checked the 7 or so non-duplicate Addresses for Rome and found
> that only 1 was not on the road itself. Is is possible that these
> lat/lon have been obtained with some other geocoding s
2011/3/3 davespod :
> I just checked three UK addresses for towns I've worked in (ok, not a
> scientific sample). One was correct, one was ambigious and one was seriously
> wrong.
> The seriously wrong one worried me slightly:
Yes, in the 7 addresses I checked for Rome there was also one
seriousl
I have checked the 7 or so non-duplicate Addresses for Rome and found
that only 1 was not on the road itself. Is is possible that these
lat/lon have been obtained with some other geocoding service? Usually
I would expect people to mark their house, not the extrapolation of
their house to the street
Pieren wrote:
> And after a quick check on the FR addresses, I've seen that about 10% of
> the
> post codes are wrong.
Yes, I think this may be a very useful additional resource, and I commend
Mapquest for releasing it, but please don't anyone think about a global bulk
upload.
I just checked
I adapted the Python code a bit, so several .osm files are created, one for
each country:
A source tag is also added. I also added some invalid data, so it shouldn't
be possible to upload these files to the server directly. As they are now,
it is possible to cherry pick addresses on one OSM layer
On Thu, Mar 3, 2011 at 1:13 AM, Anthony wrote:
>
> The Europe file has 707 addresses.
>
>
And after a quick check on the FR addresses, I've seen that about 10% of the
post codes are wrong.
Pieren
___
talk mailing list
talk@openstreetmap.org
http://list
*Hello David,
*I'm sorry if you misunderstood where these addresses came from.
These are addresses where people have directly picked up the phone and called
us with their address and latlng because they weren't being found in the
commercial datasets we license.
Our Support team gathers these a
On Wed, Mar 2, 2011 at 7:00 PM, David Murn wrote:
> On Wed, 2011-03-02 at 13:54 -0700, flambe...@gmail.com wrote:
>
>> There are currently three (3) main files - one for the United States,
>> one for Canada and one for Europe.
>
> This is great, but the US is 300m, Canada 34m and Europe 700m. The
On Wed, 2011-03-02 at 13:54 -0700, flambe...@gmail.com wrote:
> There are currently three (3) main files - one for the United States,
> one for Canada and one for Europe.
This is great, but the US is 300m, Canada 34m and Europe 700m. The
world population is just under 6.8 million. Is there any
Umm yeah quick note on that – the dupes are different spellings of an
address when it has a directional as part of the road name. lets call it a
feature of how the CAF is checked before our hitting our commercial
geocoding solution.
Mike N wrote:
A quick check shows that there are some dup
On Miércoles, 2 de Marzo de 2011 21:54:28 flambe...@gmail.com escribió:
> 4. we've checked with our lawyers, and yes, you can have them -
> UNENCUMBERED!
Hey, you will at least want to keep track of how many of them are
imported/uploaded into OSM. Have you thought about a source= tag, perhaps
so
On 2 March 2011 21:54, flambe...@gmail.com wrote:
> MapQuest is providing several address files that contain user-provided
> latitude and longitude locations across the world. Our users provided
> these exact locations to us so that they could be mapped correctly on
> our MapQuest maps.
>
> There
On 3/2/2011 3:54 PM, flambe...@gmail.com wrote:
MapQuest is providing several address files that contain user-provided
latitude and longitude locations across the world. Our users provided
these exact locations to us so that they could be mapped correctly on
our MapQuest maps.
This is great
MapQuest is providing several address files that contain user-provided
latitude and longitude locations across the world. Our users provided
these exact locations to us so that they could be mapped correctly on
our MapQuest maps.
There are currently three (3) main files - one for the United States
26 matches
Mail list logo
