Re: [OSM-dev] New OGR driver to read OpenStreetMap .osm / .pbf files
Even Rouault wrote: Le vendredi 20 juillet 2012 20:58:08, Sven Geggus a écrit : Even Rouault even.roua...@mines-paris.org wrote: Testing with larger areas, like whole France or Europe, shows sluggish performance when ways are built from nodes, but that's perhaps expected. I didn't compare with other tools to know if the indexing or request strategy is particularly bad. Hm, would it be possible with this to e.g. convert all the forests from a complete planetfile to a polygon shapefile while discarding all the rest? Yes, this should be possible by specifying the appropriate -where clause to ogr2ogr. However this will have roughly the same performance as completely converting the whole planetfile, so it will take some time... Hum, actually while writing this, I see that the attribute filter is evaluated after having reconstructed the geometry. So there's perhaps something I can do to speed that up a bit, in order to evaluate the attribute filter before and skip the geometry building if the attribute filter rejects the filter. I made a test with germany.osm.pbf file from Geofabrik. I used GDAL development version r24717 and my ogr2ogr command was: ogr2ogr -f SQlite -dsco spatialite=yes germany_forests.sqlite germany.osm.pbf polygons multipolygons -gt 2 --config OGR_SQLITE_SYNCHRONOUS OFF -where landuse='forest' -progress Execution took 12 minutes. This much landuse=forest areas were found: Layer name: polygons Geometry: Polygon Feature Count: 262683 Layer name: multipolygons Geometry: Multi Polygon Feature Count: 6917 There are some more timings and info about the hardware used in the test in this mail http://article.gmane.org/gmane.comp.gis.gdal.devel/32175 -Jukka Rahkonen- ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] [GSoC] Improvements to Vespucci
Hi, Preset support is now enhanced. When applying a preset: * Fixed tags (i.e. key and value are given) are still added as usual * Non-fixed, non-optional tags (e.g. text or combo tags) are added with the key only. If the user saves without entering a value, it will be removed. * Non-fixed, optional tags are not automatically added, but considered when the autocomplete menu is built The autosuggest now works like this: * automatically triggered once at least letter is entered (a threshold of 0 is NOT supported by android, unfortunately) * Triggered when the user clicks an already-focused input box * Can be hidden by the back key (default behavior) * The key autosuggest menu contains ** First, all keys that apply to the preset that was applied (if any) ** Then, all keys in presets fitting the current node type in alphabetical order (i.e. if a key appears only in presets that can only be applied to nodes, it will not be suggested when a way is being tagged) ** Keys that are already used are NOT offered again * The value autosuggest contains all values, in alphabetical order, that can be applied to the given key An APK will be provided later. Kind regards, Jan ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
