On 04.08.2014, at 18:04 , Adrian Custer <[email protected]> wrote: > On 8/4/14 12:09 PM, Felix Baumann wrote: >> current content of the json file: >> {"tiles_url": "https://d17pt8qph6ncyq.cloudfront.net/tiles/"} > > Oops, no, this is the low accuracy point cloud data. Interesting, but not > what I want; I'd forgotten about that layer. > >> I don't think this is documented anywhere though >> @hannosch are you planning to add a page to the API documentation about >> this or is it listed elsewhere?
The “dot cloud” consists of map tiles generated and hosted by Mozilla. I’d consider these tiles to be public domain data and they don't need any copyright information. As Felix mentioned, there’s a map.json file that contains the current base url for those tiles. It’s currently not an official API, and only used by MozStumbler. If there is interest from a second project to use that tile layer, I can make this a public and documented API. >> for the OSM map MozStumbler uses Mapbox as a provider (see about page) > > **************************************************************** > Proxying or redistributing maps served from Mapbox is prohibited. Maps may be > cached on consumer devices (laptops, smartphones, tablets) for offline use, > however, each device must populate its cache using direct requests to Mapbox > and content from a cache may only be consumed by a single end-user. Further > redistribution from a cache is prohibited. Scraping or any mass download by a > single user for purposes other than offline caching is prohibited. > **************************************************************** > > SO UNFORTUNATELY YOUR ANSWER TO 1 DOES NOT SEEM TO BE CORRECT. WE CAN NOT > REUSE THE TILES FOR ANYTHING OTHER THAN A USER CACHE. Oh well, I'll have to > wait until I can build the downloading into the app to use any of these tiles. You are correct. Mapbox limits what we can do with the image tiles they serve. For example we cannot download and proxy those image tiles, nor can we combine the base layer + dot cloud + labels layer into a single png on our end, even though that would make a lot of sense and allow us to serve one png instead of three for every tile area. >From my point of view, as Mozilla we want to use our commercial mapbox >contract only in apps and webpages that we publish ourselves. Primarily >because we need some way to ensure that the map tiles are only used for the >intended purpose. We specifically don’t want to get into the business of hosting the world base map, as that’s an area where there is already a wide variety of choice out there, both in terms of hosting map tiles yourself as well as different vendors, for example http://switch2osm.org/providers/ In an ideal world, there would be a HTML5 “map” element, which would allow you to render a map and let the operating system handle the fetching and offline caching of map tiles. And instead of each app developer, each OS or user could choose the base map provider they wanted. But unfortunately we aren’t there yet. > How does MozStumbler define its style for the street background layer? > > It might be useful for stumbling apps to share a common map style for some > continuity across platforms. It may be that this does not work design wise > but it would be nice to have the style definition anyhow in case it did. The map style is based on Mozilla’s corporate identity and style guide (https://www.mozilla.org/en-US/styleguide/websites/community/overview/). We currently don’t follow the style guide for the stumbling app, but we do for the website. I’d leave it to each app, if they want to identify themselves as part of the Mozilla community, or if they want to retain their own visual style. Hanno _______________________________________________ dev-geolocation mailing list [email protected] https://lists.mozilla.org/listinfo/dev-geolocation
