On Mon, Mar 4, 2013 at 10:19 AM, Jonathan Harley j...@spiffymap.net wrote:
On 02/03/13 16:17, Erik Johansson wrote:
On Fri, Mar 1, 2013 at 11:39 AM, Jonathan Harley j...@spiffymap.net
wrote:
So - *must* you make your database of user-sourced geodata available to
the
OSM community? I answer
Hello,
Personally, I think this does leave a loophole where you could reverse
engineer OSM's data from imagery, but as I said at the time, I'm not worried
about it because so much accuracy would be lost. In any case,
Technically, it is possible to export in a format where accuracy is
100%
Am 04.03.2013 11:29, schrieb Tadeusz Knapik:
How come? ODbL doesn't enforce PW's license - if Produced Work is
licenced Public Domain, how do you reach somebody who used this PD
Produced Work to credit OSM?
Sincerely,
This is patently wrong, see ODbL 1.0 paragraph 4.3
On 04/03/13 11:53, Pieren wrote:
On Mon, Mar 4, 2013 at 10:19 AM, Jonathan Harley j...@spiffymap.net wrote:
Personally, I think this does leave a loophole where you could reverse
engineer OSM's data from imagery, but as I said at the time, I'm not worried
about it because so much accuracy
Am 04.03.2013 13:39, schrieb Jonathan Harley:
On 04/03/13 11:53, Pieren wrote:
On Mon, Mar 4, 2013 at 10:19 AM, Jonathan Harley j...@spiffymap.net
wrote:
Personally, I think this does leave a loophole where you could reverse
engineer OSM's data from imagery, but as I said at the time, I'm
Hello All!
Again thank you for all your feedback. Unfortunately after the feedback that I
have gotten so far on my initial 4 use-cases, and the 4 extra sub-use-cases I
added later, I still do not know for sure if the use-cases I presented would
trigger the ODbL share alike clause or not. My
Hello Michael,
Just to let you know that I never heard back from anyone on the issue of
the road data for Kosovo.
I am not sure how things work, but I was very unhappy that all that data
was removed after hundreds of work hours made by many volunteers in Kosova
to update the original dataset
Hello All!
Forgive me for the previous unfinished version of this mail, here is the
complete version.
Again thank you for all your feedback. Unfortunately after the feedback that I
have gotten so far on my initial 4 use-cases, and the 4 extra sub-use-cases I
added later, I still do not know
after reading all the documents/wiki/mailinglist I am still confused:
what forces producers to publish a derivative database and not just
produced work?
usecase:
a user takes a substantial part of osm db, hand modifies it (eg changes
name of a street to correct one, make a new hiking route ...)
On 04/03/13 16:53, Michal Palenik wrote:
after reading all the documents/wiki/mailinglist I am still confused:
what forces producers to publish a derivative database and not just
produced work?
Clause 4.6 of the ODbL, which says if you publish a produced work you
must make the database it
may i add a question into faq/use cases:
Q: I want to publish a slippy map/printed map based on OSM data.
Is it a produced work or derivated database?
A: The slippy map itself is a produced work, however the database you
used has to meet the same requirements as published derived database or a
I cannot help you bekim, It seems that the licensing is a lost cause.
I for one have stopped wasting time on it.
mike
On Mon, Mar 4, 2013 at 8:31 AM, Bekim Kajtazi bekim.kajt...@gmail.com wrote:
Hello Michael,
Just to let you know that I never heard back from anyone on the issue of the
road
12 matches
Mail list logo
