OSMaxx

"OSM Arbitrary Excerpt Export" (osmaxx)

The source of worldwide geospatial data for interactive and printed maps and for geospatial data analysis. Cuts out OpenStreetMap data, processes it to geodata and converts it to typical GIS fileformats before being prepared for download.

Die weltweite Geodatenquelle für interaktive und gedruckte Karten und für GIS Analyse. OpenStreetMap-Daten ausschneiden, zu Geodaten aufbereiten und als typisches GIS-Fileformat konvertiert abgeben.

Weblinks

• Website: http://osmaxx.hsr.ch/
• Repository (Source Code, Ticketing): https://github.com/geometalab/osmaxx
• UI Mockup: http://geometalab.github.io/osmaxx/
• IFS internal (login required): https://wiki.ifs.hsr.ch/IfSwWiki/wiki.cgi?Osmaxx

Project

Project staff comes mainly from Geometa Lab HSR.

• Stefan: Lead and concept
• Raphael: Coordination, Integration, Frontend and Backend
• Tobias: Frontend (Javascript, ...)
• Nicola: Backend (Python, Postgres, ...)
• Eugene: PostGIS loading and schema transformation/data homogenization, (QGIS symbology)
• Lukas: Extraction tool chain (Linux tools, ...)
• Martin: ArcGIS symbology (ArcGIS)

Technical

Some explanations (incomplete):

• Selected OSM objects are transformed into Osmaxx tables (feature classes / layers). Some objects are captured in OSM as point, some as linestring or as area - and often both as point and area.
• All tables names contain a hint which geometry type they contain:
  • poi_p => POIs with point geometry,
  • roads_l => line/multilinestring,
  • poi_a => area/multipolygon.

Osmaxx Data Model v.2

Tables	Description
adminarea_a	Administrative boundaries range from large groups of nation states right down to small administrative districts and suburbs, with an indication of this size/level of importance.
adminunit_a	from sep. validated source
boundary_l	The boundary is used to mark the borders of areas, mostly political, but possibly also of other administrative areas.
building_a	To mark the outline of the area of the building
coastline_l	From separate source
landuse_a	Land use describes the human use of land, for example fields, pastures, and settlements.
military_a	See military_p
military_p	The military is for buildings and land used by the military.
natural_a	see natural_p
natural_p	Used to describes natural physical land features, including ones that have been modified by humans.
nonop_l	non-op./planned infrastructure not usable for traffic
geoname_l	geographic names: regions, lakes
geoname_p	geographic names: cities, towns, villages
pow_a	See pow_p
pow_p	Place of worshop - religious buildings and infrastructure
poi_a	See poi_p
poi_p	Point-of-interest - nodes plus area-centroids.
power_a	power infrastructure
power_p	power infrastructure, generators
power_l	power infrastructure
transport_a	See transport_p
transport_p	public transport
railway_l	railway lines
road_l	roads (incl. airstrips )
traffic_a	See traffic_p
traffic_p	train/bus stops , etc.
water_a	See water_p
water_p	lakes, etc.
water_l	rivers, canals, streams (centerlines)

Notes

• Das Zielschema umfasst echte Geometrien (Punkt, Multi-Linestring, Multi-Polygon) und ein GIS-Datenmodell (Highways, Railways, Buildings, etc.).
• Zur Aufbereitung in das Zielschema gehört u.a. ein Postprocessing, dass die heterogenen OSM-Daten homogenisiert (z.B. Restaurants als Punktobjekte, auch wenn sie in OSM als Gebäudefläche erfasst wurden).
• Ein zusätzliches Zielschema enthält routingfähige Strassen. Dieses wird als Teil des Garmin-Formats abgebegen.
• Abgabeformate sind GIS-Fileformaten (GeoPackage, Shapefle, File Geodatabase) sowie ein Navi-Format (Garmin .IMG).
• Es werden auch Karten-Symbologien für QGIS und ArcGIS abgegeben, passend zu den GIS-Fileformaten.