The landing page has over a dozen demos and renders using OpenStreetMap data, but I see not a single attribution statement anywhere until I open an interactive map.
Even renders and pictures require attribution.
Even renders and pictures require attribution.
So if a journalist makes a screenshot of a website that uses Felt, they would have to have a text like ...
"Image courtesy of SomeSite with an image courtesy of Felt with an image courtesy of Mapbox with an image courtesy of OpenStreetMap?"
.... under the image?
> It has no real attribution when opened on a mobile or when browser window is resized to a smaller one.
By contrast, Mapbox ask for a credit as part of a commercial agreement, which by definition can be negotiated away. I guarantee if you call up Mapbox and offer them enough money, they’ll flex on their logo requirement. There is simply no legal way to do that with OSM.
Instructions unclear, I'm broke.
Money might not buy happiness but it buys an awful lot of power.
https://www.cnbc.com/2021/12/16/mcdonalds-settles-discrimina...
https://www.restaurantbusinessonline.com/operations/mcdonald...
https://www.aclu.org/press-releases/former-mcdonalds-workers...
The oldest of these is from end of last year.
Edit: tone down phrasing
It's real good, and a good example of big corporations sometimes backing off, however unwillingly.
There’s also little benefit to them, which makes it even more pointless.
That is of course more about journalistic standards and good practice. In terms of the law, IANAL but I don't think attribution is strictly required for Fair Use usage (e.g. reportage). Only for functional usage (e.g. providing maps to be used as maps).
I don't have a conclusion from this, and if you're going to use something that requires attribution you should attribute. Maybe we just need better ways of giving that attribution. It's certainly easier in an interactive medium, with hyperlinks and collapsable sections than on paper.
For practical functional applications, 3 layers seems high, and potentially a sign of over-engineering.
To get a little more technical about our hypothetical:
- I've used Mapbox in the past, and they included (at the time) a succint dual-attribution overlay for themselves and OSM as part of their APIs. It was well-designed and baked in (nothing for me to do).
- If I were to then take my own application and offer it as a service for others to embed:
1. There's a strong likelihood I'm offering a commercial service so attribution may not be required for my layer (provided service-charges covering white-labelling)
2. If I am requiring attribution, it might make sense for me to invest in direct OSM usage & cut out the Mapbox middleman.
3. If not, it certainly seems like my added layer would be the absolute extreme (and baking in a well-made 3-component attribution would be challenging but not insurmountable).
>Other than Your Content (as defined below), all Content displayed on the site or accessible through the Services, including text, images, maps, software or source code, are the property of Felt and/or third parties and are protected by United States and international intellectual property laws. Logos and product names appearing on or in connection with the Services are proprietary to Felt or our licensors. You may not remove any proprietary notices or product identification labels from the Services.
Small print about small print.