Mirrors/remote-jobs
2
0
Fork 0
mirror of https://github.com/remoteintech/remote-jobs synced 2024-12-27 12:53:09 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update mapbox.md

Browse source
This commit is contained in:
Matijs Brinkhuis 2015-10-18 10:22:29 +01:00
parent c454c31ac5
commit 5ca757c625
1 changed files with 31 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
company-profiles/mapbox.md
View file

@ -15,10 +15,40 @@ Mapbox is an open source company. We build our product with open source parts, w
## Region
We are located in DC, SF, Ayacucho, Bangalore and Berlin.
USA, Peru, India and Germany
## Company technologies
### Software
Our focus for releasing software as open source is on reusable, general-purpose parts. In many cases, this means modules, rather than applications. We distribute these modules for other developers to use on websites like [npm](https://www.npmjs.com/) and [PyPI](https://pypi.python.org/pypi). For instance, [rasterio](https://github.com/mapbox/rasterio) is a core part of our image processing pipeline that we make available for any Python programmer to use.
A minority of our software is closed-source:
* Software that connects server processes and is heavily dependent on our configuration. This is a prevalent category but tends to be very small, in terms of code.
* Software that packages up business workflows. Software highly specific to Mapbox’s product, tied into our design, and core to our competitive advantage is often kept closed. These projects are usually applications and servers composed of parts that we release as open source so that others can build from the same foundations.
### Standards
Standards make modern software possible by connecting modular parts into systems. Open formats are the groundwork of open data. Mapbox is built on open standards: we adopt existing specs like GeoJSON and author new standards for new purposes, like [MBTiles](https://github.com/mapbox/mbtiles-spec) and [GL Style Spec](https://github.com/mapbox/mapbox-gl-style-spec). We release them under [permissive licenses](http://creativecommons.org/licenses/by/3.0/us/) that enable everyone to freely implement them in products and software, and to improve upon them.
### Design
Design components that are **reusable, general purpose, and not explicitly tied to the Mapbox brand**, like [Maki](https://www.mapbox.com/maki/), make sense as open source. We also release templates that show how to use our tools, like those in [Guides](https://www.mapbox.com/guides/).
Most of our artwork is copyrighted and not placed under any open license. It’s tied to the Mapbox identity: reusing the Mapbox.com website style isn’t a use-case we want to support. The uniqueness and specificity of our style is important to how customers identify “oh, this is Mapbox”.
### Data
The vast majority of Mapbox’s data is in the open. Large sources include [OpenStreetMap](http://www.openstreetmap.org/), [USGS](http://www.usgs.gov/), [Landsat](http://landsat.usgs.gov/), [Natural Earth](http://www.naturalearthdata.com/), and [OpenAddresses](http://openaddresses.io/). We contribute to these sources, participate in their communities, and invest in tools that help improve them.
We also work extensively with proprietary sets of data that we buy: we legally can’t open these. Nor do we release heavily processed data. Processing data and delivering the final products has obvious and real costs: server infrastructure and bandwidth, as well as labor. Our ability to distill meaning out of raw material is a core part of our product.
## Office Locations
We are located in DC, SF, Ayacucho, Bangalore and Berlin.
## How to apply
Check the [job listings](https://www.mapbox.com/jobs/)