Ko:Develop
OpenStreetMap은 단지 오픈 데이터가 아닙니다. 오픈 소스이며 여러분이 도울수 있습니다!
OpenStreetMap에 참여할 수 있는 두 가지 주요 방법이 있습니다다:
- OpenStreetMap Platform 개발하기. 여기에는 OpenStreetMap.org 웹사이트와 관련 구성 요소 및 서비스가 포함됩니다.
- OpenStreetMap 사용하기. OpenStreetMap 데이터 및 서비스뿐만 아니라 커뮤니티의 소프트웨어 및 서비스를 사용하여 원하는 것을 만들 수 잇습니다.
|
OpenStreetMap Platform
|
개발을 위한 OpenStreetMap의 이용
|
Get in touch
If you have questions, ideas or just want to meet fellow developers, you can contact the OpenStreetMap development community by using channels listed below.
- IRC
- #osm-dev channel on the OFTC network
- Mailing Lists
How the pieces fit together
The code that runs openstreetmap.org is composed of independent components that work together to provide an API, Slippy Map, and other bits of functionality.
The Rails port is the Ruby on Rails application that powers openstreetmap.org; it's where OSM's pages and basic API originate. OpenStreetMap's data, "the planet", are stored in PostgreSQL with PostGIS, and rendered into pretty map tiles with Mapnik. The Slippy Map interface for those tiles — what lets you pan and zoom the map — is powered by Leaflet.
Internally, osm2pgsql and osmosis are essential infrastructure for converting OSM XML to PostGIS. They work with Planet.osm and other extracts, which let other sites use and distribute OSM data.
Users can add and modify OpenStreetMap data thanks to open-source editors like iD, Potlatch 2, and JOSM.
Deploy OpenStreetMap stack automatically using VM
Tile serving
Stubs and untested ideas
Background
There's plenty to know about OpenStreetMap's style of storing & modifying geodata that will help you get how things work. Review the XML schema, Data Primitives, and Downloading data if you want to work on data-related tasks.
Also, OpenStreetMap runs on a relatively small server deployment for its size - see our notes on server hardware for details. There are also API v0.6 mirrors and Dev and Test APIs which help with testing code that interacts with the OSM API.
How to get involved
Many of OpenStreetMap's projects use Git (mirror at GitHub), and so you can simply fork a repo and contribute changes.
For larger changes, you may want to get an account on a development server to do serious testing.
Main projects
The OSM website Rails Port (Ruby)
This does the UI and API for the site. The Rails port page has plenty of useful information for getting started. Design help is needed here: read Rails_port/UI for a quickstart guide for designers. New users can also review pull requests as practice for getting the Rails Port set up. You can also help by contributing translations.
- Code
- Report an issue on github or trac. For server, operational issues, see Contact#Systems administrators.
Search, geocoding Nominatim
PC 지도 에디터 JOSM (Java)
JOSM 은 OpenStreetMap editors의 가장 강력한 에디터중 하나입니다.
웹 지도 에디터 iD (Javascript)
iD OpenStreetMap의 최신에디터 입니다. Users can help by testing & reporting bugs, or tackling issues tagged good-first-issue.
웹 지도 에디터 Potlatch 2 (Actionscript)
Potlatch 2 was the default editor for new OpenStreetMap users. You can also help by contributing translations.
OSM.org의 기본 스타일
- 주요 문서: Standard tile layer
Other map styles are separate, please see on their wiki pages or look at contact/license footers in a map display.
OSM data processing swiss army knife Osmosis (Java)
Osmosis is our swiss army knife for processing OpenStreetMap data. Documentation and testing are especially welcome here.
OSM data importer for rendering or geocoding osm2pgsql (C)
osm2pgsql a powertool for importing OSM XML files into PostGIS databases. Documentation and testing are especially welcome here.
Slippy map library Leaflet (Javascript)
Provides the general slippy map interface. Javascript whizzes can help us make the home page's maps even faster.
Map rendering with Mapnik (C++)
The main backend for the rendering of the maps that are produced from OSM data.
Tile rendering system with Tirex (C++ and Perl)
- Original code from Geofabrik
- Forked code for OSM
- Report an issue on GitHub or track for OSM
See also Tirex/Development and Tirex/Internals
