Re: [OSM-talk] [tagging] Feature Proposal - RFC - (Trolley)
He is referring to what Americans call "shopping carts". --Original Message-- From: Alex S. Sender: talk-boun...@openstreetmap.org To: OpenStreetMap talk mailing list Subject: Re: [OSM-talk] [tagging] Feature Proposal - RFC - (Trolley) Sent: Apr 25, 2010 4:34 PM Adrien Pavie wrote: > The tag is for know if a shop has trolleys. All the details are in the wiki. > Thanks in advance for comments. Why would shops have light-rail trains? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk -- John F. Eldredge -- j...@jfeldredge.com "Reserve your right to think, for even to think wrongly is better than not to think at all." -- Hypatia of Alexandria ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [tagging] Feature Proposal - RFC - (Trolley)
Adrien Pavie wrote: > The tag is for know if a shop has trolleys. All the details are in the wiki. > Thanks in advance for comments. Why would shops have light-rail trains? ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] [tagging] Feature Proposal - RFC - (Trolley)
Hello, I send a proposal "Trolley" (in part "shop") and I send this RFC to get opinions about this. This is a direct link : http://wiki.openstreetmap.org/wiki/Proposed_features/Trolley The tag is for know if a shop has trolleys. All the details are in the wiki. Thanks in advance for comments. Adrien Pavie (alias Dri60) ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Is this normal ?
On 25 Apr 2010, at 11:25, Jon Burgess wrote: > On Sun, 2010-04-25 at 10:51 -0700, Simon Gornall wrote: >> So, I'd set everything up on my Ubuntu linux box, and decided to time >> the import for posterity... >> >> >> www:/opt/gis> time osm2pgsql -s -v -U simon -d gis -C 7000 >> data/planet-latest.osm >>osm2pgsql SVN version 0.66- >> >>Using projection SRS 900913 (Spherical Mercator) >>Setting up table: planet_osm_point >>Setting up table: planet_osm_line >>Setting up table: planet_osm_polygon >>Setting up table: planet_osm_roads >>Mid: pgsql, scale=100, cache=7000MB, maxblocks=896001*8192 >>Setting up table: planet_osm_nodes >>NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index >>"planet_osm_nodes_pkey" for table "planet_osm_nodes" >>Setting up table: planet_osm_ways >>NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index >>"planet_osm_ways_pkey" for table "planet_osm_ways" >>Setting up table: planet_osm_rels >>NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index >>"planet_osm_rels_pkey" for table "planet_osm_rels" >> >>Reading in file: data/planet-latest.osm >>Processing: Node(593072k) Way(45376k) Relation(484k) >>Node stats: total(593072533), max(696096737) >>Way stats: total(45376969), max(55410575) >>Relation stats: total(484528), max(555276) >> >>Going over pending ways >>processing way (13679k) >> >>Going over pending relations >> >>node cache: stored: 593072533(100.00%), storage efficiency: >>86.21%, hit rate: 100.00% >>Committing transaction for planet_osm_line >>Committing transaction for planet_osm_polygon >>Committing transaction for planet_osm_roads >>Sorting data and creating indexes for planet_osm_roads >>Sorting data and creating indexes for planet_osm_polygon >>Sorting data and creating indexes for planet_osm_line >>Committing transaction for planet_osm_point >>Sorting data and creating indexes for planet_osm_point >>ANALYZE planet_osm_roads; >> failed: ERROR: could not access status of transaction >>4026772988 >>DETAIL: Could not open file "pg_clog/0F00": No such file or >>directory. >> >>Error occurred, cleaning up >>12523.240u 403.910s 7:13:16.49 49.7% 0+0k 266220448+0io >>10515pf+0w >> >> >> >> >> I'm a bit concerned about the red bit above... > > The error is coming from the postgresql server, you should probably > check its logs (/var/log/postgresql/postgresql-8.3-main.log). Perhaps > you ran out of disk space or exceeded some resource limit? Well, the logs don't actually tell me much more than the error did: 2010-04-24 20:19:22 PDT LOG: database system is ready to accept connections 2010-04-24 20:19:22 PDT LOG: incomplete startup packet 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_point" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_point; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_point_tmp" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_point_tmp; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_line" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_line; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_line_tmp" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_line_tmp; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_polygon" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_polygon; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_polygon_tmp" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_polygon_tmp; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_roads" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_roads; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_roads_tmp" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_roads_tmp; 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_nodes" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_nodes 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_ways" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_ways 2010-04-24 20:22:25 PDT ERROR: table "planet_osm_rels" does not exist 2010-04-24 20:22:25 PDT STATEMENT: DROP TABLE planet_osm_rels 2010-04-25 03:35:40 PDT ERROR: could not access status of transaction 4026772988 2010-04-25 03:35:40 PDT DETAIL: Could not open file "pg_clog/0F00": No such file or directory. 2010-04-25 03:35:40 PDT STATEMENT: ANALYZE planet_osm_roads; 2010-04-25 03:35:42 PDT LOG: unexpected EOF on client connection 2010-04-25 03:35:42 PDT LOG: unexpected EOF on client connection 2010-04-25 03:35:42 PDT LOG: unexpected EOF on client connection 2010-04-25 03:36:37
Re: [OSM-talk] Is this normal ?
On Sun, 2010-04-25 at 10:51 -0700, Simon Gornall wrote: > So, I'd set everything up on my Ubuntu linux box, and decided to time > the import for posterity... > > > www:/opt/gis> time osm2pgsql -s -v -U simon -d gis -C 7000 > data/planet-latest.osm > osm2pgsql SVN version 0.66- > > Using projection SRS 900913 (Spherical Mercator) > Setting up table: planet_osm_point > Setting up table: planet_osm_line > Setting up table: planet_osm_polygon > Setting up table: planet_osm_roads > Mid: pgsql, scale=100, cache=7000MB, maxblocks=896001*8192 > Setting up table: planet_osm_nodes > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index > "planet_osm_nodes_pkey" for table "planet_osm_nodes" > Setting up table: planet_osm_ways > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index > "planet_osm_ways_pkey" for table "planet_osm_ways" > Setting up table: planet_osm_rels > NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index > "planet_osm_rels_pkey" for table "planet_osm_rels" > > Reading in file: data/planet-latest.osm > Processing: Node(593072k) Way(45376k) Relation(484k) > Node stats: total(593072533), max(696096737) > Way stats: total(45376969), max(55410575) > Relation stats: total(484528), max(555276) > > Going over pending ways > processing way (13679k) > > Going over pending relations > > node cache: stored: 593072533(100.00%), storage efficiency: > 86.21%, hit rate: 100.00% > Committing transaction for planet_osm_line > Committing transaction for planet_osm_polygon > Committing transaction for planet_osm_roads > Sorting data and creating indexes for planet_osm_roads > Sorting data and creating indexes for planet_osm_polygon > Sorting data and creating indexes for planet_osm_line > Committing transaction for planet_osm_point > Sorting data and creating indexes for planet_osm_point > ANALYZE planet_osm_roads; > failed: ERROR: could not access status of transaction > 4026772988 > DETAIL: Could not open file "pg_clog/0F00": No such file or > directory. > > Error occurred, cleaning up > 12523.240u 403.910s 7:13:16.49 49.7% 0+0k 266220448+0io > 10515pf+0w > > > > > I'm a bit concerned about the red bit above... The error is coming from the postgresql server, you should probably check its logs (/var/log/postgresql/postgresql-8.3-main.log). Perhaps you ran out of disk space or exceeded some resource limit? Jon ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] Is this normal ?
So, I'd set everything up on my Ubuntu linux box, and decided to time the import for posterity...www:/opt/gis> time osm2pgsql -s -v -U simon -d gis -C 7000 data/planet-latest.osm osm2pgsql SVN version 0.66-Using projection SRS 900913 (Spherical Mercator)Setting up table: planet_osm_pointSetting up table: planet_osm_lineSetting up table: planet_osm_polygonSetting up table: planet_osm_roadsMid: pgsql, scale=100, cache=7000MB, maxblocks=896001*8192Setting up table: planet_osm_nodesNOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_nodes_pkey" for table "planet_osm_nodes"Setting up table: planet_osm_waysNOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_ways_pkey" for table "planet_osm_ways"Setting up table: planet_osm_relsNOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "planet_osm_rels_pkey" for table "planet_osm_rels"Reading in file: data/planet-latest.osmProcessing: Node(593072k) Way(45376k) Relation(484k)Node stats: total(593072533), max(696096737)Way stats: total(45376969), max(55410575)Relation stats: total(484528), max(555276)Going over pending waysprocessing way (13679k)Going over pending relationsnode cache: stored: 593072533(100.00%), storage efficiency: 86.21%, hit rate: 100.00%Committing transaction for planet_osm_lineCommitting transaction for planet_osm_polygonCommitting transaction for planet_osm_roadsSorting data and creating indexes for planet_osm_roadsSorting data and creating indexes for planet_osm_polygonSorting data and creating indexes for planet_osm_lineCommitting transaction for planet_osm_pointSorting data and creating indexes for planet_osm_pointANALYZE planet_osm_roads; failed: ERROR: could not access status of transaction 4026772988DETAIL: Could not open file "pg_clog/0F00": No such file or directory.Error occurred, cleaning up12523.240u 403.910s 7:13:16.49 49.7% 0+0k 266220448+0io 10515pf+0wI'm a bit concerned about the red bit above...The graph of cpu-usage was pretty interesting... {CPU}...{DISK}...{CPU} :)___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] LINZ import
John Smith wrote: >On 16 April 2010 09:39, Robin Paulson wrote: >> do oyu have any suggestions how to keep the metadata when importing? >> i presume it is a non-manual method, i.e. uploading a .osm file - >> how do you merge the two data sets? > >You open the area as normal and open the osm file as a different layer >and then you can copy and paste between layers. I helped at some imports for Kosovo where it was done this way.¹ The source data was split into small chunks (iirc 100 ways), uploaded and linked at the wiki, where users could "subscribe" to the chunks they would import. Worked quite well. hth malenki ¹http://wiki.openstreetmap.org/wiki/Kosovo_iMMAP_Import ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
