Re: [Talk-us] Quick intro and request to contribute

[stevea]

And I encourage you to ask "is this a one time import" or an "ongoing import"?
For your speed data a one time import might be OK.
For something like store locations, which change all the time, the 
data might just get stale in OSM.


The proper term for matching up data like this is 'conflation', and 
that sometimes involves one or more identifiers
you'd call conflation keys or match targets.  These could be 
database primary keys, road names, or route numbers.


See, Bryce, we do largely agree:  we both wish to help Dave achieve 
his speed limit upload.  Sometimes I "get something done in favor of 
nothing."  Sometimes I go whole hog and get every last bit of it done 
(including researching web sites and phone numbers, and entering 
those, too).


In this case, I seem to be saying to Dave, "walk, if you please." 
(Manually import, but with eyes/mind open to improving skills TOWARDS 
automation).  You seem to be saying to Dave "as you wish to run, here 
are vocabulary, help and ideas as to how."  (There are likely good 
strategies to doing an import of these data -- here is how I might 
begin.)  In my opinion, both are correct, and either of us could have 
given the others' advice.  Dave would do well to consider both and 
move towards what works best both for him and for OSM.


Often, it's good to have multiple answers:  chances of getting to the 
right one increase with options.  Yes, complexity of choosing does, 
too.  But that's a small cost, and I know I prefer having options to 
choose from.


Dave, one thing to consider along the lines of what Bryce is asking 
you is:  do you intend to keep these data up-to-date in OSM as they 
may change in the future?  This might change how you approach 
uploading the data.  (Manually, as a formal import, as a formal 
import with a good eye towards future updates, et cetera).


SteveA
California

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

Re: [Talk-us] Quick intro and request to contribute

[Bryce Nesbitt]

And I encourage you to ask "is this a one time import" or an "ongoing
import"?
For your speed data a one time import might be OK.
For something like store locations, which change all the time, the data
might just get stale in OSM.

The proper term for matching up data like this is 'conflation', and that
sometimes involves one or more identifiers
you'd call conflation keys or match targets.  These could be database
primary keys, road names, or route numbers.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Semi-spammy sorta-helpful edit: how to handle

[Bryce Nesbitt]

>
> I ran into something similar:  a note tag entered a week ago by user Noram
> (near a new node with name= Noram Auto Repair) which simply listed "Repair
> and service of Japanese, and American made automobiles and trucks."
>

Let's do better than that at http://www.noramautorepairservices.com/

But the bigger issues remain.  As OSM gains, it will become a target both
for the Mom & Pops looking to get
the word out and the less ethical. Axel's Mom was I assume just clumsy.
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Local user groups

[Clifford Snow]

On Tue, Jan 14, 2014 at 5:10 PM, Ian Dees  wrote:

> Sponsoring Meetup groups is rather difficult. Meetup doesn't have a way to
> sponsor a group's Meetup fees and doing it on a one-by-one basis is a lot
> of paperwork (how does one keep track of who gets payment and how do they
> make sure the payments are going to Meetup?)
>
> If someone were to relay to Meetup that they'd love to have a way to do
> this, that'd be super great...
>

I just asked. Awaiting a reply.


-- 
Clifford

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

Re: [Talk-us] Semi-spammy sorta-helpful edit: how to handle

[stevea]

I have not run into much spam in OSM, but while working on the 
keepright

link checker I ran into:
http://www.openstreetmap.org/user/Axel's%20Mom/

Looks like mom pimped up her son's self storage business, but rather clumsily.

I could (a) fix silently  (b) write to her on the off chance she 
will reply  (c) revert.


What do people think?


I ran into something similar:  a note tag entered a week ago by user 
Noram (near a new node with name= Noram Auto Repair) which simply 
listed "Repair and service of Japanese, and American made automobiles 
and trucks."


To the nearby node, I added shop=auto_repair and note=Japanese, 
American, truck.  If there WERE an existing tag (like 
cuisine=japanese for an amenity=restaurant) I would have used those, 
but I didn't feel like inventing one, so I leaned upon a note tag.


That was my way of fixing this note tag at a sweet spot of "quickly 
and correctly."  But not thoroughly, I admit (I could have started a 
voting page for auto_repair=light_truck, auto_repair=american and so 
on).


I didn't ask permission (it was a note tag) and I don't ask 
forgiveness (contributing something is better than nothing).  And 
while I won't lose sleep over the fact that I didn't posit a whole 
sub-tagging scheme (which would be nice, but is a small bit of work), 
I could have, done that, as well.  Someone later might come along and 
add the phone number and website (if one) to this node, and so on. 
One brick at a time is OK.


In short, I took what I had, blended as I know, uploaded something 
"appropriate" and didn't go further, though I could have.


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

Re: [Talk-us] Local user groups

[Ian Dees]

On Tue, Jan 14, 2014 at 5:25 PM, Clifford Snow wrote:

> Meetup is a nice tool to organize local groups. However the cost is
> expensive for individuals to start a Meetup group. I'm wondering if we can
> get some corporate sponsor to help offset the cost of establishing local
> communities. This is a not so subtle hint for all the corporations that
> make money off OSM!
>

Sponsoring Meetup groups is rather difficult. Meetup doesn't have a way to
sponsor a group's Meetup fees and doing it on a one-by-one basis is a lot
of paperwork (how does one keep track of who gets payment and how do they
make sure the payments are going to Meetup?)

If someone were to relay to Meetup that they'd love to have a way to do
this, that'd be super great...
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

[Talk-us] Semi-spammy sorta-helpful edit: how to handle

[Bryce Nesbitt]

I have not run into much spam in OSM, but while working on the
keepright
link checker I ran into:
http://www.openstreetmap.org/user/Axel's%20Mom/
Looks like mom pimped up her son's self storage business, but rather
clumsily.
I could (a) fix silently  (b) write to her on the off chance she will reply
 (c) revert.

What do people think?
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Quick intro and request to contribute

[stevea]

Thanks for the great info.  I'll definitely check out the Speed_limit
page for tips.

Also, I know that the data is largely good, partly because it _is_ the
Traffic Code and therefore is the legal origin of the speed limits of
the county, but mostly because I use many of the roads on there and every
one that I've checked out matches what I know and remember.

I can certainly enter data manually--like I said, I've made several edits
here and there over the last couple of years--but I was hoping to find
someone who is somewhat authoritative about mass changes.  I'm pretty
good with scripting and can probably not only extract the useful info
from the PDF (the document is here:
http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but
could probably also parse an OSM extract to match up the ways and nodes
that need to be changed.  But I don't know what to do with the information
or how to get it back into OSM in a "safe" way.

So, if there's anyone out there who can assist me with that, too, that'd
be great.  :-)


Dave, what I'd like to do is help to be encouraging to you to push 
ahead.  This is my initial "assist."


Sometimes, we look to others to "do it for us."  Sometimes, we look 
to others to say "help me do it myself."


There are a lot of methods to complete the task you have outlined.  I 
don't know if you are looking for "more automatic" methods, or are 
asking the way you seem to be because you can't or won't do the 
manual entry of the data yourself.  If you ARE willing (and able and 
ready) to do the manual entry of the data yourself, I recommend 
starting with a small subset of data, and an eye towards ways you can 
improve your own editing skills (either by becoming smarter at them, 
quicker/more facile with them, or some combination).  Think of 
yourself as "the authority" for changes.  As best you can.  Then, do 
them, maybe even automating them.  I'm fairly local to you, I do 
collaborate in OSM with one of "the firehouse folks," (shout out to 
Joe! in SLO county), I can point you to tools and methods, and I hear 
(a large part) of what you are asking.


You asked, so I am offering my opinion:  get comfy with JOSM if you 
haven't yet already.  The pdf file is a bunch of legal text.  There 
is "some work" (I'd say "substantial" or "medium-sized") involved 
with going from pdf to "well-mapped speed limit tags."  That path 
seems like it is your path.  Walk through a subset of these, 
downloading a little smidgen of the road segments you want to tag (at 
a time).  Consider the segments of the ways and where they begin/end 
often being at a jurisdictional boundary as helpful (maybe) and don't 
be afraid to split and join segments that already exist in OSM with 
authority as "I know that this makes sense."  Make use of the 
shift-click multiple selection action.  Tag "smartly selected" 
(perhaps with command-f find command, perhaps other methods) ways 
with your new speed limit tags.  Beef up these (manual) editing 
skills with simple practice.  See what might be automated as you do 
so.  Repeat, while improving.  That is safe.  (Oh, take a deep breath 
and be proud as you click the upload button, remembering that walls 
are built one brick at a time and Rome not in a day).


I believe this is largely what Tod just said.  It's simple to say 
"legalese -> (mystery robot smarts) -> script -> upload" but it is 
hard to achieve that as a goal, when expressed as a wish.  It doesn't 
really work like that.  It is doable but needs more thought.  Likely 
your thought, but we are listening.  You chose the word "contribute" 
in this thread.  Your contributions don't have to dead-end here, and 
they certainly are not doing so, but this one faces the hill it must 
climb, and there are few, if any, shortcuts.


We're listening (these talk-us pages).  We want to help you, the 
project, the data, all together.  You have permission to be 
authority, we do our best to achieve consensus as we do so.  We wish 
to set good example by way of precedent.  We wish to be helpful to 
one another as a community.  What you are talking about is 
"medium-sized."  One person CAN do it, it is also helpful, even 
necessary at some junctures to have help, especially if and as you 
need it.  This might mean advice, other people, shoulders to look 
over, lots of things.


The above is my opinion.  OSM missive me at stevea if you wish. 
What's next is how you think about it.


Best,
SteveA
California

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

Re: [Talk-us] Quick intro and request to contribute

[Dave Oksner]

It might take a bit, but I could probably do it.  If not, then it wouldn't
be unreasonable for a person to do it by hand.  As you mentioned, it's
only the ones in unincorporated areas, where the county sets the limits.
My thought was that if I was able to get it working for this small set, then
getting a larger set wouldn't be much more work (once you can convert the
raw data into something useful for merging).

I've joined the imports-us list and will introduce myself there shortly. :-)

Dave

On Tue, Jan 14, 2014 at 02:37:08PM -0800, Tod Fitch wrote:
> Looking at that PDF, it is not obvious to me how to script the data for mass 
> input. Probably would take less time to print out a copy of the PDF and sit 
> down with JOSM checking off each description as you enter it by hand. Maybe 
> it is my deficient scripting skills, but things like this don't look easy to 
> automatically parse:
> 
> "The speed limit shall be twenty-five miles per hour on Pacific Avenue 
> (County Road No. 4241) between 24th Street (County Road No. 4241) northerly 
> to Ocean Boulevard (County Road No. 4256) (Ord. 1225 § 10, 1972: Ord. 831 § 1 
> (part) 1965: prior code § 10-006.4(15))."
> 
> But sitting down with JOSM it would be reasonable for a human to enter the 
> data as long as the underlying roads were already in JOSM. Only 12 entries 
> for 25 MPH, 17 for 30 MPH, 36 for 35 MPH, 18 for 40 MPH, 21 for 45 MPH and 7 
> for 50 MPH. I can't believe that there are only 90 named streets in SLO 
> county, so I'm guessing it is not listing the ones in incorporated cities nor 
> ones for which the default state speed limit (residential area, etc.) is 
> assumed.
> 
> -Tod
> 
> 
> 
> On Jan 14, 2014, at 2:14 PM, Richard Welty wrote:
> 
> > On 1/14/14 4:51 PM, Dave Oksner wrote:
> >> I can certainly enter data manually--like I said, I've made several edits
> >> here and there over the last couple of years--but I was hoping to find
> >> someone who is somewhat authoritative about mass changes.  I'm pretty
> >> good with scripting and can probably not only extract the useful info
> >> from the PDF (the document is here: 
> >> http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but
> >> could probably also parse an OSM extract to match up the ways and nodes
> >> that need to be changed.  But I don't know what to do with the information
> >> or how to get it back into OSM in a "safe" way.
> >> 
> >> 
> > for any sort of "mass" project, you probably want to interact with the
> > US import committee first. mass/mechanical edits are something we are
> > concerned with. we meet in a google hangout every other monday
> > evening; Serge should be able to supply details. the mailing list is
> > imports...@openstreetmap.org
> > 
> > richard
> > 
> > -- 
> > rwe...@averillpark.net
> > Averill Park Networking - GIS & IT Consulting
> > OpenStreetMap - PostgreSQL - Linux
> > 
> > 
> > 
> > ___
> > 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 mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Local user groups

[Clifford Snow]

Meetup is a nice tool to organize local groups. However the cost is
expensive for individuals to start a Meetup group. I'm wondering if we can
get some corporate sponsor to help offset the cost of establishing local
communities. This is a not so subtle hint for all the corporations that
make money off OSM!

-- 
Clifford

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

Re: [Talk-us] Local user groups

[Brett Lord-Castillo]

I added in the two St Louis area groups and cleaned up our entries.
--Brett Lord-Castillo
OpenDataSTL 
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Quick intro and request to contribute

[Saikrishna Arcot]

Using the poppler library can convert PDF into plain text, and it will 
probably work on this PDF.

Saikrishna Arcot

On Tue 14 Jan 2014 05:37:08 PM EST, Tod Fitch wrote:
> Looking at that PDF, it is not obvious to me how to script the data for mass 
> input. Probably would take less time to print out a copy of the PDF and sit 
> down with JOSM checking off each description as you enter it by hand. Maybe 
> it is my deficient scripting skills, but things like this don't look easy to 
> automatically parse:
>
> "The speed limit shall be twenty-five miles per hour on Pacific Avenue 
> (County Road No. 4241) between 24th Street (County Road No. 4241) northerly 
> to Ocean Boulevard (County Road No. 4256) (Ord. 1225 § 10, 1972: Ord. 831 § 1 
> (part) 1965: prior code § 10-006.4(15))."
>
> But sitting down with JOSM it would be reasonable for a human to enter the 
> data as long as the underlying roads were already in JOSM. Only 12 entries 
> for 25 MPH, 17 for 30 MPH, 36 for 35 MPH, 18 for 40 MPH, 21 for 45 MPH and 7 
> for 50 MPH. I can't believe that there are only 90 named streets in SLO 
> county, so I'm guessing it is not listing the ones in incorporated cities nor 
> ones for which the default state speed limit (residential area, etc.) is 
> assumed.
>
> -Tod
>
>
>
> On Jan 14, 2014, at 2:14 PM, Richard Welty wrote:
>
>> On 1/14/14 4:51 PM, Dave Oksner wrote:
>>> I can certainly enter data manually--like I said, I've made several edits
>>> here and there over the last couple of years--but I was hoping to find
>>> someone who is somewhat authoritative about mass changes.  I'm pretty
>>> good with scripting and can probably not only extract the useful info
>>> from the PDF (the document is here:
>>> http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but
>>> could probably also parse an OSM extract to match up the ways and nodes
>>> that need to be changed.  But I don't know what to do with the information
>>> or how to get it back into OSM in a "safe" way.
>>>
>>>
>> for any sort of "mass" project, you probably want to interact with the
>> US import committee first. mass/mechanical edits are something we are
>> concerned with. we meet in a google hangout every other monday
>> evening; Serge should be able to supply details. the mailing list is
>> imports...@openstreetmap.org
>>
>> richard
>>
>> --
>> rwe...@averillpark.net
>> Averill Park Networking - GIS & IT Consulting
>> OpenStreetMap - PostgreSQL - Linux
>>
>>
>>
>> ___
>> 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 mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Local user groups

[Richard Weait]

http://usergroups.openstreetmap.de/

add your group to the wiki with the structured elements , and a bot
will add your group to the map.

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

Re: [Talk-us] Quick intro and request to contribute

[Tod Fitch]

Looking at that PDF, it is not obvious to me how to script the data for mass 
input. Probably would take less time to print out a copy of the PDF and sit 
down with JOSM checking off each description as you enter it by hand. Maybe it 
is my deficient scripting skills, but things like this don't look easy to 
automatically parse:

"The speed limit shall be twenty-five miles per hour on Pacific Avenue (County 
Road No. 4241) between 24th Street (County Road No. 4241) northerly to Ocean 
Boulevard (County Road No. 4256) (Ord. 1225 § 10, 1972: Ord. 831 § 1 (part) 
1965: prior code § 10-006.4(15))."

But sitting down with JOSM it would be reasonable for a human to enter the data 
as long as the underlying roads were already in JOSM. Only 12 entries for 25 
MPH, 17 for 30 MPH, 36 for 35 MPH, 18 for 40 MPH, 21 for 45 MPH and 7 for 50 
MPH. I can't believe that there are only 90 named streets in SLO county, so I'm 
guessing it is not listing the ones in incorporated cities nor ones for which 
the default state speed limit (residential area, etc.) is assumed.

-Tod



On Jan 14, 2014, at 2:14 PM, Richard Welty wrote:

> On 1/14/14 4:51 PM, Dave Oksner wrote:
>> I can certainly enter data manually--like I said, I've made several edits
>> here and there over the last couple of years--but I was hoping to find
>> someone who is somewhat authoritative about mass changes.  I'm pretty
>> good with scripting and can probably not only extract the useful info
>> from the PDF (the document is here: 
>> http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but
>> could probably also parse an OSM extract to match up the ways and nodes
>> that need to be changed.  But I don't know what to do with the information
>> or how to get it back into OSM in a "safe" way.
>> 
>> 
> for any sort of "mass" project, you probably want to interact with the
> US import committee first. mass/mechanical edits are something we are
> concerned with. we meet in a google hangout every other monday
> evening; Serge should be able to supply details. the mailing list is
> imports...@openstreetmap.org
> 
> richard
> 
> -- 
> rwe...@averillpark.net
> Averill Park Networking - GIS & IT Consulting
> OpenStreetMap - PostgreSQL - Linux
> 
> 
> 
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us



smime.p7s
Description: S/MIME cryptographic signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Quick intro and request to contribute

[Richard Welty]

On 1/14/14 4:51 PM, Dave Oksner wrote:
> I can certainly enter data manually--like I said, I've made several edits
> here and there over the last couple of years--but I was hoping to find
> someone who is somewhat authoritative about mass changes.  I'm pretty
> good with scripting and can probably not only extract the useful info
> from the PDF (the document is here: 
> http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but
> could probably also parse an OSM extract to match up the ways and nodes
> that need to be changed.  But I don't know what to do with the information
> or how to get it back into OSM in a "safe" way.
>
>
for any sort of "mass" project, you probably want to interact with the
US import committee first. mass/mechanical edits are something we are
concerned with. we meet in a google hangout every other monday
evening; Serge should be able to supply details. the mailing list is
imports...@openstreetmap.org

richard

-- 
rwe...@averillpark.net
Averill Park Networking - GIS & IT Consulting
OpenStreetMap - PostgreSQL - Linux





signature.asc
Description: OpenPGP digital signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Quick intro and request to contribute

[Dave Oksner]

Thanks for the great info.  I'll definitely check out the Speed_limit
page for tips.

Also, I know that the data is largely good, partly because it _is_ the
Traffic Code and therefore is the legal origin of the speed limits of
the county, but mostly because I use many of the roads on there and every 
one that I've checked out matches what I know and remember.

I can certainly enter data manually--like I said, I've made several edits
here and there over the last couple of years--but I was hoping to find
someone who is somewhat authoritative about mass changes.  I'm pretty
good with scripting and can probably not only extract the useful info
from the PDF (the document is here: 
http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but
could probably also parse an OSM extract to match up the ways and nodes
that need to be changed.  But I don't know what to do with the information
or how to get it back into OSM in a "safe" way.

So, if there's anyone out there who can assist me with that, too, that'd
be great.  :-)

Dave

On Mon, Jan 13, 2014 at 03:36:48PM -0800, stevea wrote:
> Hello Dave:
> 
> In California, the California Public Records Act or CPRA (1) and 
> recent court cases (2, 3) make data published by our government 
> (public) entities consistent with OpenStreetMap's license.  This went 
> all the way to the California Supreme Court and is established 
> statute, and so is essentially legally unassailable.
> 
> I (and I believe the greater OSM community) welcome your input of 
> these data into OSM.  This is done by adding the correct speed_limit 
> tags to the appropriate ways:  don't forget to add MPH otherwise the 
> units are assumed to be km/h.  See 
> http://wiki.openstreetmap.org/wiki/Speed_limit for our documentation.
> 
> You might also want to take a look at existing tagging on roadways 
> near you using the handy map at http://www.itoworld.com/map/124 which 
> shows existing speed_limit tagging in OSM via a custom renderer built 
> especially for that purpose.  For example see US-101 north of Cal 
> Poly and California State Route 58 through Santa Margarita.
> 
> It couldn't hurt to travel to the closest road and "check consistency 
> of published data against on-the-ground reality."  Use this as a 
> guide to judge for yourself the quality of the data.
> 
> If you trust the data, give a local roadway a try by entering it into 
> OSM and see if you like the way the results look (in the itoworld 
> map), and then take it from there.  You might continue to manually 
> add more, you might want to posit an import to the wider community 
> (and get help, or do it yourself), you might point others to the data 
> you have found and ask them to do an import.  But again, I welcome 
> you to enter the data into OSM and "enjoy" the results!
> 
> SteveA
> California
> 
> 
> (1) California Government Code, section 6250 et seq
> 
> (2) County of Santa Clara vs. California First Amendment Coalition, 
> Court of Appeal Sixth Appellate District #H031658, Super. Ct. No. CV 
> 072630, (2009) where the court held "the CPRA contains no provisions 
> either for copyrighting (this work of geographic data) or for 
> conditioning its release on an end user or licensing agreement by the 
> requester.  The record thus must be disclosed as provided in the 
> CPRA, without any such conditions or limitations."
> 
> (3)  Finally, in the Supreme Court of California, Sierra Club vs. 
> Superior Court of Orange County (S194708) ruled that "digital mapping 
> files known as geographic information systems must be released under 
> the state's public records law."  (2013)
> 
> See 
> http://articles.latimes.com/2013/jul/08/local/la-me-adv-map-ruling-20130709 
> as well as 
> http://articles.latimes.com/2010/jun/09/business/la-fi-digital-maps-20100609
> 
> 
> 
> >I'm new to this mailing list, but have contributed little changes here
> >and there for almost two years in San Luis Obispo county, California.
> >
> >I'd like to contribute more: specifically, speed limit info.  I recently
> >stubled across a document put out by the county Public Works department
> >that summarizes all of the county traffic codes, including the speed
> >limits of all county-maintained roads, and I would like to find out more
> >about how to incorporate this.  I have no illusions that my first act should
> >be to do a mass update or anything, but I think that if I knew what would
> >be useful information to provide, I could extract and process the data from
> >this document and give the data to someone else who does know what they're
> >doing.
> >
> >What should be my first step(s)?

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

[Talk-us] Local user groups

[Martijn van Exel]

Hi all,

I cleaned up the list of local OSM groups on the 'WikiProject United
States' page, deleting empty rows. If you run a local group and don't
see it listed here
http://wiki.openstreetmap.org/wiki/WikiProject_United_States - please
add a row with your local group info!

There must be a better & nicer way to collect and maintain this information...?
There's also 
http://www.meetup.com/find/?keywords=openstreetmap&radius=Infinity&sort=default
but not everyone is on meetup probably. There was also a local user
group map that I can't find now.

-- 
Martijn van Exel
http://oegeo.wordpress.com/
http://openstreetmap.us/

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

[Talk-us] Fwd: [OSM-talk] The game 'Kort' finally updates OpenStreetMap

[Simon Poole]

>From the talk mailing list (mandatory disclosure: yes I know the authors).


 Original-Nachricht 

Hi there,

I'm very proud to announce that finally Kort[1] (the OSM game) writes
back it's collected solutions to OSM! All changes are made by the OSM
user "kort-to-osm"[2], so it's easy to track them.

Our actions were coordinated with the local (Swiss) community and the
Data Working Group (DWG). According to the "Mechanical Edit Policy"[3]
all changesets have the tag mechanical=yes and the users profile page
contains all relevant information about the project. With all the extra
information in the changeset comment, we are able to trace back an edit
through Kort and even further to its source. By the way, for most
missions KeepRight[4] is the source.

Until now we made over 280 changes. All changes were validated by at
least 3 users. There are still lots of solved missions that are just
waiting to be validated, so that we are able to finally provides them to
OSM.

The source code for kort-to-osm is available on GitHub[5], you are very
welcome to open issues or provide pull requests. The underlying python
library to access the OpenStreetMap API is osmapi[6].

***Apart from this big step, Kort itself has some new features:***
- Upgrade to Sencha Touch 2.3 -> now all major browsers are supported
(IE, Firefox, Chrome, Safari)
- Thanks to our new database server, we can provide missions in the USA
as well (no more limits!)
- Our homepage kort.ch  is available in English, too :)


Any remarks, comments, issues etc. are very welcome!

Best regards Stefan

[1] http://www.kort.ch/index_en.html resp. http://play.kort.ch

[2] http://www.openstreetmap.org/user/kort-to-osm
[3] http://wiki.openstreetmap.org/wiki/Mechanical_Edit_Policy
[4] http://keepright.at 
[5] https://github.com/kort/kort-to-osm
[6] https://pypi.python.org/pypi/osmapi


___
talk mailing list
t...@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

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

Re: [Talk-us] Oklahoma relations spreadsheet

[Minh Nguyen]

On 08:34 2014-01-13, Peter Davies wrote:

Thanks, Mihh.

Actually I'm interested in any road on which significant traffic
incidents and slowdowns occur, including county roads and major named
urban streets (OSM primary, secondary, and maybe tertiary).  I've not
heard of anyone planning to go down to those levels with route
relations, but we might (one day) be able to generate them automatically
in our proposed location database importer, if folks would be
interested.  If it happened, this would return (export) the assembled
"bot" relations data to the OSM community.


One extreme example would be Logan County, Ohio. [1] Outside the county 
seat, Bellefontaine, virtually every road has a route shield, so I've 
been adding them all to route relations. So far, I've completed the 
western half of the county.


I'm primarily motivated by supporting the "shield renderer" that'll 
hopefully go up on osm.org someday. So any county or township that 
doesn't signpost its routes is not a particularly high priority for me.


Route relations certainly aren't going to supplant tags on ways for 
every use case. You'll still have to look at the individual ways to be 
sure about the road name.


[1] http://www.openstreetmap.org/relation/184059

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


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