<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanks Tom, we can chase that up, or
alternatively if you know people at these networks you're welcome
to invite them to join OCM as a data provider (just CC myself and
J-C Saint-Po) - we are generally trying to convince them to
donate their information under a CC BY S-A 3.0 license
(<a class="moz-txt-link-freetext" href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>) but we'll
consider other terms as long as it means we can redistribute the
information via our API etc.<br>
<br>
In general most US stations have come from either the DOE AFDC
system or from Carstations.com (and these would probably have been
a point of reference for other map providers as well). It would
generally be better for OCM to pull from the networks own data
sets however these are often locked into systems we're not
permitted to copy from. Historically we've been flexible about our
data sources (so OCM data has mixed data licensing terms which can
be seen in the Data Provider section of each POI) but we're now
pretty strict about getting explicit permission - for instance we
got permission yesterday to redistribute another 600 Canadian
locations under an open data license.<br>
<br>
De-duplication is a big and surprisingly complicated problem.
Currently we will try not to add stations which are within 100m of
each other specifically because it may just be the same location
described differently. In general stations from the same network
are grouped under 1 POI with multiple equipment details entries.<br>
<br>
The absolute best way to get the information correct is for you to
edit things when you see that they're wrong, or add information if
you see it's not there. I realise that's where it gets frustrating
because you end up having to enter stuff into all the various apps
you use.<br>
<br>
Thanks for the offer of the perl script, we have a fairly
standardised import mechanism (written in C#, which is similar to
Java) which you can see here (excuse the mess, several of these
providers are not used): <br>
<a
href="https://github.com/openchargemap/ocm-system/tree/master/Import/OCM.Import.Common/Providers">https://github.com/openchargemap/ocm-system/tree/master/Import/OCM.Import.Common/Providers</a><br>
<br>
Chris<br>
<br>
On 24/05/2014 06:19, Tom Saxton wrote:<br>
</div>
<blockquote cite="mid:CFA5165D.62E13%25tom@idleloop.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>That's a fair point, although I don't think it's especially
proprietary since users can report the same information
manually. The stations are all public.</div>
<div><br>
</div>
<div>I'd suggest contacting Kent Rathwell:</div>
<div><br>
</div>
<div>Kent Rathwell</div>
<div>President and Founder</div>
<div>Sun Country Highway</div>
<div><a class="moz-txt-link-abbreviated" href="mailto:kent@suncountryhighway.ca">kent@suncountryhighway.ca</a></div>
<div>306-612-4600</div>
<div>800-467-6920</div>
<div><br>
</div>
<div>If Kent says it's OK, but can't give you a nice data feed, my
script may be useful.</div>
<div><br>
</div>
<div> Tom</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 5/23/14, 2:46 PM, "Paul Churchley" <<a
moz-do-not-send="true" href="mailto:paul@churchley.org">paul@churchley.org</a>>
wrote:</div>
</div>
<div><br>
</div>
<div dir="ltr">
<div>I think that OCM needs to be mindful of copyright when
taking data from other sources. In fact, I know that
Christopher Cook of OCM is mindful of that. So unless the
data at the Sun Country Highway Network is open source OCM
will be cautious of "grabbing" data from anywhere.<br>
<br>
</div>
This whole area of potential of breach of copyright and data
licensing is something we all need to me mindful of. :-)<br>
</div>
</span></blockquote>
<br>
</body>
</html>