Re: [Talk-us] Announcement: Address Improvement project

2011-10-06 Thread Metcalf, Calvin (DOT)
I was proposing to just make sure zipcodes are up to date before the extremly 
complex street naming idea with prefixes based on similarly named streets 
relitive locations 
Sent with Verizon Mobile Email


---Original Message---
From: Brad Neuhauser brad.neuhau...@gmail.com
Sent: 10/5/2011 11:57 pm
To: calvin.metc...@dot.state.ma.us
Cc: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Announcement: Address Improvement project

Calvin, getting back to your original comment, what exactly do you mean use 
ZIP codes?  They are currently tagged with the key addr:postcode.  Are you 
proposing an import or some other way to use the Census ZCTA data?  Brad

On Wed, Oct 5, 2011 at 9:32 PM, Metcalf, Calvin (DOT) 
calvin.metc...@state.ma.us wrote:
census is bad for places that DON'T have people but especialy when you build 
your data set off the block layer the shapes will include all the addresses 
they need to but will miss some strange ones (like theme parks)
Sent with Verizon Mobile Email


---Original Message---
From: Nathan Edgars II nerou...@gmail.com

Sent: 10/5/2011 9:37 pm
To: calvin.metc...@dot.state.ma.us
Cc: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Announcement: Address Improvement project


On 10/5/2011 9:15 PM, Metcalf, Calvin (DOT) wrote:
 In MA they are good in they are precise
How have you tested this?

  don't know about the rest of the country but say wht you will about
the census they tend to get the areas right in the sense of getting all
the houses.
In Florida, they omit 32830, which has been Walt Disney World's zip code
since it opened in 1971.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us




___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Nathan Mills

On Tue, 04 Oct 2011 22:39:24 -0700, Paul Norman wrote:

In this case the A was part of the house number and 112A had no 
connection

to 112.

What I see around here more often is suite numbers (e.g. 101, 102) 
that are
placed in front of the number when written out, but sometimes are 
placed
after on forms. Eg 
http://www.openstreetmap.org/browse/node/1052967131 where

I mapped it as addr:housenumber=#104-7885


I just use the building's address number in addr:housenumber and write 
something
like 112 West Center Street Suite 700 in addr:full if all the 
entrances are
to the same building and have the same street address but different 
suite numbers,

prefixes, or postfixes.

-Nathan



___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Peter Dobratz
For secondary house numbers, I use addr:flats as this appears to be at
least semi-documented on the wiki.  I also use addr:full in this case
to write the whole address so it's clear what's going on.  We have a
number of buildings around here that use Sutie/Apartment/Lot/Unit
numbers along with the regular house number to indicate their address.
 Some hypothetical examples:

A hypothetical mobile home:
20 Main Street Lot 5
Derry, NH 03038
addr:housenumber=20
addr:street=Main Street
addr:flats=5
addr:full=20 Main Street Lot 5;Derry, NH 03038
addr:postcode=03038

A hypothetical townhouse:
12 Main Street Unit 6
Derry, NH 03038
(on the way for the whole building)
addr:housenumber=12
addr:street=Main Street
addr:postcode=03038
(on the node for the entrance to a townhouse)
addr:housenumber=12
addr:street=Main Street
addr:flats=6
addr:full=12 Main Street Lot 6;Derry, NH 03038

Though I haven't actually tagged any apartment buildings yet, I would
use addr:flats=1-6 on the node for the entrance to a building with 6
apartments in it.  I would also use addr:full to write out the full
address.

Peter

On Wed, Oct 5, 2011 at 2:12 AM, Nathan Mills nat...@nwacg.net wrote:
 On Tue, 04 Oct 2011 22:39:24 -0700, Paul Norman wrote:

 In this case the A was part of the house number and 112A had no connection
 to 112.

 What I see around here more often is suite numbers (e.g. 101, 102) that
 are
 placed in front of the number when written out, but sometimes are placed
 after on forms. Eg http://www.openstreetmap.org/browse/node/1052967131
 where
 I mapped it as addr:housenumber=#104-7885

 I just use the building's address number in addr:housenumber and write
 something
 like 112 West Center Street Suite 700 in addr:full if all the entrances
 are
 to the same building and have the same street address but different suite
 numbers,
 prefixes, or postfixes.

 -Nathan



 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Carl Anderson
For range data there is uncertainty how to increment addresses when an
end is such as

N82W15855 VALLEY VIEW DR,, MENOMONEE FALLS, WI, 53051-3709, USA
45-558 KAMEHAMEHA HWY STE B3,, KANEOHE, HI, 96744-1944, USA
46-026 A ALALOA ST,, KANEOHE, 96744-3824, USA, HI

On Tue, Oct 4, 2011 at 9:39 PM, Mike N nice...@att.net wrote:
 On 10/4/2011 9:04 PM, Steven Johnson wrote:

 The purpose of this project is to improve the tagging and better reflect
 local addressing practice, particularly in areas where the Karlsruhe
 schema does not fit local practice. This includes Japan and United
 States, but likely other regions as well. We've made attempts to
 consolidate a number of addressing discussions and proposals from around
 the OSM wiki.

  I must confess that I haven't seen cases in the US that aren't already
 covered by Karlsruhe.   The only thing I can think of would be multi floors
 and building interiors - which aren't generally mapped in OSM anyway. If the
 problem is that something isn't documented clearly, that can be addressed.
 One thing I noticed is that the page links to the proposed Karlsruhe schema
 rather than the 'approved' page:

 https://wiki.openstreetmap.org/wiki/Key:addr

  I started to look at the US ... Address Data Standard and admit that I'd be
 blown away at trying to at trying to add any of it to typical OSM address
 data collection process.   I'd probably just end up entering everything with
 FIXME's and let someone else fix it.  g

 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us




-- 
Carl Anderson, GISP

cander...@spatialfocus.com
carl.ander...@vadose.org

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Alan Mintz

At 2011-10-04 18:38, Ian Dees wrote:

When I use addr:street I put the entire street's name in the field.

Breaking apart that street name into pieces is the job of other tags, I 
would imagine.


I proposed, and have widely used addr:street_direction_prefix for the 
cardinal direction of addr:housenumber along addr:street. I've also used 
addr:suite when needed.


Example 1: when there is one Main Street that runs predominantly N/S, 123 
North Main Street is tagged:


addr:housenumber=123
addr:street_direction_prefix=N
addr:street=Main Street


Example 2: When there are two separate Vermont Avenues that run 
predominantly N/S and parallel to each other, 123  West Vermont Avenue is 
tagged:

addr:housenumber=123
addr:street=West Vermont Avenue

In this particular case in Los Angeles, the Vermont Avenue right-of-way was 
split to put a rail system down the middle, creating a southbound West 
Vermont Avenue and a northbound East Vermont Avenue.


I'd like to see some kind of indicator to show that the second case is 
correct (i.e. the direction is really part of the street name) instead of 
just being an instance that hasn't been properly analyzed yet. I had 
proposed making the addr:street tag contain the full 
prefix+root+type+suffix and then using addr:street_* tags for the 
individual components, the presence of any of which would indicate that the 
name had been properly analyzed.


I understand the arguments that this can be complicated to 
explain/use/enforce. Not sure what to do about that. I don't think it's 
rocket science. There are days when I think we should expect more. Then 
again, on days when I can't read 3 professional 300-word news stories 
without finding 10 mistakes...


--
Alan Mintz alan_mintz+...@earthlink.net


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Mike N

On 10/5/2011 8:46 AM, Carl Anderson wrote:

For range data there is uncertainty how to increment addresses when an
end is such as

N82W15855 VALLEY VIEW DR,, MENOMONEE FALLS, WI, 53051-3709, USA
45-558 KAMEHAMEHA HWY STE B3,, KANEOHE, HI, 96744-1944, USA
46-026 A ALALOA ST,, KANEOHE, 96744-3824, USA, HI


 At some point, the work required to define a custom address range 
exceeds the work required to tag each address individually, particularly 
if it's only used once.  If there are one or two dozen custom address 
incrementing schemes in the US, does it make sense to define rule sets 
for each one?


  I haven't skimmed all of the referenced specifications, which may 
have a hint on incrementing rules that would work in all of the US.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Nathan Edgars II

On 10/5/2011 7:51 PM, Metcalf, Calvin (DOT) wrote:

ZIP codes, which in America are not copy righted [sic]

Are you sure about this?

 and (at least in MA) widely available.
Are these precise or TIGER's horrible approximations?

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Metcalf, Calvin (DOT)
In MA they are good in they are precise don't know about the rest of the 
country but say wht you will about the census they tend to get the areas right 
in the sense of getting all the houses.
(sorry about the spelling phone sucks)
Sent with Verizon Mobile Email


---Original Message---
From: Nathan Edgars II nerou...@gmail.com
Sent: 10/5/2011 8:53 pm
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Announcement: Address Improvement project

On 10/5/2011 7:51 PM, Metcalf, Calvin (DOT) wrote:
 ZIP codes, which in America are not copy righted [sic]
Are you sure about this?

  and (at least in MA) widely available.
Are these precise or TIGER's horrible approximations?

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Nathan Edgars II

On 10/5/2011 9:15 PM, Metcalf, Calvin (DOT) wrote:

In MA they are good in they are precise

How have you tested this?

 don't know about the rest of the country but say wht you will about 
the census they tend to get the areas right in the sense of getting all 
the houses.
In Florida, they omit 32830, which has been Walt Disney World's zip code 
since it opened in 1971.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Dale Puch
Are you sure it is omitted, and not just a tiny dataset ( say  30 ) since I
think there are only a few Disney executives residences there?

On Wed, Oct 5, 2011 at 9:35 PM, Nathan Edgars II nerou...@gmail.com wrote:

 On 10/5/2011 9:15 PM, Metcalf, Calvin (DOT) wrote:

 In MA they are good in they are precise

 How have you tested this?


  don't know about the rest of the country but say wht you will about the
 census they tend to get the areas right in the sense of getting all the
 houses.
 In Florida, they omit 32830, which has been Walt Disney World's zip code
 since it opened in 1971.


 __**_
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.**org/listinfo/talk-ushttp://lists.openstreetmap.org/listinfo/talk-us




-- 
Dale Puch
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Carl Anderson
Although there is only 1 edge on the TIGER 2010 edges dataset having
zipl = '32830' or zipr = '32830'  (TLID = 94368893)
there are 539 faces in the TIGER 2010 faces dataset having ZCTA5CE10 =
'32830' or ZCTA5CE00 = '32830'

You might consider using the ZCTA5CE00 and ZCTZ5CE10 face data in
conjunction with the edge data

ftp://ftp2.census.gov/geo/pvs/tiger2010st/12_Florida/12095/tl_2010_12095_edges.zip
ftp://ftp2.census.gov/geo/pvs/tiger2010st/12_Florida/12095/tl_2010_12095_faces.zip

The American Fact Finder reports industry statistics by ZIP code '32830'

http://factfinder.census.gov/servlet/IBQTable?_bm=y-geo_id=86000US32830-ds_name=EC0744Z5-_lang=en


C.


On Wed, Oct 5, 2011 at 9:35 PM, Nathan Edgars II nerou...@gmail.com wrote:
 On 10/5/2011 9:15 PM, Metcalf, Calvin (DOT) wrote:

 In MA they are good in they are precise

 How have you tested this?

 don't know about the rest of the country but say wht you will about the
 census they tend to get the areas right in the sense of getting all the
 houses.
 In Florida, they omit 32830, which has been Walt Disney World's zip code
 since it opened in 1971.

 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us




-- 
Carl Anderson, GISP

cander...@spatialfocus.com
carl.ander...@vadose.org

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Nathan Edgars II

On 10/5/2011 10:08 PM, Carl Anderson wrote:

Although there is only 1 edge on the TIGER 2010 edges dataset having
zipl = '32830' or zipr = '32830'  (TLID = 94368893)
there are 539 faces in the TIGER 2010 faces dataset having ZCTA5CE10 =
'32830' or ZCTA5CE00 = '32830'


Are these based on roads or areas? To be sure about which zip code a 
property near the line is in, you would need an area. (Yes, I know the 
method of assigning zip codes doesn't make areas easy to generate, but 
the same seems true for segments of roads.)



As for 32830 specifically, it may have been added since the 2002 files 
you linked here: 
http://lists.openstreetmap.org/pipermail/talk-us/2010-November/004800.html


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Carl Anderson
Census faces are areas.


On Wed, Oct 5, 2011 at 10:19 PM, Nathan Edgars II nerou...@gmail.com wrote:
 On 10/5/2011 10:08 PM, Carl Anderson wrote:

 Although there is only 1 edge on the TIGER 2010 edges dataset having
 zipl = '32830' or zipr = '32830'  (TLID = 94368893)
 there are 539 faces in the TIGER 2010 faces dataset having ZCTA5CE10 =
 '32830' or ZCTA5CE00 = '32830'

 Are these based on roads or areas? To be sure about which zip code a
 property near the line is in, you would need an area. (Yes, I know the
 method of assigning zip codes doesn't make areas easy to generate, but the
 same seems true for segments of roads.)


 As for 32830 specifically, it may have been added since the 2002 files you
 linked here:
 http://lists.openstreetmap.org/pipermail/talk-us/2010-November/004800.html




-- 
Carl Anderson, GISP

cander...@spatialfocus.com
carl.ander...@vadose.org

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-05 Thread Brad Neuhauser
Calvin, getting back to your original comment, what exactly do you mean use
ZIP codes?  They are currently tagged with the key addr:postcode.  Are you
proposing an import or some other way to use the Census ZCTA data?  Brad

On Wed, Oct 5, 2011 at 9:32 PM, Metcalf, Calvin (DOT) 
calvin.metc...@state.ma.us wrote:

 census is bad for places that DON'T have people but especialy when you
 build your data set off the block layer the shapes will include all the
 addresses they need to but will miss some strange ones (like theme parks)
 Sent with Verizon Mobile Email


 ---Original Message---
 From: Nathan Edgars II nerou...@gmail.com
 Sent: 10/5/2011 9:37 pm
 To: calvin.metc...@dot.state.ma.us
 Cc: talk-us@openstreetmap.org
 Subject: Re: [Talk-us] Announcement: Address Improvement project

 On 10/5/2011 9:15 PM, Metcalf, Calvin (DOT) wrote:
  In MA they are good in they are precise
 How have you tested this?

   don't know about the rest of the country but say wht you will about
 the census they tend to get the areas right in the sense of getting all
 the houses.
 In Florida, they omit 32830, which has been Walt Disney World's zip code
 since it opened in 1971.
 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


[Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Steven Johnson
Hi all,

I'd like to announce a broad-based project to improve addresses in OSM. The
project page is here:
https://wiki.openstreetmap.org/wiki/Address_Improvement

The purpose of this project is to improve the tagging and better reflect
local addressing practice, particularly in areas where the Karlsruhe schema
does not fit local practice. This includes Japan and United States, but
likely other regions as well. We've made attempts to consolidate a number of
addressing discussions and proposals from around the OSM wiki.

I'd like to invite anyone with an interest in addresses and addressing to
lend their talents to the project. Please add to the discussion.

-- SEJ
-- twitter: @geomantic
-- skype: sejohnson8

Common sense is the collection of prejudices acquired by age eighteen. --
Einstein
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Serge Wroclawski
On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson sejohns...@gmail.com wrote:
 Hi all,

 I'd like to announce a broad-based project to improve addresses in OSM. The
 project page is here:
 https://wiki.openstreetmap.org/wiki/Address_Improvement

Can you summarize the project?

All the Wiki page says right now is there's a problem.

What is your proposed solution?

- Serge

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Steven Johnson
Serge,
I don't have canned solutions, but I do think there needs to be greater
specificity and flexibility in address tagging. The page links to a
relatively new national (US) address standard and how we can adopt a
lightweight profile of the standard to gain that flexibility and
specificity.

HTH,

-- SEJ
-- twitter: @geomantic
-- skype: sejohnson8

Common sense is the collection of prejudices acquired by age eighteen. --
Einstein



On Tue, Oct 4, 2011 at 21:08, Serge Wroclawski emac...@gmail.com wrote:

 On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson sejohns...@gmail.com
 wrote:
  Hi all,
 
  I'd like to announce a broad-based project to improve addresses in OSM.
 The
  project page is here:
  https://wiki.openstreetmap.org/wiki/Address_Improvement

 Can you summarize the project?

 All the Wiki page says right now is there's a problem.

 What is your proposed solution?

 - Serge

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Ian Dees
I'm a bit confused about how Karlsruhe doesn't apply to the US.

When I'm adding addressing information I usually use the following two tags:

addr:street=*
addr:housenumber=*

Those seem to cover the vast majority of addressing use cases in the US.
What am I missing?

On Tue, Oct 4, 2011 at 8:17 PM, Steven Johnson sejohns...@gmail.com wrote:

 Serge,
 I don't have canned solutions, but I do think there needs to be greater
 specificity and flexibility in address tagging. The page links to a
 relatively new national (US) address standard and how we can adopt a
 lightweight profile of the standard to gain that flexibility and
 specificity.

 HTH,


 -- SEJ
 -- twitter: @geomantic
 -- skype: sejohnson8

 Common sense is the collection of prejudices acquired by age eighteen. --
 Einstein



 On Tue, Oct 4, 2011 at 21:08, Serge Wroclawski emac...@gmail.com wrote:

 On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson sejohns...@gmail.com
 wrote:
  Hi all,
 
  I'd like to announce a broad-based project to improve addresses in OSM.
 The
  project page is here:
  https://wiki.openstreetmap.org/wiki/Address_Improvement

 Can you summarize the project?

 All the Wiki page says right now is there's a problem.

 What is your proposed solution?

 - Serge



 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Ian Dees
When I use addr:street I put the entire street's name in the field.

Breaking apart that street name into pieces is the job of other tags, I
would imagine.

On Tue, Oct 4, 2011 at 8:31 PM, Steven Johnson sejohns...@gmail.com wrote:

 When you use addr:street you normally add the street type (e.g. road,
 street, land, drive, etc.) in the same field. You may also put cardinals in
 there, too.


 -- SEJ
 -- twitter: @geomantic
 -- skype: sejohnson8

 Common sense is the collection of prejudices acquired by age eighteen. --
 Einstein



 On Tue, Oct 4, 2011 at 21:26, Ian Dees ian.d...@gmail.com wrote:

 I'm a bit confused about how Karlsruhe doesn't apply to the US.

 When I'm adding addressing information I usually use the following two
 tags:

 addr:street=*
 addr:housenumber=*

 Those seem to cover the vast majority of addressing use cases in the US.
 What am I missing?

 On Tue, Oct 4, 2011 at 8:17 PM, Steven Johnson sejohns...@gmail.comwrote:

 Serge,
 I don't have canned solutions, but I do think there needs to be greater
 specificity and flexibility in address tagging. The page links to a
 relatively new national (US) address standard and how we can adopt a
 lightweight profile of the standard to gain that flexibility and
 specificity.

 HTH,


 -- SEJ
 -- twitter: @geomantic
 -- skype: sejohnson8

 Common sense is the collection of prejudices acquired by age eighteen.
 -- Einstein



 On Tue, Oct 4, 2011 at 21:08, Serge Wroclawski emac...@gmail.comwrote:

 On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson sejohns...@gmail.com
 wrote:
  Hi all,
 
  I'd like to announce a broad-based project to improve addresses in
 OSM. The
  project page is here:
  https://wiki.openstreetmap.org/wiki/Address_Improvement

 Can you summarize the project?

 All the Wiki page says right now is there's a problem.

 What is your proposed solution?

 - Serge



 ___
 Talk-us mailing list
 Talk-us@openstreetmap.org
 http://lists.openstreetmap.org/listinfo/talk-us




___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Mike N

On 10/4/2011 9:04 PM, Steven Johnson wrote:

The purpose of this project is to improve the tagging and better reflect
local addressing practice, particularly in areas where the Karlsruhe
schema does not fit local practice. This includes Japan and United
States, but likely other regions as well. We've made attempts to
consolidate a number of addressing discussions and proposals from around
the OSM wiki.


 I must confess that I haven't seen cases in the US that aren't already 
covered by Karlsruhe.   The only thing I can think of would be multi 
floors and building interiors - which aren't generally mapped in OSM 
anyway. If the problem is that something isn't documented clearly, that 
can be addressed.   One thing I noticed is that the page links to the 
proposed Karlsruhe schema rather than the 'approved' page:


https://wiki.openstreetmap.org/wiki/Key:addr

 I started to look at the US ... Address Data Standard and admit that 
I'd be blown away at trying to at trying to add any of it to typical OSM 
address data collection process.   I'd probably just end up entering 
everything with FIXME's and let someone else fix it.  g


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Serge Wroclawski
On Tue, Oct 4, 2011 at 9:17 PM, Steven Johnson sejohns...@gmail.com wrote:

 I don't have canned solutions, but I do think there needs to be greater
 specificity and flexibility in address tagging.

If there's something wrong with the way we're handling addresses,
let's bring it up on this forum. Since this is the talk-us list, is
there something US related that you've found doesn't work with the
current addressing system? I think this is exactly the right forum to
discuss it, with as many eyes as possible.

- Serge

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Toby Murray
I would put splitting cardinal directions out into their own tag on
the same level as breaking them out on streets. I'm sure some people
do it (in fact I seem to recall a discussion about that a few months
ago?) but I don't plan on making it a priority for myself any time
soon.

The one address component that I have seen missing is suite. We have a
couple of places where businesses share housenumbers and use suite
numbers or letters. I'm sure this is not uncommon. Some places write
it as 123-A on the outside of the building while others actually say
123 Suite A so it's kind of ambiguous whether to just include it in
the housenumber or split it into its own tag. But I've started using
an addr:suite tag where it is listed as a suite. Since there are only
300 uses in the database I'm guessing no tools make use of this tag
yet.

Toby

___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Announcement: Address Improvement project

2011-10-04 Thread Paul Norman
 -Original Message-
 From: Toby Murray [mailto:toby.mur...@gmail.com]
 
 
 The one address component that I have seen missing is suite. We have a
 couple of places where businesses share housenumbers and use suite
 numbers or letters. I'm sure this is not uncommon. Some places write it
 as 123-A on the outside of the building while others actually say
 123 Suite A so it's kind of ambiguous whether to just include it in
 the housenumber or split it into its own tag. But I've started using an
 addr:suite tag where it is listed as a suite. Since there are only
 300 uses in the database I'm guessing no tools make use of this tag yet.

I can't speak for certain about in the US, but on one summer work term I
lived in a house with an A suffix, and found out lots about addressing when
trying to get the cable installers to come to the right house.

In this case the A was part of the house number and 112A had no connection
to 112.

What I see around here more often is suite numbers (e.g. 101, 102) that are
placed in front of the number when written out, but sometimes are placed
after on forms. Eg http://www.openstreetmap.org/browse/node/1052967131 where
I mapped it as addr:housenumber=#104-7885

I don't view these types of addresses as a significant problem because OSM
is not well-suited for mapping of multi-story buildings with many shops
inside.


___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us