[Talk-us] Battlegrid back up

2015-01-14 Thread Martijn van Exel
Finally I had some time to fix the Battlegrid. (If you hadn't noticed, it
has been broken for a while.)

A diary entry with (slightly) more info and a link to the battlegrid (in
case you didn't know it was battlegrid.us) --
http://www.openstreetmap.org/user/mvexel/diary/28460

Happy mapping,

-- 
Martijn van Exel
skype: mvexel
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Please review: new proposed bylaws for OSM US, open for comments until Jan 20th

2015-01-14 Thread Clifford Snow
Alex,
In the by-laws document, paragraph 5.2, it specifies that the Chapter
should have members mailing addresses, not just email addresses. I don't
recall ever giving my address when I first joined. Most likely I've since
forgotten but is the Chapter collecting that information?

Thanks,
Clifford


-- 
@osm_seattle
osm_seattle.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Please review: new proposed bylaws for OSM US, open for comments until Jan 20th

2015-01-14 Thread Ian Dees
Clifford, we do collect that information from our members. The current form
doesn't have it marked as required but I'll probably change that after you
pointed this out.

On Wed, Jan 14, 2015 at 5:22 PM, Clifford Snow cliff...@snowandsnow.us
wrote:

 Alex,
 In the by-laws document, paragraph 5.2, it specifies that the Chapter
 should have members mailing addresses, not just email addresses. I don't
 recall ever giving my address when I first joined. Most likely I've since
 forgotten but is the Chapter collecting that information?

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


Re: [Talk-us] GNIS POI populations

2015-01-14 Thread Marc Gemis
Or Overpass + Level0   :-)

regards

m.



On Tue, Jan 13, 2015 at 7:50 PM, Richard Fairhurst rich...@systemed.net
wrote:

 Minh Nguyen wrote:
  I think we should consider a mechanical edit to update these tags

 While you're thinking about GNIS mechanical edits, could I suggest one for
 GNIS-sourced POIs with (historical) in the name?

 There are several gazillion amenity=post_office, name=Fred Creek Post
 Office
 (historical) in the database. Clearly these aren't actually post offices
 any
 more. Ideally I guess they should be disused:amenity=post_office, or
 historic:amenity, or something.


 https://www.google.co.uk/search?q=site%3Aopenstreetmap.org+gnis+historicalgws_rd=ssl

 I'd do it myself but this is about the one area where you _do_ need JOSM
 rather than P2. ;)

 cheers
 Richard





 --
 View this message in context:
 http://gis.19327.n5.nabble.com/GNIS-POI-populations-tp5829895p5829925.html
 Sent from the USA mailing list archive at Nabble.com.

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

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


[Talk-us] Please review: new proposed bylaws for OSM US, open for comments until Jan 20th

2015-01-14 Thread Alex Barth
To all OpenStreetMap US members:

Our new proposed bylaws are open for comments until **January 20th 3PM
Eastern**.

As part of the process of bringing our organization in line with IRS
requirements for a 501 c 3 tax deductible status we are applying for our
legal counsel has recommend we update our bylaws to comply with District of
Columbia law - the District of Columbia being the seat of OpenStreetMap US.

Considering your feedback we will bring the new bylaws to a vote by the
OpenStreetMap US membership after January 20th. To pass the new bylaws, we
will need a majority of 2/3 of 50 % of the membership (currently there are
229 members).

Per vote of January 14th, the OpenStreetMap US board unanimously recommends
to adopt the new proposed bylaws as available here:

- PDF http://cl.ly/3X2T1w0U0v0i
- Word http://cl.ly/2a051Q1K0k1M

Compare with the current bylaws:

http://wiki.openstreetmap.org/wiki/Foundation/Local_Chapters/United_States/Bylaws

While the new bylaws are rewritten from ground up following proven
templates for 501 c 3 organizations, there are actually few effective
changes:

Should all members be deceased or dissolved or should all members have
resigned, additional members may be nominated by the Board and elected at
any annual or special meeting of the Board.
4.1 (c) - ensures that non of the board members personally benefits of OSM
US earnings
4.1 (d) - Explicitly states the board can appoint advisors (isn't
explicitly denied in current Bylaws)
4.2 - board can be 3-9 directors (now 4-9), must be uneven number (now: no
regulation)
4.3 - All directors shall be members of the Corporation
4.5 - Removal. Any director may be removed with or without cause at any
time during his or her term at any regular, special or annual meeting of
the members, by a two-thirds (2/3) majority vote of a minimum of fifty
percent (50%) of all member (this used to be )
4.8 - Ability to form committees including executive committees - this is
fine as it's in-line with the laws of DC and not something that the
previous Bylaws prohibited
4.9 - this is new and will help us with gaining 501 c3 status: Directors
cannot be paid for their services to OSM US but may be reimbursed for
expenses
5.6 - Quorum. At meetings, a majority of the directors then in office or a
majority of the current members shall be necessary to constitute a quorum
for the transaction of business. - this is better than todays rule which
says a quorum is determined at the beginning of a meeting (VII/3)
12.1 - Dissolution - this is an important change for us to be able to
attain 501c3 status: Current bylaws say upon dissolution, OSM US assets go
to OSMF, new bylaws say  shall be disposed of in accordance with the laws
of the District of Columbia, Section 501(c)(3) of the Code - which de
facto ensures that OSM US assets remain in a 501 (c) (3) non profit.

Alex

PS:

- To become a member, sign up here: http://openstreetmap.us/join/
- To inquire about your membership status, send us an email at
members...@opensteretmap.us

--
Alex Barth
Vice President
OpenStreetMap United States Inc.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] GNIS POI populations

2015-01-14 Thread Paul Norman

On 1/13/2015 5:34 AM, Minh Nguyen wrote:
It looks like most of the place=city/town/village/hamlet POIs from 
GNIS are tagged with 2000 Census populations in the population tag. 
These population tags allow renderers to label places with font sizes 
corresponding to population, which is a pretty common use case.


I had done a PR which would have added population sorting for place 
names, but as a style maintainer I'm interested in what styles use 
population for sizes.


I think we should consider a mechanical edit to update these tags to 
the 2010 Census figures en masse. I've been updating individual places 
as I edit them for other reasons, but this tag is most useful when its 
vintage is consistent across the board. 
Although I somewhat like the idea of updating the population tags, I 
think we should give higher priority to fixing their tagging. When I did 
some cleanup of Washington place=city POIs I found that I ended up 
retagging most, deleting many, and only a few were place=city.


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


Re: [Talk-us] Place classifications

2015-01-14 Thread Minh Nguyen

On 2015-01-13 05:28, Minh Nguyen wrote:

On 2015-01-12 11:23, Elliott Plack wrote:

Great start on this Minh,

I tried to tackle this in the Baltimore Washington region last year.
After reading the wiki, I decided on the following classifications:

* hamlet: census population was less than 200
* village: census pop. between 200 and 1
* town: census pop. between 10001 and 5
* city: major hub urban centers above 5


I like the idea of lowering the bar for place=city somewhat, to rope in
smaller cities that have their own suburbs as part of a micropolitan
area. However, if we just go by population, the map ends still ends up
rather sparse, making OSM look undermapped.

Most rural counties have a center of commercial activity, often the
county seat (or a former county seat). Even though its population may
not reach 10,000, it's significant enough to be labeled at the same zoom
levels as those that do. For example, I made an exception for Hillsboro,
OH. [1] Nowhere else in the county comes close to its population of
6,605. As a county seat, it has its own daily newspaper, radio station,
fairgrounds, general aviation airport, high school, and two U.S.
highways. I cite attributes like these in the changeset comment or note
tag whenever making an exception.

[1] http://osm.org/relation/183049


There are some CDPs though that would be a city by population alone, but
really don't have a true city feel, and cartographically would look bad
as being a city on a map. The tricky one is Glen Burnie, sprawl area
south of Baltimore with no urban core, yet the pop is over 65k. It is
marked as a city now, but really should be town I think. I like your one
city per metropolis idea.


In suburban areas, even a city in the official sense may lack a downtown
core. But yes, if you'd consider Glen Burnie to be subordinate to
Baltimore, place=city is probably too prominent. You wouldn't consider
any town to be a suburb of Glen Burnie.

The unincorporated places I referred to the other day are different than
CDPs. They came from the GNIS database and likely originated as
century-ago post offices, cemeteries, or railroad stops. Wikipedia and
the Census Bureau are mum on most of these places, but it's entirely
possible that they're marked on the ground with signs. I haven't heard
back from the mapper who made them into towns, but I'd like to revert
their changes soon.


Fortunately it was just a misunderstanding. They explained that 
place=hamlet appeared wrong, since no one uses the word hamlet in this 
part of the country. They're using mostly Potlatch 2 and JOSM. P2's 
basic mode does have human-friendly preset names, but none of the 
popular editors attempts to bridge this particular Britishism/New-Yorkism.


Though some of these POIs look so obscure they might not even qualify 
for place=isolated_dwelling...


--
m...@nguyen.cincinnati.oh.us


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


Re: [Talk-us] GNIS POI populations

2015-01-14 Thread Minh Nguyen

On 2015-01-14 01:29, Paul Norman wrote:

On 1/13/2015 5:34 AM, Minh Nguyen wrote:

It looks like most of the place=city/town/village/hamlet POIs from
GNIS are tagged with 2000 Census populations in the population tag.
These population tags allow renderers to label places with font sizes
corresponding to population, which is a pretty common use case.


I had done a PR which would have added population sorting for place
names, but as a style maintainer I'm interested in what styles use
population for sizes.


Here are a couple that use it:

https://github.com/Citytracking/Terrain
as seen at: http://maps.stamen.com/terrain/
https://github.com/migurski/OSM-Solar

I do see quite a few instances of population-based sorting on GitHub:

https://github.com/search?q=planet_osm_point+populationtype=Code

But the difference between 2006 and 2010 populations is unlikely to be 
large enough to matter much for this use case.


Still, weighting city labels by population is a common enough practice 
dating back to the days of paper maps. Someone trying to emulate it with 
OSM data would find the `population` tag much more convenient than 
conflating with an external source, since precision would be less 
important than accuracy.



I think we should consider a mechanical edit to update these tags to
the 2010 Census figures en masse. I've been updating individual places
as I edit them for other reasons, but this tag is most useful when its
vintage is consistent across the board.

Although I somewhat like the idea of updating the population tags, I
think we should give higher priority to fixing their tagging. When I did
some cleanup of Washington place=city POIs I found that I ended up
retagging most, deleting many, and only a few were place=city.


In Ohio and surrounding states, I've seen lots of incorrect `place=city` 
on boundary relations, but all the `place=city` POIs were correct. I 
think the `place` tags on those relations were set to whatever the TIGER 
classification happened to be. On the other hand, there are plenty of 
`place=hamlet`s on POIs that should either be deleted or turned into 
named landuse areas (mostly trailer parks).


--
m...@nguyen.cincinnati.oh.us


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