Osm2pgsql - Versionsgeschichte

Stefan: /* About */

2020-05-13T19:16:20Z

About

← Nächstältere Version		Version vom 13. Mai 2020, 19:16 Uhr
Zeile 10:		Zeile 10:
	osm2pgsql is mainly written for rendering data with data. So it only imports tags which are going to be useful for rendering. These tags are defined in the file 'default.style' ([http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.style svn], [http://trac.openstreetmap.org/browser/applications/utils/export/osm2pgsql/default.style trac]). It also manipulates data for mapnik (i.e. placing nodes in the centre of gravity of polygons).		osm2pgsql is mainly written for rendering data with data. So it only imports tags which are going to be useful for rendering. These tags are defined in the file 'default.style' ([http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.style svn], [http://trac.openstreetmap.org/browser/applications/utils/export/osm2pgsql/default.style trac]). It also manipulates data for mapnik (i.e. placing nodes in the centre of gravity of polygons).
	* [http://wiki.openstreetmap.org/wiki/Osm2pgsql osm2pgsql Homepage]		* [http://wiki.openstreetmap.org/wiki/Osm2pgsql osm2pgsql Homepage]
	* [~~http~~://~~trac~~.~~openstreetmap~~.~~org~~/~~browser~~/~~applications/utils/export~~/osm2pgsql osm2pgsql ~~Trac~~]		* [https://www.volkerschatz.com/net/osm/osm2pgsql-usage.html osm2pgsql usage from Volkerschatz]

	== Alternatives ==		== Alternatives ==

Stefan am 22. Oktober 2012 um 09:45 Uhr

2012-10-22T09:45:19Z

← Nächstältere Version		Version vom 22. Oktober 2012, 09:45 Uhr
Zeile 60:		Zeile 60:
	== Tipps & Tricks ==		== Tipps & Tricks ==

			=== Append mode ===
	If you want to add a new key but avoid re-importing the full database, you can add the key to osm2pgsql's style file, somehow generate an .osm file that contains only the objects that have this tag, wrap this .osm file into a "<osmChange><modify>...</modify></osmChange>" instead of "<osm>...</osm>" and throw it at osm2pgsql in append mode.		If you want to add a new key but avoid re-importing the full database, you can add the key to osm2pgsql's style file, somehow generate an .osm file that contains only the objects that have this tag, wrap this .osm file into a "<osmChange><modify>...</modify></osmChange>" instead of "<osm>...</osm>" and throw it at osm2pgsql in append mode.

			=== Differential Update ===
			The problem is that; despite the osm2pgsql -b option, the bounding box is ignored and the full diff file is added to the database;

			Possible solution:
			# Make a copy of the extract.
			# Apply the update to the copy (using osmosis)
			# Clip the copy using the Vietnam clip bounds file (using osmosis?)
			# Make a diff between the original and the copy (using osmosis?)
			# Apply the diff to the PostGIS database (osm2pgsql)
			# Finally make the copy the new original for next update

Stefan: /* Alternatives */

2012-07-16T20:47:33Z

Alternatives

← Nächstältere Version		Version vom 16. Juli 2012, 20:47 Uhr
Zeile 13:		Zeile 13:

	== Alternatives ==		== Alternatives ==
	Besides osm2pgsql there's also osmosis, osmium and imposm. osm2pgsql and imposm are geared towards creating useful geometry tables, whereas osmosis and osmium more geared towards truthfully representing a full OSM data set. They all have their advantages and disadvantages. osm2pgsql is the standard choice for most people making maps, with imposm gaining ground. Major difference between them is that osm2pgsql can do updates whereas imposm cannot, that means, it requires you to drop and reimport. imposm probably creates a richer table structure that is easier to understand.		Besides osm2pgsql there's also osmosis, osmium and imposm. osm2pgsql and imposm are geared towards creating useful geometry tables, whereas osmosis and osmium more geared towards truthfully representing a full OSM data set. They all have their advantages and disadvantages. osm2pgsql is the standard choice for most people making maps, with imposm gaining ground. Major difference between them is that osm2pgsql can do updates whereas imposm cannot, that means, it requires you to drop and reimport. imposm probably creates a richer table structure that is easier to understand. And there's also osmconvert together with osmfilter, which are fast (because of C++) in filtering PDF files.

	Be advised that any of the tools mentioned will take between one and several days to import a world-wide dataset even on a reasonably fast machine.		Be advised that any of the tools mentioned will take between one and several days to import a world-wide dataset even on a reasonably fast machine.

Stefan am 16. Juli 2012 um 20:08 Uhr

2012-07-16T20:08:15Z

← Nächstältere Version		Version vom 16. Juli 2012, 20:08 Uhr
Zeile 5:		Zeile 5:
	* [[PostGIS-Terminal]], [[OpenPOIMap]]		* [[PostGIS-Terminal]], [[OpenPOIMap]]
	* osmosis, osmium and imposm (and osm2gis).		* osmosis, osmium and imposm (and osm2gis).


	== About ==		== About ==

Stefan am 16. Juli 2012 um 20:08 Uhr

2012-07-16T20:08:02Z

← Nächstältere Version		Version vom 16. Juli 2012, 20:08 Uhr
Zeile 1:		Zeile 1:
	Well-known "OSM data to PostgreSQL/PostGIS database converter and loader" (Autor: jburgess777(at)googlemail.com).		Well-known "OSM data to PostgreSQL/PostGIS database converter and loader" (Autor: jburgess777(at)googlemail.com). We use osm2pgsql mainly to feed [[EOSMDBOne]] which in serves as a database for the [[PostGIS-Terminal]], [[OpenPOIMap]] und weitere (z.B. "AR for OSM").

	See also:		See also:
	* [[OSM-Technisches]] (Deutsch)		* [[OSM-Technisches]] (Deutsch)
			* [[PostGIS-Terminal]], [[OpenPOIMap]]
	~~We use osm2pgsql mainly to feed [[EOSMDBOne]] which in serves as a database for the~~ [[PostGIS-Terminal]], [[OpenPOIMap]] ~~und weitere~~ (~~z.B. "AR for OSM"~~).		* osmosis, osmium and imposm (and osm2gis).

	== About ==		== About ==

Stefan am 16. Juli 2012 um 20:07 Uhr

2012-07-16T20:07:08Z

← Nächstältere Version		Version vom 16. Juli 2012, 20:07 Uhr
Zeile 1:		Zeile 1:
	~~Einer der beliebtesten~~ "OSM~~-Daten zu~~ PostgreSQL/PostGIS~~-DB~~" ~~Converter und Loader.~~ (Autor: jburgess777(at)googlemail.com).		Well-known "OSM data to PostgreSQL/PostGIS database converter and loader" (Autor: jburgess777(at)googlemail.com).

	~~Siehe auch~~:		See also:
	* [[OSM-Technisches]]		* [[OSM-Technisches]] (Deutsch)
	* [[PostGIS-Terminal]]
	* [[EOSMDBOne]]

			We use osm2pgsql mainly to feed [[EOSMDBOne]] which in serves as a database for the [[PostGIS-Terminal]], [[OpenPOIMap]] und weitere (z.B. "AR for OSM").

			== About ==
	osm2pgsql is mainly written for rendering data with data. So it only imports tags which are going to be useful for rendering. These tags are defined in the file 'default.style' ([http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.style svn], [http://trac.openstreetmap.org/browser/applications/utils/export/osm2pgsql/default.style trac]). It also manipulates data for mapnik (i.e. placing nodes in the centre of gravity of polygons).		osm2pgsql is mainly written for rendering data with data. So it only imports tags which are going to be useful for rendering. These tags are defined in the file 'default.style' ([http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/default.style svn], [http://trac.openstreetmap.org/browser/applications/utils/export/osm2pgsql/default.style trac]). It also manipulates data for mapnik (i.e. placing nodes in the centre of gravity of polygons).
	* [http://wiki.openstreetmap.org/wiki/Osm2pgsql osm2pgsql Homepage]		* [http://wiki.openstreetmap.org/wiki/Osm2pgsql osm2pgsql Homepage]
	* [http://trac.openstreetmap.org/browser/applications/utils/export/osm2pgsql osm2pgsql Trac]		* [http://trac.openstreetmap.org/browser/applications/utils/export/osm2pgsql osm2pgsql Trac]

			== Alternatives ==
			Besides osm2pgsql there's also osmosis, osmium and imposm. osm2pgsql and imposm are geared towards creating useful geometry tables, whereas osmosis and osmium more geared towards truthfully representing a full OSM data set. They all have their advantages and disadvantages. osm2pgsql is the standard choice for most people making maps, with imposm gaining ground. Major difference between them is that osm2pgsql can do updates whereas imposm cannot, that means, it requires you to drop and reimport. imposm probably creates a richer table structure that is easier to understand.

			Be advised that any of the tools mentioned will take between one and several days to import a world-wide dataset even on a reasonably fast machine.

	== Installation ==		== Installation ==

Stefan: /* Tipps+Tricks */

2012-02-16T22:22:00Z

Tipps+Tricks

← Nächstältere Version		Version vom 16. Februar 2012, 22:22 Uhr
Zeile 51:		Zeile 51:


	== Tipps+Tricks ==		== Tipps & Tricks ==

	If you want to add a new key but avoid re-importing the full database, you can add the key to osm2pgsql's style file, somehow generate an .osm file that contains only the objects that have this tag, wrap this .osm file into a "<osmChange><modify>...</modify></osmChange>" instead of "<osm>...</osm>" and throw it at osm2pgsql in append mode.		If you want to add a new key but avoid re-importing the full database, you can add the key to osm2pgsql's style file, somehow generate an .osm file that contains only the objects that have this tag, wrap this .osm file into a "<osmChange><modify>...</modify></osmChange>" instead of "<osm>...</osm>" and throw it at osm2pgsql in append mode.

Stefan am 16. Februar 2012 um 22:21 Uhr

2012-02-16T22:21:40Z

← Nächstältere Version		Version vom 16. Februar 2012, 22:21 Uhr
Zeile 49:		Zeile 49:
	oder		oder
	node,way osm_version int4 linear		node,way osm_version int4 linear


			== Tipps+Tricks ==

			If you want to add a new key but avoid re-importing the full database, you can add the key to osm2pgsql's style file, somehow generate an .osm file that contains only the objects that have this tag, wrap this .osm file into a "<osmChange><modify>...</modify></osmChange>" instead of "<osm>...</osm>" and throw it at osm2pgsql in append mode.

Stefan: /* Output Database */

2011-11-15T15:56:50Z

Output Database

← Nächstältere Version		Version vom 15. November 2011, 15:56 Uhr
Zeile 40:		Zeile 40:
	** osm_polygon: with polygon geometry (one of the unique features of Osm2pgsql!)		** osm_polygon: with polygon geometry (one of the unique features of Osm2pgsql!)
	** osm_roads: a special table with polyline geometry		** osm_roads: a special table with polyline geometry

			== Style File ==

			Style File (Default.style):

			-x ...
			node,way osm_version int linear
			oder
			node,way osm_version int4 linear

Stefan: /* Output Database */

2011-07-24T00:02:51Z

Output Database

← Nächstältere Version		Version vom 24. Juli 2011, 00:02 Uhr
Zeile 38:		Zeile 38:
	** osm_point: with point geometry		** osm_point: with point geometry
	** osm_line: with polyline geometry		** osm_line: with polyline geometry
	** osm_polygon: with polygon geometry (one of the unique features of Osm2pgsql!		** osm_polygon: with polygon geometry (one of the unique features of Osm2pgsql!)
	** osm_roads: a special table with polyline geometry		** osm_roads: a special table with polyline geometry