Re: [Talk-us] What does the community want from a US local chapter?
I had a very difficult time trying to convert the hierarchy into terms I understand, and when I took to the wiki, I would come up against contradictory understandings. As for the other contributions you mention? They are less interesting to me, personally, probably because they are usually of minimal interest to me as a map consumer. Scott On Sat, Oct 1, 2011 at 8:59 PM, Ian Dees wrote: > Can I ask where you got this impression from? Perhaps we need to fix the > communication... In the vast majority of cases, "how roads should be > described" is decided. Editors like Potlatch and Cloudmade's Mapzen do a > pretty good job of describing visually (via icons or words) which tags > should be applied to which roads. > > The general hierarchy of motorway > trunk > primary > secondary > tertiary > is (hopefully) well understood. The argument seems to be over where people > want to draw the lines between those categories, and there are very few > (loud) people arguing about it. Either way, applying highway tags to ways is > a very small part of OSM: try adding POI, opening hours, parks, bike paths, > McDonald's, libraries, town halls, pubs/bars, etc. All of this is very > useful data and won't be subject to someone changing a highway tag. > -- Scott Rollins, * * *New info, effective 7/25:* 625 South St, Portsmouth, VA 23704 (757) 673-8992 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Mapping party best practices
Two critical elements of a successful mapping party are the people and publicity. WRT publicity, I have learned (the hard way) that publicity materials need to convey enough information to get people curious enough to show up. Also you need to disperse publicity through as many channels as you can. If you can target organized groups (e.g. boy/girl scouts, 4H, bicycling clubs, sports clubs, etc.) you have a better shot at getting good participation. And speaking of civic/youth organizations, in terms of people these groups are more likely to show up and take enthusiasm in the project, partly because they are naturally curious students, but also because they have community service requirements easily filled by OSM contrbutions. I also think retirees may be good candidates, though I haven't personally reached out to those groups. (Sadly, my experience with my fellow GIS professionals is that initially they show a great deal of curiosity about OSM, but they tend to be less committed than amateurs and more dismissive of OSM on accuracy grounds.) I'll also second Jim's suggestion of the Mapping Weekend How To. Good luck! -- SEJ -- twitter: @geomantic -- skype: sejohnson8 "Common sense is the collection of prejudices acquired by age eighteen." -- Einstein On Mon, Oct 3, 2011 at 22:07, Jim McAndrew wrote: > Hi, > > We're been trying to come up with ways to help people run mapping parties, > and have come up with a very basic outline. > You may find the best resource to be here: > http://wiki.openstreetmap.org/wiki/Mapping_Weekend_Howto > > As far as focusing on people, we've have good response from GIS groups, and > universities. > If you can find a local Geography department, you can send them a flyer > about the party. > Community colleges tend to be a good source too, and a lot of places have > GIS classes. > > The real hard part is to get the word out, and to the right people, but > there are a few places you can start. > > -- > Jim McAndrew > > On Mon, Oct 3, 2011 at 7:01 PM, Ian Dees wrote: > >> On Mon, Oct 3, 2011 at 7:51 PM, Martijn van Exel wrote: >> >>> Hi, >>> >>> As I am preparing my first mapping party here in Salt Lake, I am >>> wondering what works and what doesn't. I'm used to organizing events >>> in The Netherlands, but geographical and cultural differences may >>> require a different approach in the US so I'd like to poke your >>> brains: are there formats that work particularly well or not at all? >>> Particular types of venues to gather, interest groups to target, types >>> of mapping to do... Any input welcome. >> >> >> I had a decent response when I sought out GIS user groups and university >> folks. They seemed to be most interested in what OSM is and how to change >> it. They were also the quickest to disappear once they heard what OSM is >> (back then it was "you can't use ESRI? oh..."), but a few stuck and helped >> find other groups to work with. >> >> As far as location, I looked for places with fast wifi and decent places >> to sit down. Zoos, libraries, outdoor mall/commercial districts, etc. are >> all good places to start. >> >> ___ >> 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 mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] OSM US Chapter Voting Open
The OSM US board nominations have closed and elections are open. The following people were nominated to run: - Carl Anderson - Jim McAndrew - Randy Hale - Martijn van Exel - Richard Welty - Michal Migurski If you are a paid-up member of the OSM US local chapter you may vote by email for the next US local chapter board. To do this, send an e-mail to the following addresses containing details of your votes: To: ian.d...@gmail.com (Ian Dees - US local chapter secretary) cc: osmus2...@jonno.cix.co.uk (Jonathan Bennett - Independent scrutineer) cc: vote2...@weait.com (Richard Weait - Independent scrutineer) Subject: US Chapter Board Vote 2011 The content of the email should be a list of the candidates for whom you are voting. You may vote for up to five candidates. Any ballot with more than five candidates listed will be discarded as spoiled. Any ballot with conditions will be discarded as spoiled. Your ballot should include the name or email address that you used to register as a US Local Chapter member, if you are sending your vote from another email address. For more details, please visit the election wiki page: http://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Elections#2011-2012 If you have any questions not covered here, please ask me before voting. Thanks, Ian Dees ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
Hi, On 10/04/2011 03:14 AM, Nathan Edgars II wrote: Ah, the county line dupe problem. It would be nice if http://josm.openstreetmap.de/ticket/5867 were fixed. Personally I think OSM suffers too much from automated edits already. I am a big fan of people editing things while actually looking at them, rather than doing a few "select-all/fix-all" keystrokes without even knowing what gets fixed. I hope that we will get to a point where problems in OSM are fixed by humans who care for the data at that specific location. The knee-jerk reaction "oh, there's a problem, let's think of ways to fix that automatically" creates an atmosphere in which everyone waits for someone else to fix it automatically. I am very much in favour of banning all automatic or semi-automatic editing, including "search and replace" operations. With very few, individually discussed and community ok'd exceptions. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On 10/4/2011 2:09 PM, Frederik Ramm wrote: Hi, On 10/04/2011 03:14 AM, Nathan Edgars II wrote: Ah, the county line dupe problem. It would be nice if http://josm.openstreetmap.de/ticket/5867 were fixed. Personally I think OSM suffers too much from automated edits already. I am a big fan of people editing things while actually looking at them, rather than doing a few "select-all/fix-all" keystrokes without even knowing what gets fixed. Currently the only way to fix a dupe node in JOSM is to delete one and then re-extend all ways back to the other. If the node is in the middle of one of these ways, you also have to split. This is way too much work to fix a common issue. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Geography Awareness Week 2011
Hi all, Someone just told me about Geography Awareness Week[1] which is in November (coincidentally this is the week of GIS Day 2011 which is on Nov 16). This is the first I learned about it but it could be a good vehicle for OSM promotion / mapping events. This year's GAW apparently focuses on The Adventure in Your Community which seems like a good fit. I am going to align the SLC mapping party with that event and am working with the University of Utah to coordinate. It would be great if we could have a host of OSM related activities on GIS day! Martijn [1] http://education.nationalgeographic.com/education/collections/geographyawarenessweek/?ar_a=1 [2] http://www.gisday.com/ -- martijn van exel geospatial omnivore 1109 1st ave #2 salt lake city, ut 84103 801-550-5815 http://oegeo.wordpress.com ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On Tue, Oct 4, 2011 at 3:18 PM, Nathan Edgars II wrote: > On 10/4/2011 2:09 PM, Frederik Ramm wrote: >> >> Hi, >> >> On 10/04/2011 03:14 AM, Nathan Edgars II wrote: >>> >>> Ah, the county line dupe problem. It would be nice if >>> http://josm.openstreetmap.de/ticket/5867 were fixed. >> >> Personally I think OSM suffers too much from automated edits already. I >> am a big fan of people editing things while actually looking at them, >> rather than doing a few "select-all/fix-all" keystrokes without even >> knowing what gets fixed. > > Currently the only way to fix a dupe node in JOSM is to delete one and then > re-extend all ways back to the other. If the node is in the middle of one of > these ways, you also have to split. This is way too much work to fix a > common issue. Try selecting both nodes and using "m" to merge them. drag-select, m. One mouse gesture, one keypress. Easy. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On Tue, Oct 4, 2011 at 3:21 PM, Richard Weait wrote: > On Tue, Oct 4, 2011 at 3:18 PM, Nathan Edgars II > wrote: > > On 10/4/2011 2:09 PM, Frederik Ramm wrote: > >> > >> Hi, > >> > >> On 10/04/2011 03:14 AM, Nathan Edgars II wrote: > >>> > >>> Ah, the county line dupe problem. It would be nice if > >>> http://josm.openstreetmap.de/ticket/5867 were fixed. > >> > >> Personally I think OSM suffers too much from automated edits already. I > >> am a big fan of people editing things while actually looking at them, > >> rather than doing a few "select-all/fix-all" keystrokes without even > >> knowing what gets fixed. > > > > Currently the only way to fix a dupe node in JOSM is to delete one and > then > > re-extend all ways back to the other. If the node is in the middle of one > of > > these ways, you also have to split. This is way too much work to fix a > > common issue. > > Try selecting both nodes and using "m" to merge them. drag-select, m. > One mouse gesture, one keypress. Easy. A lot of times these overlapping ways are on county boundaries and share nodes with the border ways, making it very difficult to only select the nodes that belong to the highway=* ways. Also, merging nodes doesn't merge the overlapping ways; when all the nodes are merged you still have two distinct ways that use the same nodes. Currently, one of the duplicate ways needs to be split and deleted. This process takes many keystrokes and mouse gestures :) ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On 10/4/2011 4:21 PM, Richard Weait wrote: Try selecting both nodes and using "m" to merge them. drag-select, m. One mouse gesture, one keypress. Easy. Holy shit. It would still be nice to be able to do it en masse (given that the problem was caused in the first place by an import) but this is really useful. Thanks. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On 10/4/2011 4:27 PM, Ian Dees wrote: A lot of times these overlapping ways are on county boundaries and share nodes with the border ways, making it very difficult to only select the nodes that belong to the highway=* ways. I usually use a filter to hide any boundaries. Of course you have to detach the boundaries from the roads first (hit G). ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On Tue, Oct 4, 2011 at 4:27 PM, Ian Dees wrote: > On Tue, Oct 4, 2011 at 3:21 PM, Richard Weait wrote: [ob on topic: It is awesome that geofabrik is making this debug layer available outside of Europe! Thank you!] >> Try selecting both nodes and using "m" to merge them. drag-select, m. >> One mouse gesture, one keypress. Easy. > > A lot of times these overlapping ways are on county boundaries and share > nodes with the border ways, making it very difficult to only select the > nodes that belong to the highway=* ways. Not in that cases I just tried. I had two roads perpendicular to the border and bisected by the border. No border node on the scene. If there were, I would consider deleting the border node as long as it doesn't wreck the border shape. Then merge the nodes. > Also, merging nodes doesn't merge the overlapping ways; when all the nodes > are merged you still have two distinct ways that use the same nodes. Not in the case I looked at. Yes, undoing a duplicate import and dupe-ways is a pain. This is not that. ;-) ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
On 10/4/2011 4:42 PM, Richard Weait wrote: Not in the case I looked at. Yes, undoing a duplicate import and dupe-ways is a pain. This is not that. ;-) The problem comes when there's a road along the county line. This is especially common in the Midwest. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Announcement: Address Improvement project
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
On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson 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
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 wrote: > On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson > 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
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 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 wrote: > >> On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson >> 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
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 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 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 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 wrote: >>> On Tue, Oct 4, 2011 at 9:04 PM, Steven Johnson 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
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. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] OSM inspector routing layer now also available in the US
> > On Tue, Oct 4, 2011 at 3:18 PM, Nathan Edgars II wrote: >> On 10/4/2011 2:09 PM, Frederik Ramm wrote: >>> >>> Hi, >>> >>> On 10/04/2011 03:14 AM, Nathan Edgars II wrote: Ah, the county line dupe problem. It would be nice if http://josm.openstreetmap.de/ticket/5867 were fixed. >>> >>> Personally I think OSM suffers too much from automated edits already. I >>> am a big fan of people editing things while actually looking at them, >>> rather than doing a few "select-all/fix-all" keystrokes without even >>> knowing what gets fixed. >> >> Currently the only way to fix a dupe node in JOSM is to delete one and then >> re-extend all ways back to the other. If the node is in the middle of one of >> these ways, you also have to split. This is way too much work to fix a >> common issue. > > Try selecting both nodes and using "m" to merge them. drag-select, m. > One mouse gesture, one keypress. Easy. No! If you have two different items with a duplicate node, for example, a street and a landuse=, then you have combined them into one. Good luck at separating them back into their individual parts. -Dion ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Announcement: Address Improvement project
On Tue, Oct 4, 2011 at 9:17 PM, Steven Johnson 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] OSM inspector routing layer now also available in the US
On 10/4/2011 9:44 PM, Dion Dock wrote: On 10/4/2011 2:09 PM, Frederik Ramm wrote: Try selecting both nodes and using "m" to merge them. drag-select, m. One mouse gesture, one keypress. Easy. No! If you have two different items with a duplicate node, for example, a street and a landuse=, then you have combined them into one. Good luck at separating them back into their individual parts. Can you give an example of two ways where this happens? ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Announcement: Address Improvement project
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
> -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
Re: [Talk-us] Announcement: Address Improvement project
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
