JA:OSM2World

この記事は翻訳記事ですが、翻訳が不完全であり、抜けや誤り、未翻訳の部分があります。
英語版の記事の内容が分かる方は、翻訳の完成にご協力ください。このウィキの翻訳方法についての説明をお読みください。
現時点では、誰もこの記事の翻訳に取り組んでいないようですので、あなたが取り組めます。

OSM2World

作者：	Tobias Knerr and other contributors
ライセンス：	GNU Lesser General Public License (無償)
動作環境：	Windows、 Linux および macOS
版数：	0.2.0 (2019-06-23)
言語：	英語
ウェブサイト：	http://osm2world.org
ソースコード：	https://code.launchpad.net/osm2world
プログラミング言語：	Java
Creates a 3D model of the world from OSM data.

OSM2World (osm2world.org) は、オープンストリートマップのデータを3Dモデルに変換するコンバータです。作成された3Dモデルは他のフォーマットに出力することができます。

出力フォーマット

現在のところ, Wavefront .obj ファイル, POVRay raytracer 用の .pov ファイル, JOGL (OpenGL bindings for Java) を使った直接出力，JOGL 出力による .png 画像の生成などがサポートされています。必要なら他のフォーマットを追加することができます。

OSM2World の使い方

POVRay rendering of OSM2World scene

インストール

OSM2World はJRE(Java Runtime Environment) 1.6 以降を必要とします。あなたが JOSM を利用しているなら, あなたはすでにJRE1.6以降を持っています。

Javaを設定したら、osm2world.org/download のサイトでZIPファイルをダウンロードして、任意のフォルダに解凍します。

GUI操作

お使いのシステムに合ったバッチ／スクリプトを使ってコマンドラインから OSM2World を実行させます。するとＯＳＭデータファイルを開いてモデリング操作を行うことができます。

左マウスボタンでカメラ位置を移動
右マウスボタンでカメラの向き回転
マウスホイールでカメラの地面からの遠近を変更

キーボード操作でも代替可能です。さまざまなデバッグレイヤーを表示させることができ，.png，.pov，.obj に出力することが可能です。Be warned that the visualization is low quality and rather performance hungry at the moment, it primarily serves debugging purposes.

コマンドライン操作

This is a short documentation of the OSM2World command line. Please understand that the command line syntax is not yet stable and is likely to change in the future.

入力と出力

Result of the PNG export example

-i/--input <file> .osm, .osm.gz, .osm.bz2 or .osm.pbf input file
-o/--output <file> ... one or more output files. Filename extensions determine output file format. Available are .obj, .pov and .png files.
--resolution <horiz_res>,<vert_res> size in pixels for resolution-dependent outputs (.png)

カメラ

Defining a camera and projection for viewing the generated scene is required for .png output. It is optional (but recommended) for .pov files. You can either use orthographic or perspective projection. The available parameters for defining the camera depend on this choice.

Orthographic view:

--oview.angle <angle_deg> downwards angle of orthographic view in degrees; defaults to 30. Only works for angles > 0° and < 90°.
--oview.from <N/E/S/W> cardinal direction from which the orthographic view is rendered; defaults to south (S)
there are two alternatives for defining the bounds of the rectangle (in the elevation=0 plane) that is projected onto the viewing plane:
- --oview.bbox <lat>,<lon> <lat>,<lon> ... list of coordinates; the closest bounds containing all these coordinates will be used
- --oview.tiles <zoom>,<tileX>,<tileY> ... one or more tiles (defined using zoom level and x/y coordinate); the closest bounds containing all these tiles will be used

Perspective view:

--pview.pos <lat>,<lon>,<ele> camera position for perspective view
--pview.lookAt <lat>,<lon>,<ele> look-at for perspective view
--pview.aspect <value> aspect ratio (width / height) for perspective view; defaults to aspect ratio of resolution
--pview.fovy <angle_deg> vertical field of view angle for perspective view, in degrees; defaults to 45.

Logging

--performancePrint prints execution times to the command line after each phase of conversion
--performanceTable <file> appends execution times to a file after the conversion, formatted as a line of a plaintext table

Other parameters

Example for alternative color scheme using the --config parameter

--config <file> properties file with additional parameters (see OSM2World/Configuration file). Can be used for both the graphical and command line interfaces.
--gui starts the #Graphical interface
--help prints a short description of the available command line parameters
--version prints the current version of OSM2World

If you use --gui, --help or --version, OSM2World will not perform a conversion - it will execute this single action instead.

Parameter files

--parameterFile <file> a file containing one set of parameters per line.

If you want to perform multiple conversions, you can write the parameters (without program name) into a file and pass it as an argument to OSM2World. Lines starting with # will be ignored.

The main advantage is that conversions will be grouped if possible - i.e. if they have the same --input and --config parameters. For example, you can quickly render the same data from different perspectives.

例

 ./osm2world -i example.osm -o image.png --pview.pos +50.2607,+10.965,+110.0 --pview.lookAt 50.2623367,10.9640632,0

Writes an OpenGL rendering of the 3D model generated from example.osm to image.png. The rendering uses a perspective projection, with the defined coordinates for camera position and look at.

 ./osm2world -i example.osm -o tileexample.pov

Creates a 3D model from example.osm and exports it to the POVRay file example.pov. The POVRay file will not contain a camera definition, so you have to set it manually before feeding example.pov to POVRay.

 ./osm2world -i example.osm -o tileexample.pov --oview.tiles 12,2186,1312 12,2186,1313

Creates a 3D model from example.osm and exports it to the POVRay file tileexample.pov. The POVRay file will also contain the necessary camera definition for an orthographic view. It will be chosen to show the smallest possible bounding box that includes the two tiles 2186,1312 and 2186,1313 (both zoom 12). The camera looks at that area from the south. No --oview.angle parameter is given, so it defaults to 30 degrees. This angle is particularly interesting as it means that two "normal" square tiles will fit exactly into one square orthographic tile (that's because sin(30°)=0.5).

Library interface

You can use OSM2World as a Java library. The preferred way to do this is by using the ConversionFacade class that wraps the whole conversion into a single method call. It lets you provide input data and set output targets. You can also choose which kinds of world objects you want to be created and provide fine-tuning parameters - or you can just stick to the defaults, of course. Have a look at the javadoc.

If you need more functionality, don't understand the code, etc., just ask!

Plans and limitations

OSM2World rendering featured on the front page in November 2011

Elevation data

Elevation calculation in OSM2World is currently very fragile and deactivated by default, but exists as an experimental option. The calculation is intended to use object attributes (such as incline=*, layer=*, tunnel=* and bridge=*) and absolute elevation (ele=*, either from OSM itself or converted from sources such as SRTM or OpenDEM).

Troubleshooting

It's recommended to load only small maps, especially using the graphical interface. There are several places in OSM2World where very inefficient algorithm placeholders are used.
If OSM2World runs out of RAM, you can edit the start scripts and raise the -Xmx parameter.
If you have any other questions, use the talk page or take part in relevant discussions in forums or mailing lists. You can also contact User:Tordanik directly.