GeoConverter

2008-06-24T10:55:03Z

Tbinna: /* How To... */

Diskussion:GeoConverter

2008-06-20T12:36:17Z

Tbinna: /* History */

== Projektmanagement ==

=== ToDos ===
*
* Zusätzliches (vorhandenes) Format: "MapInfo Interchange Format (.tab)"
* Erstaunlich, dass das funktioniert:
** => Nur .dbf? 19.03.2008 19:51 klmcmahan 168.236.43.132 conversion successful .dbf .mif L_COMM_INFO.dbf 1598
** => "e00"? 01.04.2008 18:53 natal 158.125.70.104 conversion succeeded .e00 .csv n/a n/a dividing_area.e00 134147

=== Bugs und kleinere Verbesserungen ===
* Wenn bei Shapefile-Quellformat eine Metadaten-XML-Datei dabei ist (z.B. Bahnhoefe.shp.xml), dann funktioniert's nicht.
* Mehr Angaben im Log-File im Fehlerfall.
* Hintergrund grau statt schwarz => freundlicher?
* Anzeige "Failed" bei oder neben Schritt 3 anstelle oben.
* Möglichkeit, gleich nach "...succeeded" und v.a. nach "...failed" eine Mitteilung abzuschicken (intern per Mail). Dabei ev. eine 'Job-Nr.' mitgeben und diese auch ins Log schreiben. So kann man die Parameter nachvollziehen (ev. auch die Dateien??).

ERROR messages:
* Source SRS missing. Conversion always includes a source and a target SRS given.

=== Erweiterungsideen ===
* .kmz verarbeiten (KML mit Zip komprimiert). Sollte einfach mit (un-)zip weiterverarbeitbar sein (die Haupt-Datei drin hat dann oft denselben Namen 'google.kml' - aber nicht immer).
* .tar.gz verarbeiten?
* Zusatz-Option 'Angabe Ausschnitt' (BBox-Feld: minX, minY, maxX, maxY)
* Verwendeter OGR2OGR-Aufruf in eine Batch-Datei mit-verpacken (mit Dateinamen ohne Pfad).
* Neues Zielformat 'Statistics (.txt)'. Ruft intern "ogrinfo <options> <inputfile_directory>" auf und gibt eine Textdatei aus.
* Formate:
** DGN-Reader und DGN-Writer dazufügen/aktivieren
** [[OSM]]-Reader implementieren (mit Hilfe xslt/Java-Aufruf, der GML erzeugt, das dann weiterverarbeitet werden kann)
** Ergänzen der Converter-Checklist durch dasselbe Zielformat wie das Quellformat.
** (DXF Reader/Writer fehlt leider in OGR)

Anzeige einer Statistik mit Konvertierungen.
Statistics (2007-01-13, 55 Datasets)
Top 10 Source Formats Sum Succ. Top 10 Target Formats Sum Succ.
1. INTERLIS 1 (>) 33x (30x) 1. ESRI Shapefile (>) 39x (30x)
2. ESRI Shapefile (v) 11x (..x) 2. KML (^) 5x (..x)
3. GPX (^) 1x (..x) 3. GPX (^) 1x (..x)

== History ==
* Redesign des Programmcodes -> DONE, 20.06.08
* Upload und konvertieren von OSM-Dateien -> DONE, 20.06.08
* Ergänzen der target file format-Auswahlliste mit allen notwendigen Dateien (z.B. ".shp, .shx, .dbf"). -> DONE, 08.04.08
* CRS anstelle SRS -> DONE, 08.04.08
* Anfang des log.txt löschen bis zum Punkt, wo CRS geloggt werden und Delimiter auf ";" stellen -> DONE, 08.04.08
* "MapInfo Interchange Format" anstelle "Mapinfo File". -> DONE, 08.04.08
* Rechtschreibefehler korrigieren (Refrence -> Reference) -> DONE, 28.03.08
* SRS loggen -> DONE, 28.03.08
* Führen eines Logs für spätere Statistik-Auswertung z.B. mit den Angaben: Username, User-IP, Datum/Zeit, Successfull (oder nicht), Quellformat, Zielformat, Quelldatei-Name, Quelldatei-Grösse (vgl. unten). -> DONE
* Zusatz-Option 'Koordinaten-Transformation':
** Angabe der Koordinaten-Transformation des Zielformats (-t_srs-Option). -> DONE
** KML-Writer soll fix Parameter -t_srs EPSG:4326 erhalten (Google Earth erwartet immer WGS84). Dann muss aber auch das Quell-SRS bekannt sein, sonst wird EPSG:4326 angenommen (sonst gibt's Fehler). -> DONE
* Formate: KML-Reader einbauen/aktivieren -> DONE

== Feature Requests, Bug Reports and Suggestions ==

Please put your feature requests, bug reports and suggestions here.

GeoConverter

2008-06-20T12:28:28Z

Tbinna: /* How To... */

[[Bild:GeoConverter_V1.png|thumb|right]]
GeoConverter - Free Online Geospatial Data Converter. Reads and writes several [[GIS]] vector file formats based on the famous [[OGR]] tools.

Homepage: '''http://geoconverter.hsr.ch'''

== About ==

GeoConverter is a static ('1:1') geospatial file data format converter and coordinate transformer. It is running as a webapplication and designed to be used by technical users who casually have to convert [[GIS]] and [[GPS]] data.

Possible source GIS vector file formats are mostly the same as the target file formats (see the FAQ below).

GeoConverter is based on the FWTools (GDAL 1.5.0b1, FWTools 2.0.2, released 2007/12/05), especially on OGR2OGR as documented in the [[OGR]] pages.

It's possible that in the near future GeoConverter get's an additional machine-machine interface and this would be a typical Web Processing Service ([[WPS]]).

== Rules for uploading files ==
This section explains the rules for uploading files to GeoConverter:
* Let 'source file format' be the file(s) to be uploaded and let 'target file format' be the file you will download.
* We assume that you deliver '''one''' dataset at a time.
* There are formats, like Shapefile, Mapinfo or INTERLIS 2, which consist of more than one file. Before uploading, they ''must'' be packed into a zip file (use e.g. gzip or PKZIP).
* You ''may'' zip your file before uploading for those formats which consist of a single file, like GPX and KML.
* If you choose CSV as source file format to upload follow the special formatting described below.
* If you convert data to INTERLIS 2 (.xml), make sure you provide also an INTERLIS (target) model file (.ili).

If no coordinate reference system (CRS) parameters are given the conversion maintains it. Note that KML always defaults to WGS84 - EPSG 4326, the GPS system - which means that if a source dataset in a local CRS is given you ''must'' indicate the source CRS and set the target CRS to (EPSG:) 4326.

== FAQ ==

These are ''Frequently Asked Questions'' (FAQ) for the GeoConverter documentation Wiki.

=== When conversion fails... ===

;What to do when SHP conversion fails?: Make sure you provide an accompanying .DBF and .SHX files and make a ZIP file with all three.

;What to do when MIF conversion fails?: Make sure you provide an accompanying .MID file and make a ZIP file with both.

;GML or GPX fail to convert, what to do?: These formats are [[XML]] file formats. XML is a human readable ASCII format with a very rigid structure and encoding. There are readers which validate the input and even complain about the character encoding. Often when there is an encoding called 'UTF-8' but the file comes as Windows 'ANSI'; so you have to look for an editor or a tool which writes a proper UTF-8 encoded file.

;What to do when converting to KML succeeds but Google Earth displays nothing?: First, KML is an XML dialect so check the question about GML and GPX above. Second, KML assumes the GPS coordinate system WGS84. So check if you have filled in both numbers in the fields "Source EPSG no.:" and "Target EPSG no.:". Search for these EPSG numbers in [http://www.spatialreference.org spatialreference.org].

;What to do in general when the conversion fails?:
# Check the log file provided with the error.
# Check, if your input file is not bigger than 100 MB. If you have not uploaded a zip file, zip it and try again.
# Read the FAQ and check the rules given here.
# Try out some sample files (see below)
# Finally, if the problem persists consider dropping us a mail.

;Where can one submit bugs and feature requests?: [http://gis.hsr.ch/wiki/Diskussion:GeoConverter Here] at the bottom of the Wiki discussion page.

=== How To... ===

;Which file formats are supported by this webapplication?: These formats are supported for writing and also for reading. Try them out with the sample data below:
* Comma Separated Value (.csv/(.csvt))
* GPX (.gpx)
* Geographic Markup Language (.gml)
* INTERLIS 1-Transfer Format (.itf/.ili)
* INTERLIS 2-XML Transfer Format (.xml/.ili)
* Keyhole Markup Language (.kml)
* Mapinfo File (.mif/.mid)
* Shapefile (.shp/.dbf/.shx)
* OSM (.osm) -> reading only!

;What is WKT?: Well Known Text, i.e. geometry values in string representation. Typical examples are POINT(1 1), LINESTRING(1 1, 2 2, 3 3) and POLYGON((1 1, 2 2), (2 2, 3 3), (1 1)). See [[WKT]] for more information.

;How do I create an INTERLIS file (.ili) when converting to INTERLIS 2?: See documentation and/or contact us. Future INTERLIS 2 drivers won’t need this parameter for simple cases whereas professional conversion will need a full-fledged and configurable converter (see documentation page).

=== About Background / Terms of Use ===

;What is a layer and a dataset?: An OGR feature object encapsulates the values of a whole feature, that is a geometry and a set of attributes. A layer object is a collection of features (objects) of the same feature class. A data source represents a file or a database containing one or more layer objects. Note that 'layer' definition and 'feature class' definition are essentially the same. Layers have a reference to a spatial coordinate reference system (CRS). See also [[OGR]] for an explanation in german.

;I see GPX but can't find any other GPS file formats?: GPS file formats like NMEA or Garmin (.gdb) are converted best through existing software. See [[GPS-Software]] for more information about this topic.

;I miss DXF and other CAD file formats?: Microstation's DGN (up to version 7) is supported by OGR but not implemeted yet in GeoConverter. DXF unfortunately does not yet exist as a suitable driver for OGR altough some free libraries exist - so, sponsors are welcome!

;Why do I have to register before using this service? What are you doing with my personal information like my e-mail?: We ask for your e-mail and name mainly because of the tedious fight against spam! As a side effect you become part of the [[GISpunkt HSR]] community where we send information mails sometimes. These mails are currently sent every other month and will never exceed once a week. Your e-mail will never be used for other purposes whatsoever and we will never give away your personal data.

;What does GeoConverter mean?: GeoConverter means "Online ''Geo''spatial Data Format ''Converter''".

;Is this webapplication free?: Yes, GeoConverter is a free webapplication and it will remain free as long as this service is not abused by daily business cases (e.g. as long as bandwidth remains low).

;Is GeoConverter a competitor to other converter software?: There are quite some professional products around like FME, igtools or InterlisStudio. These products offer more than a straight forward and static 1:1 conversion. They can be manually configured and often support more file formats. So: No! GeoConverter is not meant as a competition but as an enabler of GIS and geospatial data!

;Who runs this webapplication?: This user service is brought to you by [[GISpunkt HSR]]. It is an experimental project without any warranty.

;What are the Terms of Service of the GeoConverter?: See [http://gis.hsr.ch/geoconverter/index.php?section=tos here].

;Can these conversions also be run on a local PC?: Yes, if you can install some software on your PC: We use OGR2OGR which is delivered among others as FWTools and you can run most conversions locally as it was designed for initially. See [[OGR]] for more information about this.

== CSV source format used in GeoConverter ==

GeoConverter uses the 'Comma Separated Values' ([[CSV]]) reader/writer from [[OGR]]. The OGR CSV reader/writer allows to encode geometry by using [[WKT]] as attribute values. Unfortunately, CSV leaves many decisions open and most annoying is that the (german) MS Excel is a non-conformant CSV writer. When trying to upload CSV from MS Excel some re-formatting is needed before hand, e.g. replacing semi-colons with colons, removing double quotes etc.

These are the rules in order to successfully upload CSV file with geometry:
* Use comma as field separator/delimiter
* The first line must be a column header (upper or lower case).
* The column header must contain one of two possibilities as column names:
** "LON" followed by "LAT" and a "NAME" attribute. LON/LAT are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "LAT" followed by "LON" and a "NAME" attribute. LAT/LON are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "longitude" followed by "latitude" and a "NAME" attribute. longitude/latitude are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "latitude" followed by "longitude" and a "NAME" attribute. latitude /longitude are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "ID, NAME, THEGEOM". THEGEOM attributes (alternate name 'OGR_GEOM_WKT') have to be formatted as [[WKT]], i.e. with no comma but including the parantheses.
* There can be more attributes than these three.

Examples (see [[HowTo_OGR2OGR#CSV-Reader_und_Writer|HowTo_OGR2OGR]] for more):
lon, lat, name
12.375, 49.618, Wert 1
16.198, 50.431, Wert 2
19.628, 51.389, Wert 3

ID, NAME, OGR_GEOM_WKT
1, Wert 1, "POINT(12.375 49.618)"
2, Wert 2, "POINT(16.198 50.431)"
3, Wert 3, "POINT(19.628 51.389)"

== Download sample files ==

Get your sample files by clicking to the links below. The data is about Swiss train stations and its of geometry type POINT (see [[WKT]]).

* [http://geoconverter.hsr.ch/data/shp/Bahnhoefe.zip Shapefile (.shp) data]
* [http://geoconverter.hsr.ch/data/csv/Bahnhoefe.zip Comma Separated Value (.csv) data]
* [http://geoconverter.hsr.ch/data/gml/Bahnhoefe.zip Geographic Markup Language (.gml) data]
* [http://geoconverter.hsr.ch/data/gpx/Bahnhoefe.zip GPS eXchange (.gpx) data]
* [http://geoconverter.hsr.ch/data/interlis1/Bahnhoefe.zip INTERLIS 1-Transfer Format (.itf) data]
* [http://geoconverter.hsr.ch/data/interlis2/Bahnhoefe.zip INTERLIS 2-XML Transfer Format (.xml) data]
* [http://geoconverter.hsr.ch/data/mif/Bahnhoefe.zip Mapinfo File (.mif) data]

== Feature requests, bug reports and suggestions ==

Do you have any feature requests, bug reports and suggestions? We appreciate every feedback!

Please go to the "discussion" ("Diskussion") tab of this Wiki page and put it there by adding (+) your feedback on the bottom.

== Weblinks ==

Look also at alternatives
* here at [[GIS-Konverter]] (de),
* especially at [[OpenLayers]]-Online
* and [[GPS-Software]].

GeoConverter in the press:
* http://freegeographytools.com/2008/two-online-vector-gisgpskml-conversion-utilities

GeoConverter

2008-06-20T12:26:58Z

Tbinna:

[[Bild:GeoConverter_V1.png|thumb|right]]
GeoConverter - Free Online Geospatial Data Converter. Reads and writes several [[GIS]] vector file formats based on the famous [[OGR]] tools.

Homepage: '''http://geoconverter.hsr.ch'''

== About ==

GeoConverter is a static ('1:1') geospatial file data format converter and coordinate transformer. It is running as a webapplication and designed to be used by technical users who casually have to convert [[GIS]] and [[GPS]] data.

Possible source GIS vector file formats are mostly the same as the target file formats (see the FAQ below).

GeoConverter is based on the FWTools (GDAL 1.5.0b1, FWTools 2.0.2, released 2007/12/05), especially on OGR2OGR as documented in the [[OGR]] pages.

It's possible that in the near future GeoConverter get's an additional machine-machine interface and this would be a typical Web Processing Service ([[WPS]]).

== Rules for uploading files ==
This section explains the rules for uploading files to GeoConverter:
* Let 'source file format' be the file(s) to be uploaded and let 'target file format' be the file you will download.
* We assume that you deliver '''one''' dataset at a time.
* There are formats, like Shapefile, Mapinfo or INTERLIS 2, which consist of more than one file. Before uploading, they ''must'' be packed into a zip file (use e.g. gzip or PKZIP).
* You ''may'' zip your file before uploading for those formats which consist of a single file, like GPX and KML.
* If you choose CSV as source file format to upload follow the special formatting described below.
* If you convert data to INTERLIS 2 (.xml), make sure you provide also an INTERLIS (target) model file (.ili).

If no coordinate reference system (CRS) parameters are given the conversion maintains it. Note that KML always defaults to WGS84 - EPSG 4326, the GPS system - which means that if a source dataset in a local CRS is given you ''must'' indicate the source CRS and set the target CRS to (EPSG:) 4326.

== FAQ ==

These are ''Frequently Asked Questions'' (FAQ) for the GeoConverter documentation Wiki.

=== When conversion fails... ===

;What to do when SHP conversion fails?: Make sure you provide an accompanying .DBF and .SHX files and make a ZIP file with all three.

;What to do when MIF conversion fails?: Make sure you provide an accompanying .MID file and make a ZIP file with both.

;GML or GPX fail to convert, what to do?: These formats are [[XML]] file formats. XML is a human readable ASCII format with a very rigid structure and encoding. There are readers which validate the input and even complain about the character encoding. Often when there is an encoding called 'UTF-8' but the file comes as Windows 'ANSI'; so you have to look for an editor or a tool which writes a proper UTF-8 encoded file.

;What to do when converting to KML succeeds but Google Earth displays nothing?: First, KML is an XML dialect so check the question about GML and GPX above. Second, KML assumes the GPS coordinate system WGS84. So check if you have filled in both numbers in the fields "Source EPSG no.:" and "Target EPSG no.:". Search for these EPSG numbers in [http://www.spatialreference.org spatialreference.org].

;What to do in general when the conversion fails?:
# Check the log file provided with the error.
# Check, if your input file is not bigger than 100 MB. If you have not uploaded a zip file, zip it and try again.
# Read the FAQ and check the rules given here.
# Try out some sample files (see below)
# Finally, if the problem persists consider dropping us a mail.

;Where can one submit bugs and feature requests?: [http://gis.hsr.ch/wiki/Diskussion:GeoConverter Here] at the bottom of the Wiki discussion page.

=== How To... ===

;Which file formats are supported by this webapplication?: These formats are supported for writing and also for reading. Try them out with the sample data below:
* Comma Separated Value (.csv/(.csvt))
* GPX (.gpx)
* Geographic Markup Language (.gml)
* INTERLIS 1-Transfer Format (.itf/.ili)
* INTERLIS 2-XML Transfer Format (.xml/.ili)
* Keyhole Markup Language (.kml)
* Mapinfo File (.mif/.mid)
* Shapefile (.shp/.dbf/.shx)

;What is WKT?: Well Known Text, i.e. geometry values in string representation. Typical examples are POINT(1 1), LINESTRING(1 1, 2 2, 3 3) and POLYGON((1 1, 2 2), (2 2, 3 3), (1 1)). See [[WKT]] for more information.

;How do I create an INTERLIS file (.ili) when converting to INTERLIS 2?: See documentation and/or contact us. Future INTERLIS 2 drivers won’t need this parameter for simple cases whereas professional conversion will need a full-fledged and configurable converter (see documentation page).

=== About Background / Terms of Use ===

;What is a layer and a dataset?: An OGR feature object encapsulates the values of a whole feature, that is a geometry and a set of attributes. A layer object is a collection of features (objects) of the same feature class. A data source represents a file or a database containing one or more layer objects. Note that 'layer' definition and 'feature class' definition are essentially the same. Layers have a reference to a spatial coordinate reference system (CRS). See also [[OGR]] for an explanation in german.

;I see GPX but can't find any other GPS file formats?: GPS file formats like NMEA or Garmin (.gdb) are converted best through existing software. See [[GPS-Software]] for more information about this topic.

;I miss DXF and other CAD file formats?: Microstation's DGN (up to version 7) is supported by OGR but not implemeted yet in GeoConverter. DXF unfortunately does not yet exist as a suitable driver for OGR altough some free libraries exist - so, sponsors are welcome!

;Why do I have to register before using this service? What are you doing with my personal information like my e-mail?: We ask for your e-mail and name mainly because of the tedious fight against spam! As a side effect you become part of the [[GISpunkt HSR]] community where we send information mails sometimes. These mails are currently sent every other month and will never exceed once a week. Your e-mail will never be used for other purposes whatsoever and we will never give away your personal data.

;What does GeoConverter mean?: GeoConverter means "Online ''Geo''spatial Data Format ''Converter''".

;Is this webapplication free?: Yes, GeoConverter is a free webapplication and it will remain free as long as this service is not abused by daily business cases (e.g. as long as bandwidth remains low).

;Is GeoConverter a competitor to other converter software?: There are quite some professional products around like FME, igtools or InterlisStudio. These products offer more than a straight forward and static 1:1 conversion. They can be manually configured and often support more file formats. So: No! GeoConverter is not meant as a competition but as an enabler of GIS and geospatial data!

;Who runs this webapplication?: This user service is brought to you by [[GISpunkt HSR]]. It is an experimental project without any warranty.

;What are the Terms of Service of the GeoConverter?: See [http://gis.hsr.ch/geoconverter/index.php?section=tos here].

;Can these conversions also be run on a local PC?: Yes, if you can install some software on your PC: We use OGR2OGR which is delivered among others as FWTools and you can run most conversions locally as it was designed for initially. See [[OGR]] for more information about this.

== CSV source format used in GeoConverter ==

GeoConverter uses the 'Comma Separated Values' ([[CSV]]) reader/writer from [[OGR]]. The OGR CSV reader/writer allows to encode geometry by using [[WKT]] as attribute values. Unfortunately, CSV leaves many decisions open and most annoying is that the (german) MS Excel is a non-conformant CSV writer. When trying to upload CSV from MS Excel some re-formatting is needed before hand, e.g. replacing semi-colons with colons, removing double quotes etc.

These are the rules in order to successfully upload CSV file with geometry:
* Use comma as field separator/delimiter
* The first line must be a column header (upper or lower case).
* The column header must contain one of two possibilities as column names:
** "LON" followed by "LAT" and a "NAME" attribute. LON/LAT are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "LAT" followed by "LON" and a "NAME" attribute. LAT/LON are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "longitude" followed by "latitude" and a "NAME" attribute. longitude/latitude are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "latitude" followed by "longitude" and a "NAME" attribute. latitude /longitude are floating point values (e.g. 47.355). Attribute values may (but must not) be enclosed in paratheses.
** "ID, NAME, THEGEOM". THEGEOM attributes (alternate name 'OGR_GEOM_WKT') have to be formatted as [[WKT]], i.e. with no comma but including the parantheses.
* There can be more attributes than these three.

Examples (see [[HowTo_OGR2OGR#CSV-Reader_und_Writer|HowTo_OGR2OGR]] for more):
lon, lat, name
12.375, 49.618, Wert 1
16.198, 50.431, Wert 2
19.628, 51.389, Wert 3

ID, NAME, OGR_GEOM_WKT
1, Wert 1, "POINT(12.375 49.618)"
2, Wert 2, "POINT(16.198 50.431)"
3, Wert 3, "POINT(19.628 51.389)"

== Download sample files ==

Get your sample files by clicking to the links below. The data is about Swiss train stations and its of geometry type POINT (see [[WKT]]).

* [http://geoconverter.hsr.ch/data/shp/Bahnhoefe.zip Shapefile (.shp) data]
* [http://geoconverter.hsr.ch/data/csv/Bahnhoefe.zip Comma Separated Value (.csv) data]
* [http://geoconverter.hsr.ch/data/gml/Bahnhoefe.zip Geographic Markup Language (.gml) data]
* [http://geoconverter.hsr.ch/data/gpx/Bahnhoefe.zip GPS eXchange (.gpx) data]
* [http://geoconverter.hsr.ch/data/interlis1/Bahnhoefe.zip INTERLIS 1-Transfer Format (.itf) data]
* [http://geoconverter.hsr.ch/data/interlis2/Bahnhoefe.zip INTERLIS 2-XML Transfer Format (.xml) data]
* [http://geoconverter.hsr.ch/data/mif/Bahnhoefe.zip Mapinfo File (.mif) data]

== Feature requests, bug reports and suggestions ==

Do you have any feature requests, bug reports and suggestions? We appreciate every feedback!

Please go to the "discussion" ("Diskussion") tab of this Wiki page and put it there by adding (+) your feedback on the bottom.

== Weblinks ==

Look also at alternatives
* here at [[GIS-Konverter]] (de),
* especially at [[OpenLayers]]-Online
* and [[GPS-Software]].

GeoConverter in the press:
* http://freegeographytools.com/2008/two-online-vector-gisgpskml-conversion-utilities

OSM

2008-06-20T12:26:09Z

Tbinna:

OSM (.osm) ist eine Abkürzung für [[OpenStreetMap]] sowie ein OpenStreetMap/XML-Dateiformat.

Diese Seite beschreibt das OSM-Dateiformat. Die Einstiegsseite zu OpenStreetMap befindet sich [[OpenStreetMap|hier]].

Siehe auch:
* [[OpenStreetMap]] - Einstiegsseite ins Projekt mit weiteren Weblinks
* [[HowTo OpenStreetMap]] - 'Alles' über das Erfassen, Editieren und Darstellen von OpenStreetMap-Daten
* [[GeoConverter]]

== Technische Dokumentation zum OSM-Dateiformats ==

OSM/XML besteht aus Knoten (Nodes), Kanten-Listen (Ways, früher: Segments) und Relations.

* http://wiki.openstreetmap.org/index.php/Develop - Übersicht und Einführung für Entwickler.
* http://wiki.openstreetmap.org/index.php/REST - Beschreibung des APIs.
* [http://wiki.openstreetmap.org/index.php/Planet.osm Planet.osm]-Repository.
* [http://wiki.openstreetmap.org/index.php/User:Frederik_Ramm/OSM_Book OpenStreetMap - Die freie Weltkarte nutzen], Buch von Frederic Ramm und Jochen Topf, 29.95 Euros. ISBN is 978-3-86541-262-1.

== Import/Export der OSM-Daten ==

=== FAQ ===
;How to get the OSM data?: If the size of the bounding box isn't too large osmxapi is great. osmxapi will return data from its own database, it's a web-based app; you don't need to download a planet file. If you want a large area or many areas, then switch to osmosis. Osmosis is a local application working on your own data file you need to download a planet file before.

;How to get reliable bbox coordinates?: Use http://www.informationfreeway.org/ Google Earth is probably the simplest, possibly Google Maps.

=== Notizen ===
* [[OpenStreetMap#Osmxapi]] - schreibt/exportiert nach XML direkt vom Webserver.
* [[OpenStreetMap#Osmosis]] - liest lokal oder übers Web (OSM REST API) und schreibt/exportiert nach XML, MySQL und PostgreSQL.

Möglichkeiten:
* [http://wiki.openstreetmap.org/index.php/Converting_OSM_to_GML Converting OSM to GML] - mit XSLT. Kann dann z.B. mit [[OGR]] weiterverarbeitet werden
* [http://svn.openstreetmap.org/applications/utils/ utils auf SVN (Tool-Sammlung)] z.B. mit osm2cvs (Perl) und osm2kml (cpp)
* [http://wiki.openstreetmap.org/index.php/Shapefile_upload_script Shapefile upload script]
* [http://geometrybag.wordpress.com/2007/06/18/openstreetmap-data-in-arcgis/ Open Street Maps in ArcGIS laden] (ArcScript mit Python)
* [http://osmlib.rubyforge.org/osmlib-export/ OSM Export for Ruby]

Outdated:
* [http://wiki.openstreetmap.org/index.php/OSM_in_Google_Earth OSM in Google Earth] (kml), XSLT-Skript (leider noch mit 0.4 API).

Mobiles:
* [http://freegeographytools.com/2007/converting-openstreetmap-data-into-gpx-or-garmin-img-format Converting OSM to Garmin IMG]
* Mit [http://www.mgmaps.com/create/ Shustrik's .map file creation tool] für [http://www.mgmaps.com/ MGMaps] aufbereiten.

=== OSM zu Shapefiles konvertieren ===

Man beachte, dass es bedingt durch das Datenmodell von OSM keine einzig richtige Konversion gibt.

Ein Versuch eines Datenmodells, das topografischen Karten nahe kommt, wird hier diskutiert:
* Mailingliste http://lists.geofabrik.de/listinfo/osm-gis
* Erste Ergebnisse lassen sich direkt ab [http://www.geofabrik.de/download.html Geofabrik.de] herunterladen, diese sind wie folgt strukturiert: buildings, natural, points, railways, roads, waterways.

Ansonsten kann man vorsichtigerweise bei Nodes/Ways/Relations bleiben.
Für kleinere Ausschnitte:
# Export-Tab auf openstreetmap.org => .osm lokal speichern.
# .osm zu GML konvertieren mit XSTL-Skript ([http://wiki.openstreetmap.org/index.php/Converting_OSM_to_GML Converting], verwendet xalan). Achtung: Das XSLT muss noch verbessert werden ('Closed Ways' fehlen).
# GML zu Shapefiles konvertieren mit [[OGR]]-Tools oder [[GeoConverter]].
Für grössere Datenmengen:
* Export nach .osm mit Planetfiles (siehe oben)
* Import in PostgreSQL mit [http://svn.openstreetmap.org/applications/utils/export/osm2pgsql/ osm2pgsql]

== OSM REST API 0.5 ==

OSM REST API 0.5: http://api.openstreetmap.org/api/0.5/map?bbox=11.54,48.14,11.543,48.145
Example bbox:
* Example 11.54,48.14,11.543,48.145
* Bremen 8.4900,52.9195,9.123,53.234
* Hannover 9.55,52.3,9.91,52.47
* IsleOfWight -1.6,50.57,-1.0,50.77
* Rapperswil ...

[[Kategorie:Dateiformat]]

Tbinna: /* Weiterentwicklung */

== Dokumentation ==

=== Projekt-Dokumentation ===
* Webapplikation läuft auf Port 7777.
* Fahrplan, Abschnitte, Stationen und Fahrzeuge werden als CSV-Datei (z.B. MS Excel) erfasst.
* Anzeige der eingesetzten Transportfahrzeug-Typen

=== Dateiformate ===

Fahrplan (courses):
ID,CourseNo,Name,SectionId,Leaving,Arriving
1,1,Küsnacht-Erlenbach-Thalwil (Querfahrten),7,06:10,06:18
2,3,Küsnacht-Erlenbach-Thalwil (Querfahrten),28,06:30,06:39
3,5,Küsnacht-Erlenbach-Thalwil (Querfahrten),32,07:00,07:06
Abschnitte (sections):
ID,Name,FromId,ToId,OGR_GEOM_WKT
1,Altendorf ZSG-Lachen ZSG,1,11,LINESTRING (8.832605487655814 47.195020971866192 0,8.836920336491104 47.195139532468382 0)
2,Altendorf ZSG-Pfäffikon SZ ZSG,1,16,LINESTRING (8.832602456564302 47.195032939911052 0,8.820443150089432 47.203773325450562 0)
Stationen (stations):
ID,StationName
1,Zürich Bürkliplatz
2,Insel Ufenau
3,Rapperswil ZSG
Fahrzeuge (vehicles):
ID,Name,Imagename,Description
1,MS Uetliberg,ms_uetliberg.png,Motorschiff Uetliberg
2,Yyyyy,yyyyy.png,fsd dsg dg dgd
3,DS Rapperswil,ds_rapperswil.png,Dampfschiff Rapperswil

== To Do ==

* ZSG-Simulation als Webserver (Servlet), d.h. ohne Installation auf Desktop.

Erledigt
* Deutsche und englische Benutzerdoku. -- [[Benutzer:Stefan|Stefan]] 10:31, 2. Mär. 2008 (CET)
* Konfiguration -- [[Benutzer:DTran|DTran]] 13:48, 4. Jan. 2008 (CET)
* Separate Fahrplan-Komponente -- [[Benutzer:DTran|DTran]] 13:48, 4. Jan. 2008 (CET)

== Weiterentwicklung ==
* Ideen:
** Anbindung PostgreSQL ([http://wiki.hsr.ch/Prog1Java/wiki.cgi?GoogleEarthServer4PG GoogleEarthServer4PG])
** Bei Start einstellen (verändern) der Zeit: fingierte Startzeit und Zeitraffer, so dass man die Simulation auch Nachts anschauen kann.