Skip to content
This repository was archived by the owner on Apr 16, 2023. It is now read-only.

FAQ

Jump to bottom
Stefan edited this page Dec 18, 2016 · 6 revisions

General

Q: Are there alternatives to OSMaxx?

Yes, see OSM Wiki.

Q: How long does it take to process?

From 20 minutes to hours - depending on the work load of other processes. Users get mail when processing is finished.

Q: What do you meand by 2.5D?

OSM is "data driven" vector data with a topological geometry model. There's no wireframe but attributes like the height of a building, the building-levels or the roof type and orientation of a building.

Q: What typical other map data is missing in OSMaxx?

  • No digtial terrain model data. That could come from a separate data source.
  • No satellite imagery. Thats a raster data source different from OSM and vector.
  • No user ratings of POIs (restaurants). That's not belonging to the principles and philosophy of OSM.

Q: What are the known limitations of OSMaxx?

  • The download data size is restricted to ~700 MB.
  • No geocoding: There's table address_p which contains housenumber attribute and mostly street name. But geocoding (and routing) is much more than that. See our project OSMNames. There's limited possibility to collect all name tags in order to ge a geoname search.
  • No routing (except Garmin format): Routing (and geocoding) requires much more sophisticated processing of OSM data. In the meantime use Garmin format or look e.g. at project OSRM.

Q: What are the underlying limitations of OSMaxx?

  • No editing: Editing means reading the whole information about an entity/object and conserving the original data structure and information. That's not the case in OSMaxx since it's goal (and unique selling point) is to restructure the OSM data in order to make it manageable by GIS systems.

Clone this wiki locally