Opened 3 years ago

Closed 3 years ago

#1698 closed task (fixed)

Change OSM featured city to Bonn for FOSS4G

Reported by: kalxas Owned by: live-demo@…
Priority: critical Milestone: OSGeoLive10.0
Component: OSGeoLive Keywords: OSM data
Cc: live-demo@…

Description

We need to switch the featured city for the next release.

Change history (8)

comment:1 Changed 3 years ago by darkblueb

http://download.osgeo.org/livedvd/10.0/BONN_DE.osm.bz2

here is a "rough" cut ... I made sure the City Hall downtown was in it, plus more city to the North across the Rhine .. but otherwise it is fairly arbitrary.

comments or changes welcome

comment:2 Changed 3 years ago by darkblueb

Trac login takes a OSGeo userid -- operare ?

comment:3 Changed 3 years ago by darkblueb

nightly build 165 -- osm data looks ok, but install_pgrouting.sh shows:

...
Setting up osm2pgrouting (2.1.0-1~xenial1) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
create pgrouting database with PostGIS and pgRouting
CREATE EXTENSION
CREATE EXTENSION

ERROR: /usr/local/share/data/osm/feature_city_CBD.osm.bz2 sample data is not available

coordinate with https://github.com/robe2/OSGeoLive-doc/blob/master/en/quickstart/pgrouting_quickstart.rst

comment:4 Changed 3 years ago by kalxas

osm2pgsql seems to be fine with the following link:

/usr/local/share/data/osm/feature_city.osm.bz2

===============================================================
Starting "load_postgis.sh" ...
===============================================================
CREATE EXTENSION
osm2pgsql SVN version 0.88.1 (64bit id space)

Using built-in tag processing pipeline
Using projection SRS 4326 (Latlong)
Setting up table: planet_osm_point
Setting up table: planet_osm_line
Setting up table: planet_osm_polygon
Setting up table: planet_osm_roads
Allocating memory for dense node cache
Allocating dense node cache in one big chunk
Allocating memory for sparse node cache
Sharing dense sparse
Node-cache: cache=800MB, maxblocks=102400*8192, allocation method=3
Mid: Ram, scale=10000000

Reading in file: /usr/local/share/data/osm/feature_city.osm.bz2
StartElement: Unknown element name: note
Unknown node type 3
EndElement: Unknown element name: note
StartElement: Unknown element name: meta
EndElement: Unknown element name: meta

comment:6 Changed 3 years ago by darkblueb

adding another pgrouting fix to this changeset; adding tiny osm CLI tools

user@live10a:~/osgeolive_dbb_gogs/bin$ sudo apt-get install    osmctools osmium-tool  
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  osmctools osmium-tool
0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded.
Need to get 367 kB of archives.
After this operation, 1,335 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 osmium-tool amd64 1.3.0-1 [247 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 osmctools amd64 0.6-1 [120 kB]
Fetched 367 kB in 2s (181 kB/s)     
Selecting previously unselected package osmium-tool.
(Reading database ... 177594 files and directories currently installed.)
Preparing to unpack .../osmium-tool_1.3.0-1_amd64.deb ...
Unpacking osmium-tool (1.3.0-1) ...
Selecting previously unselected package osmctools.
Preparing to unpack .../osmctools_0.6-1_amd64.deb ...
Unpacking osmctools (0.6-1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up osmium-tool (1.3.0-1) ...
Setting up osmctools (0.6-1) ...

comment:7 Changed 3 years ago by darkblueb

fixed in build 174 -- close ticket after testing

comment:8 Changed 3 years ago by kalxas

Resolution: fixed
Status: newclosed

fixed

Note: See TracTickets for help on using tickets.