|Software described on this page or in this section is unlikely to be compatible with API v0.6 deployed on April 20, 2009. If you have fixed the software, or concluded that this notice does not apply, remove it.|
If you are writing a new script, look at the [library], it contains functions to simplify many tasks. It also removes most of the distinction between different server versions.
- This script will import a planet.osm file into a database (mysql or postgresql). It can optionally only import the things within a bounding box, just exclude things within a bounding box. It can read from STDIN, or from a file, or download the latest planet.osm for you. If requested, can output the schema to use, or clean the database from a previous import.
- The postgres support has been updated for the 0.5 API, but the mysql part may need some tweaks for 0.5
- Sample use might be:
- ./planetosm-to-db.pl --dbtype pgsql --schema | psql -U osm -d osm
- ./planetosm-to-db.pl --dbtype pgsql Planet.osm
- This program checks an OSM file for ways with open/unconnected ends or it checks certain ways for intersections on the same layer where no common node is present. The checks can be customized in an XML file. Output is HTML with positions, ways, other information and of course links to OSM and Openstreetbugs so you can inspect and correct data.
- This script takes an osm file like planet.osm and runs some simple statistics. A user name has to be given and then file and user statistics about nodes, ways and relations are given based on the field "user".
- This program counts the numbers of nodes, ways and relations per user in a planet.osm file. Of course segments/parts can be used like germany.osm or hessen.osm. No history data is used. Just the field user in xml. Output is first general stats, then lists of users with numbers of nodes, ways and relations, unsorted. Then TOP lists are generated and displayed.
- This program calculates the center of a user's activity in a given osm file/area for all users. It uses the field user and builds the means of longitude and latitude for each user. This information is added to the original OSM file and can be fed to a renderer, i.e. KOSMOS. The file is written to STDOUT. Users are labeled light, medium and heavy according to contributed nodes. Limits can be edited in source file. Example output of KOSMOS see here: KOSMOS CenterUserActivity.png
- This takes a bounding box, and only outputs the parts of the planet.osm that are within it (much like the -bbox parameter to planetosm-to-db.pl). So, you can produce a mini planet.osm for just one area, without going via a database. Updated for 0.5
- Oh, and it reads from STDIN if you want it to, so you can do
bzcat planet-061023.osm.bz2 | planetosm-excerpt-area.pl -bbox 50,-2,60,1 | bzip > mini-planet.osm.bz2
- This script finds ways with certain tags on them, their segments and nodes, and nodes with certain tags on them. So, you could do an area excerpt for just the UK, then filter it through this to get all the railways and cities, then pass that straight to osmarender.
- It doesn't support STDIN, as it has to make multiple passes over the file, so you should probably do an area excerpt first. Updated for 0.5
|Imports and automated edits should only be carried out by those with experience and understanding of the way the OpenStreetMap community creates maps, and only with careful planning and consultation with the local community.
See Import/Guidelines and Automated Edits code of conduct for more information. Imports/automated edits which do not follow these guidelines might be reverted!
With this program you can read your tracks and filter them with different filters.
osmtrackfilter.pl [-d] [-v] [--out-osm] [--limit-area]
<File1.gps> [<File2.sav>,<File2.ns1>,...] Other options which might be useful:
- --man Complete documentation
- --out-raw-gpx: write a raw .gpx file after conversion from .nmea, .gps, ...
- --out-upload-gpx : write a reduced .gpx file
- --out-osm: write a .osm file for loading into JOSM
- --split-tracks: split Tracks if distance too long, speed too high, ...
- --filter-against-osm : throw out all tracksegments found already in osm
- --filter-dup-seg: throw out second time you drove a street
- --filter-reduce: reduce number of points. (for example: reduce long straight lines)
- --limit-area: use filter files to reduce area
- --filter-clew: clews are produced if you have your GPS standing still
- --filter-all: use filter files to reduce area
- --draw_filter_areas: draw the (--limit-area) areas into GPX file
- --generate_ways: try to guess way info(not working yet)
- --fake-gpx-date: write faked date into GPX
- --write-gpx-wpt: also include waypoints into GPX-file
- --stdin: read from stdin
- --stdout: write to stdout
The old perl script has been moved to a 'perl' subdirectory, and a new 'ruby' version has been added.
The old perl version is not a straightforward file converter, rather it performs an immediate upload of the data to the OpenStreetMap server. This no longer works. It is only compatible with OSM API version 0.3 (very old) In any case, immediate upload of the data to the OpenStreetMap server is kind of frowned upon these days. Better to convert to a .osm file to review prior to upload using JOSM or a bulk_upload.py In fact this script will perform downloads to check to see if it's likely that the object already exists in OSM. If it thinks it might, it'll report the likely match, and defer the upload.
The ruby version of the script is a straightforward file converter. It does not perform any checks on the data, and does not perform an upload, but it does output data which is ready to be uploaded. It is up to the user to decide whether this is appropriate, and this always be carried out in accordance with Import/Guidelines
This is a directory to include for all sorts of perl modules which might be useful for other osm-related Perl applications.
Stuff for downloading/mirroring planet.osm Files
The [library] also lives here.
Read/write GPX Files
Handle Track data-structure in memory. Copy one track to another, split tracks, ...
Stuff to read different Track formats.
Stuff for filtering Tracks and OSM Data.
Filter data for a given Area. For now the area can be specified as a bounding box or country/region name.