Am 31.05.2023 um 22:08 schrieb Christian Quest:
... OSM editors integration.
That was one of the reasons why I was asking, as I have already done
some work on a STAC layer based on the GeoVisio API.
OpenPGP_signature
Description: OpenPGP digital signature
__
Christian, does this relate in some fashion to Geovisio?
And a, I suppose, obvious observation: key for adoption in OSM would be
an easy to access API for editing apps. Does that exist/are there plans
for one?
Simon
Am 30.05.2023 um 16:01 schrieb Christian Quest:
Le 24/05/2023 à 14:31, Greg
Am 12.04.2023 um 16:20 schrieb Mateusz Konieczny via talk:
From legal point of view it depends on specifics, but yes it can be
legal to
render using odbl+proprietary data.
See
https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Horizontal_Map_Layers_-_Guideline
It should be note
Not quite unexpected this discussion has already gone off on a tangent
about stable ids. My question on the other hand would be: what do you
actually want to achieve and what would you expect an application to do
with the parameter?
It should be noted that we already have a couple of URI schem
Am 30.11.2022 um 18:50 schrieb Minh Nguyen:
..
The contributor terms in question state:
This Agreement shall be governed by English law without regard to
principles of conflict of law.
[1]
https://wiki.osmfoundation.org/wiki/Special:PermanentLink/9165#Miscellaneous
My understanding of what
Am 29.11.2022 um 15:30 schrieb Greg Troxel:
...
Also, what we need is a copyright license, so that's not necessarily --
and hopefully isn't -- a contract.
Well there is this kind of underlying assumption that for most material
in question, with the exception of actual maps, there is no copyrigh
On 28.11.22 at Simon Poole wrote:
What is "OSM Contributor Terms compatibility" supposed to be?
Ok, this is clearly imprecise wording.¹
The context is that we would like to offer data donors a standard
legal text that they can use to make their data available to OSM in
such a way
Am 29.11.2022 um 03:57 schrieb Minh Nguyen:
Vào lúc 15:48 2022-11-28, Tobias Knerr đã viết:
On 28.11.22 at Simon Poole wrote:
What is "OSM Contributor Terms compatibility" supposed to be?
Ok, this is clearly imprecise wording.¹
The context is that we would like to offer dat
Am 28.11.2022 um 20:11 schrieb Amanda McCann:
Hello fellow OSMers.
As you are no doubt aware, OSM requires that data imports be listed on the OSM
Wiki ( https://wiki.openstreetmap.org/wiki/Import/Catalogue ), including if the
source is “ODbL OK status”.
At the Nov. 2022 OSMF Board meeting (2
Am 27.10.2022 um 06:17 schrieb Michael Collinson:
and note that Bing imagery is provided to us on the same basis - for
use in OSM but not otherwise.
Mike
Bing imagery is available for inspection to everybody, for use in OSM
terms are relaxed that would otherwise prohibit tracing etc.
Not
Am 12. Oktober 2022 20:04:42 MESZ schrieb Mike Thompson :
>On Wed, Oct 12, 2022 at 11:42 AM Simon Poole wrote:
>
...
>>
>Thanks. Unfortunately most of the time I will be surveying without a data
>connection, so this isn't going to work for me.
I would recommend using
The alerts are generated when data is downloaded/merged and the device location
is within the specified radius around the object causing the notification.
With other words you need to have one of the auto download options enabled for
the mechanism to work (or you need to replace all the data).
have noticed that Google Maps somehow seems to get a location at
times when all other apps are struggling.
I'm not entirely convinced the playing field is level there.
On Sun, 20 Dec 2020, 18:18 Simon Poole, <mailto:si...@poole.ch>> wrote:
I don't expect side loading to
I don't expect side loading to be a thing for very much longer. Given
googles crack down on anything using location, see
https://twitter.com/vespucci_editor/status/1331541328883298306 for some
of the drama, it would seem to be silly to leave that avenue open.
Definitely you are going to run in
Am 08.12.2020 um 18:36 schrieb Rory McCann:
Yes, fundamentally, you're 100% correct. The ODbL licence is the thing that
matters when it comes to what's legally required. And that says nothing about
“device independent pixels” or “javascript popup clicks”, it only refers to the
mental state of
Am 30.10.2020 um 16:33 schrieb Dave F:
But anyway... Point slit stands: Why did iD take this authoritarian
position.
Already pointed this out n-times now: because it synthesizes an area
object type.
As has been noted other, editors don't make this assumption.
Other editors don't try to
ways. They aren't meant to be the default for all objects.
See above.
Simon
DaveF
On 27/10/2020 08:11, Simon Poole wrote:
Its done that essentially since day one. As Bryce points out doing so
keeps the object a valid "area" (and iD makes a valiant effort to
stop you from break
Its done that essentially since day one. As Bryce points out doing so
keeps the object a valid "area" (and iD makes a valiant effort to stop
you from breaking that).
It is also one of my favourite examples in talks why trying to keep
things simple for the user is very difficult and some times
You need to take this up with the DWG (d...@osmfoundation.org) once
direct contact with the mapper in question has failed. Posting to this
and the tagging list is not going to achieve anything except that you
will receive pointers to the DWG.
Simon
Am 24.10.2020 um 17:54 schrieb Erick de Oliv
Am 18.10.2020 um 16:49 schrieb Colin Smale:
On 2020-10-18 15:04, Simon Poole wrote:
Am 18.10.2020 um 11:07 schrieb Rory McCann:
Like mnany things in OSM, the reason it hasn't been done is because no-one has actually done it
yet. It looks like other people find your idea of "l
Am 18.10.2020 um 11:07 schrieb Rory McCann:
Like mnany things in OSM, the reason it hasn't been done is because no-one has actually done it
yet. It looks like other people find your idea of "levels" and "badges"
interesting, so you should try attempt it yourself.
Like many things in OSM, the
Am 07.10.2020 um 10:25 schrieb Christian Quest:
We have tested blurring using image segmentation which allows to blur
full parts of pictures like people and cars, not only faces and
license plates.
Here is the result: https://takeitout.cquest.org/photo/cquest/blurred/
The code used is on
Am 07.10.2020 um 01:13 schrieb Niels Elgaard Larsen:
...
You will probably have to let users add and remove blurs.
That is what Mapillary do.
They do not, they stopped providing that facility literally years ago,
and they've gone as far as no longer storing unblurred images even for a
limited
Nominatim tries to build correct address hierarchies from the data, in
particular it suspects a matching street (name) in the vicinity if an
addr:street tag is specified. While it will match a wide range on name
tags on streets (see
https://github.com/osm-search/Nominatim/blob/master/settings/impor
As, independent of any other concerns, a matter of good form, I would
want to point out that there is no such thing as ownership of
OSM-objects, and discussing a concept of "their OSM-objects" is starting
the discussion on the wrong foot.
Am 22.08.2020 um 11:08 schrieb pangoSE:
> Hi
>
> I would li
To add to what Andy has already said, complaints about people using
private paths etc are relatively common, not a large number in absolute
terms, but there tend to be a couple each month which either land with
the DWG, or LWG, or naturally with the local community (I've handled a
couple of them wi
The "names" in wikidata are mostly the names of WP pages for the object
in question and have little to do with actually existing names (as per
the OSM definition) of places.
It would be a massive drop in quality if we would do the proposed switch.
Simon
Am 09.08.2020 um 10:25 schrieb pangoSE:
>
Am 04.08.2020 um 17:05 schrieb Alexandre Oliveira:
>> At this time nobody is proposing anything more than giving P2 a bit more
>> life for a small sum of money
> And as myself and others have brought up, it's not a good idea to
> spend money to port P2 from a dead technology to another dead
> tec
Could we move all the programming language du jour fanboying, apps that
have nothing to do OSM and other unrelated to the topic discussions
somewhere else please?
And yes it underlines my point that regardless of how exotic the feature
is, you are always going to find somebody that finds it critic
Am 02.08.2020 um 11:31 schrieb mmd:
> ...
> In a more mid-term, I really like to see a move away from such
> proprietary platforms to an editor that runs in a browser
> out-of-the-box.
...
Don't we already have that?
signature.asc
Description: OpenPGP digital signature
_
Am 02.08.2020 um 01:03 schrieb Skyler Hawthorne:
> ...
>
> Sorry if this sounds harsh, but I think using any funds at all to
> continue support for a tool that 1% of editors use would be wasteful.
> Flash is, for all intents and purposes, a dead technology. This money
> is better spent on other us
That was a good decade ago, nothing that would factor in to a decision
now (because Linux could not be a target platform to start with).
Am 01.08.2020 um 10:16 schrieb Sören Reinecke via talk:
> So far as I understood Adobe dropped Linux support for its AIR
> plattform. If that is right, then I a
Am 19.06.2020 um 13:47 schrieb Nick Whitelegg:
>
> (Disclaimer: I am the developer of said project)
One of the key functionalities required for such a project to be useable
in countries with developed privacy regulation is the ability to
automatically pixelate relevant parts of the images with a
I've advocated for this in the past, but getting this right from a
business logic pov is fairly tricky and is yet another thing that an
editor needs to keep track of when creating and modify geometries, and
changing tags. From the top my head at least: new object creation,
dragging nodes and ways,
Am 09.06.2020 um 18:04 schrieb nd...@redhazel.co.uk:
>
> Who owns the iD project now? What's happened after "nearly all of the
> original authors left Mapbox", has the project ownership been
> transferred from Mapbox to OSMF, or perhaps to current maintainers?
> Does Mapbox still retain the o
Am 09.06.2020 um 14:18 schrieb Mikel Maron:
> ---
>
> As it should be.
Mapbox developers decide on (not just have input on) budgets, product
specs etc etc etc etc etc etc for the company?
signature.asc
Description: OpenPGP digital signature
___
tal
Frederik has already corrected most of your misconceptions, so just some
additional comments;
Am 09.06.2020 um 12:32 schrieb nd...@redhazel.co.uk:
>
> - Taking control from the original authors would slow down, if not
> stall, the development of iD.
>
Nearly all of the original authors left Mapbox
Hi Jose
Maybe you should have a look at https://github.com/komoot/photon which
is the go to ES based solution for OSM data (I'm not quite sure how you
missed it with the large amount of research you did, but anyway).
The other bit to understand is that the design goals of Nominatim, at
least his
ubject line so it is more specific
>> than "Re: Contents of talk digest..."
>>
>>
>> Today's Topics:
>>
>>1. Re: our Q&A site help.openstreetmap.org is dying
>> (Mateusz Konieczny)
>>2. Re: our Q&A site help.openstreet
Am 20.05.2020 um 15:45 schrieb Mateusz Konieczny via talk:
> Well, if nobody will volunteer to fix it then we will need to select
> between
> stack exchange migration and simply killing the QA site.
We could simply pay for the migration (and if necessary for some support
going forward), the thing
Am 13.05.2020 um 13:46 schrieb Mateusz Konieczny via talk:
...
> And, no, a typical user will not click on a hidden button or check
> deeply in settings.
>
...
Nobody ever even remotely indicated that attribution via a "hidden
button" or deep in any settings was sufficient, in fact the draft
guid
Am 12.05.2020 um 23:03 schrieb Mateusz Konieczny via talk:
>
>
>
> May 12, 2020, 05:48 by rockyt...@gmail.com:
>
>
> As Joseph said:
>
> The attribution goes on the map.
> This is not a difficult requirement to meet.
>
>
> The most recent version of the guidelines
>
Am 2. Mai 2020 15:44:33 MESZ schrieb Christoph Hormann :
>
>> The only time in the past this
>was done was with the change to the ODbL in 2012 IIRC.
That is not correct, the licence change process has never been invoked.
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit Kaiten Mai
Am 27.04.2020 um 19:49 schrieb Alexandre Oliveira:
> Hello!
>
> I'll try to be brief and explain the main problems that exist with
> OSM's way of handling lack of (proper) attribution.
>
There was just a (nearly 100 messages) long thread on the subject here
not to mention a longish consultation l
Am 17.04.2020 um 13:20 schrieb Christoph Hormann:
> ...
> Independent of what the OSMF suggests in the future - i would probably
> continue attributing "OpenStreetMap contributors" where feasible to
> clarify that i am crediting the contributors and not the OSMF.
With the exception of imported
Sarah has already given the answer, but a small remark anyway: I would
suggest following the operations twitter account
https://twitter.com/OSM_Tech as that is the place you are most likely to
see short term notices about these kind of things.
Simon
Am 16.04.2020 um 08:10 schrieb Andrzej Kępys:
>
We currently are lacking a simple lightweight way of blocking write
access to the API, but it is being looked at.
This would normally be the ultima ratio as it essentially means all work
already done before an upload is lost, but in the case of a 1 change per
changeset app as healthsite.io it coul
Am 20.03.2020 um 20:00 schrieb Mikel Maron:
>> But this thread is from Facebook trying to change that. To side step
>> imports.
> No they're not. It's a couple sections in a blog post that is being wildly
> misinterpreted.
Today's blog posts are the press releases of past years. It would have
Am 12.03.2020 um 16:06 schrieb THEVENON Julien:
> Le jeudi 12 mars 2020 à 15:43:17 UTC+1, Simon Poole a écrit
> :
>
>> To use a completely different example: assume that you purchase a TV set
>> paid by monthly instalments and you default on them. In civilised countries
Am 12.03.2020 um 15:56 schrieb Pierre Béland:
> Mar. 12 2020 10 h 43 min UTC−4, Simon Poole wrote :
>
> > To use a completely different example: assume that you purchase
> a TV set paid by monthly instalments and you default on them. In
> civilised countries that doesn
seller needs to utilize the whatever tools are provided by
the legal system, totally regardless off how upset they are and how
righteous they might feel about their actions.
Simon
Am 12.03.2020 um 15:09 schrieb Martin Koppenhoefer:
> Am Do., 12. März 2020 um 11:50 Uhr schrieb Simon Poole <
Am 12.03.2020 um 10:58 schrieb Martin Koppenhoefer:
> Am Mi., 11. März 2020 um 17:21 Uhr schrieb Simon Poole <mailto:si...@poole.ch>>:
>
> I would be very very wary of doing anything that deliberately
> defaces a web site without consulting with a local (to the count
or
> likely to lead to a liability claim than just a blacked out map, but I
> would not mind at all to be enlightened.
>
> Joost
>
> Op wo 11 mrt. 2020 om 15:39 schreef Simon Poole <mailto:si...@poole.ch>>:
>
> As I wrote (conveniently ignored in the noise of the
Am 11.03.2020 um 15:48 schrieb Mateusz Konieczny via talk:
> Mar 11, 2020, 15:37 by si...@poole.ch:
>
> As I wrote (conveniently ignored in the noise of the vigilante
> rampage): "
>
> I guess that people were irritated by describing gentle reminder about
> license requirements
> using pej
Even if the ToU's could be lacking in detail, couldn't we simply
> change them? The final section talks about changes, which we seem to
> be able to just do when we want to.
>
> I would think the biggest challenge on OSMF side would be the workload
> for OWG/sysadmins.
&g
Just for the record:
Enforcing attribution for services that you are providing directly (aka
tiles in some form) only has a small overlap with the goals of the
attribution guideline, and the avenues open to you depend on your ToUs /
contracts with your users and the legal situation in the countrie
From a pedagogic point of view I would consider that suboptimal, no to
mention that it would be endless.
For anybody that is going to contribute more than once (and iDs tutorial
does a good job of guiding through that), we want them to learn the
basic concepts of OSM and enable them to extend that
Am 19.02.2020 um 14:24 schrieb Christoph Hormann:
> In this case the statement that "small maps or multiple data sources"
> are the only cases where the document does not require visible
> attribution is wrong. For example it is later stated that visible
> attribution is not required if "there
Am 20.02.2020 um 11:34 schrieb Christoph Hormann:
> What you don't seem to understand is that there is nothing in the ODbL
> that allows the conclusion that for OSM data use on certain devices
> there is a *lesser* requirement for making the user aware of the use of
> OSM data than on others (b
Am 20.02.2020 um 11:19 schrieb Christian Quest:
>
> - the 10.000m2 limit, this is completely artificial
>
>
Artificial "yes", but the main thing is that it is small enough to
ensure that it will essentially never be a substantial extract, on the
other hand large enough that you can cover the locat
Folks, I was being a bit tongue in cheek, obviously the point didn't get
across. I apologize and re-state:
For many legal and marketing reasons providing attribution to "OSM" is
not something that is likely ever going to be supported or recommended
by the OSMF as sufficient.
This is nothing new a
Am 19.02.2020 um 20:17 schrieb Mateusz Konieczny via talk:
> 19 Feb 2020, 17:22 by dieterdre...@gmail.com:
>
> But I stick to the comment that 500px are far too many (=1000
> actual retina pixels or 1500 px on a retina@3).
>
> Yes, you may easily fit at least "© OSM"
> with link in such s
I believe there is actually a small issue with the definition here, as
there are two conflicting DIP definitions in use (one pixel on mobile
devices ~160 DPI vs one pixel for CSS 96 DPI), we need to state what we
are using.
Simon
Am 19.02.2020 um 17:22 schrieb Martin Koppenhoefer:
>
> sent from a
Am 19.02.2020 um 15:59 schrieb Martin Koppenhoefer:
> ..
> Imho we should not differentiate between mobile and desktop devices:
> either there is sufficient space and attribution should be permanent,
> or there isn’t and it is ok you have to click somewhere to see it. The
> constraints/conditions
.
> That article is unintelligible to me. Too many jargon terms. But I
> will note that "Slippery slope" is a logical fallacy, whether you use
> it to argue for stronger or weaker license enforcement and terms.
> https://yourlogicalfallacyis.com/slippery-slope
>
> - Joseph Ei
Am 19.02.2020 um 15:02 schrieb Frederik Ramm:
>
> In my mind I always ask the question: How essential was OSM for what is
> being done? How much of your hike remains if you remove OSM from the
> picture? How much of a trained AI remains if you remove OSM from the
> picture?
Assuming "essential" d
Am 19.02.2020 um 14:40 schrieb Joseph Eisenberg:
>> IMHO attribution should always be required 1. on the map 2. in high contrast
> Agreed.
>
> The main problem is that mobile devices, which are by far the most
> common ways of accessing maps around the world, are only required to
> provide attrib
Am 19.02.2020 um 13:50 schrieb Frederik Ramm:
> ...
> I acknowledge Kathleen Lu's recent remark about the ODbL being very
> clear on a derived product having to "contain" OSM in some way which
> would not be the case here; but I think this calls for working on ODbL
> 1.1 to rectify the issue, rath
The LWG has now integrated feedback from the initial airing in August
last year, from a total of three sessions at SOTM-US and SOTM in
Heidelberg, feedback from the OSMF board and from the wider OSM community.
Barring any major late developing issues, we intend to forward this to
the OSMF board fo
Am 17.02.2020 um 23:42 schrieb Yves:
> ..
> ... or worse, not using the brand at all on their maps for the same goal!
> Yves
>
Actually no, and I'm fairly sure that is the "BIG MISUNDERSTANDING".
If somebody doesn't provide sufficient attribution that doesn't run
away, and we can, for all pr
In no particular role, specifically no official OSMF one:
Can't we resolve this by moving the logo and potentially other ones to
an explicit category:
"Fun, parody and other, not totally serious, remixes of the OSM logo,
not endorsed by anybody"
With a different hat on: it would be really nice i
We are talking literally about a one command "pipeline" that already does
everything right and consumes 1% of the volume of a weekly download of the
planet.
Not to mention that you get a daily (or whatever you want) updated planet out
of it that contains a defined set of diffs (contrary to the
A couple of general points first:
- nobody "owns" their OSM data in any larger OSM community your data
will be changed by other mappers, and sometimes they will be wrong and
sometimes you,
- good comments and source tags are your friend, indicating how the data
was sourced is key to enabling othe
It's not quite the same thing as uncertainty in the datum itself.
Crust movements simply lead to things being somewhere else relative to a
global datum (aka they have moved), so a new measurement of the position
for the same object would return the correct current position and
theoretically if the
Thus is a slightly tricky subject and it is not going away.
For another aspect of it see
https://www.openstreetmap.org/user/StephaneP/diary/390290
Essentially in some cases we are using imagery that isn't actually using
WGS84 as if it was (fsvo of WGS84 as you correctly point out) and we
currentl
Am 08.11.2019 um 13:19 schrieb marc marc:
> Hello,
>
> Simon Poole :
>> The issue with addresses is definitely not due to a lack of tools
>> for OSM contributors. For example
>> https://regio-osm.de/hausnummerauswertung/anzeige_dynamisch.html?land=Schweiz&lon=8.7
Due to a change in the data format provided by the Osmose API, if you
have Osmose enabled (the default), you will experience a crash when
trying to download an area since yesterday.
While I've built a new version that handles the issue (this is simply a
crash avoidance measure, but doesn't address
Just as a further data point for the discussion: we are currently adding
roughly 10'000'000 addresses per year relatively constant since 2013,
with some exceptions due to imports (mainly NL in 2014 I believe).
signature.asc
Description: OpenPGP digital signature
The issue with addresses is definitely not due to a lack of tools for
OSM contributors. For example
https://regio-osm.de/hausnummerauswertung/anzeige_dynamisch.html?land=Schweiz&lon=8.71423&lat=47.05777&zoom=8&layers=B
which covers essentially all the analytics needed for comparison with
open d
The clause is mainly a consequence of the relevant GDPR rules and at the
time (not sure why we are having this discussion after the fact) we
spent a lot of time investigating what potential routes there could be
to working around this, but nobody came up with a workable solution.
Simon
Am 05.11.
Am 04.11.2019 um 12:57 schrieb Martin Koppenhoefer:
> Am Mo., 4. Nov. 2019 um 12:20 Uhr schrieb Simon Poole <mailto:si...@poole.ch>>:
>
> https://wiki.osmfoundation.org/wiki/Terms_of_Use#II._Privacy requires
> you to keep your contact information (which is
Am 04.11.2019 um 10:03 schrieb Maarten Deen:
> On 2019-11-04 09:28, Simon Poole wrote:
>> Am 03.11.2019 um 23:08 schrieb Martin Koppenhoefer:
>>> ...
>>> it depends from whom you hide, but generally you should not use a
>>> traceable email account if you want t
Am 03.11.2019 um 23:08 schrieb Martin Koppenhoefer:
> ...
> it depends from whom you hide, but generally you should not use a traceable
> email account if you want to remain anonymous. Using Google would seem like a
> total no-go (they are even reserving the right to read your emails). Use a
>
The problem with this thread is that it is conflating different (but a
bit related) things.
- missing or less than perfect attribution,
- corporate messaging about OpenStreetMap (or more the lack of it).
As to the first point in general we are just arguing about the form, not
the principle. We h
Thanks.
BTW I'm not saying that it is always clear when a "good idea" is
actually controversial or that you and Quincy are not subject to
multiple forces pulling or pushing in opposite directions, but the only
solution can be to escalate such issues to a wider audience before
implementation, when
nd the actual changes and
not around your behaviour which is what in the end is causing the high
tension.
Simon
>
> Bryan
>
>
>
>> On Sep 10, 2019, at 9:55 AM, Simon Poole wrote:
>>
>> Roland
>>
>> I can't help noticing that you are tiptoeing a
Roland
I can't help noticing that you are tiptoeing a bit around the actual
issue which started the whole discussion: unilateral changes by the iD
maintainers (everybody else doesn't have enough leverage to enforce
their position, so it is not me specifically picking on them, it is
simply a conseq
Am 09.09.2019 um 14:16 schrieb Christoph Hormann:
> On Monday 09 September 2019, Simon Poole wrote:
>>> And what happens if one of the data sources has a hard visible
>>> attribution requirement without the OSMF 'attribution light'
>>> liberty? As you
t odds with the ODbL),
and last, but not least, that the attribution guideline when it is
finalised is clearer than the current guidance and helps us massively
reduce unattributed use of OSM data.
Simon
Am 09.09.2019 um 14:14 schrieb Christoph Hormann:
> On Monday 09 September 2019, Simon
Just as a general comment and data point on the "the OSMF is scumbling
to commercial interests and throwing the licence out of the window"
narrative.
Ever noticed that while there are lots and lots of sites of all kinds
that use OSM derived base maps and the road network for routing, there
is esse
Am 09.09.2019 um 12:08 schrieb Christoph Hormann:
>
> Existing guidelines allow a lot of things that are clearly not allowed
> by the ODbL itself in terms of share-alike (like the regional cuts
> concept for example).
That statement is completely wrong. What is correct is that the
limitation
as required by the licence can be provided or not. I should
note that this is a hypothetical, Facebook doesn't display a logo on the
small inset maps nor on the larger popup maps on their website.
Simon
>
> - Joseph Eisenberg
>
> On 9/9/19, Simon Poole wrote:
>> To illustrate
on to OSM of
all sources used does not do that.
Simon
> -Joseph Eisenberg
>
> (Disclosure: Just a volunteer contributor as a mapper and at
> Openstreetmap-carto, I don't have any financial interest in this
> project, nor will the copyright policy directly affect me, except when
>
To illustrate where this discussion has gone awry please consider a
rendering using 10 data sources all licensed on ODbL terms (in real life
it is not uncommon to have multiple dozens of different sources, so 10
is not a high number). The ODbL does not, nor does any other open
licence, intend for
Nobody is even remotely suggesting that use OpenStreetMap data can be
used without attribution (claims that that is the case lead me to
believe that some haven't actually read the document in question).
The discussion is solely about the practicalities of where to put the
attribution when multipl
Am 08.09.2019 um 23:52 schrieb Christoph Hormann:
> On Sunday 08 September 2019, Clifford Snow wrote:
>> Christoph,
>> What would you recommend and how can it be implemented and tested to
>> insure compliance with the license? How does the user of OSM data
>> figure out what data is counted in the
Am 08.09.2019 um 20:37 schrieb Christoph Hormann:
> On Sunday 08 September 2019, Simon Poole wrote:
>> I think you are confusing potentially extractable information with
>> actual data. For example satellite imagery may have a potentially
>> high information content that coul
Am 08.09.2019 um 19:39 schrieb Christoph Hormann:
> On Sunday 08 September 2019, Simon Poole wrote:
>> /If OpenStreetMap is not the largest data provider for the visible
>> map rendering, attribution with other sources on a separate page that
>> is visible after user inte
text which however applies to the suggested
50% rule too.
Simon
Am 08.09.2019 um 16:38 schrieb Simon Poole:
>
> I don't quite follow your argument here. According to the draft
> guideline if a majority of the data displayed is derived from OSM,
> then attribution needs to be display
ces and are not complying with ODbL by not showing
> the license.
> Seen multiple maps by their clients and they show data "copyright l.map"
>
> I have confirmed with multiple contributors that largely the data used
> is OSM and it's around a year old dump of the planet
1 - 100 of 647 matches
Mail list logo
