[sumo-user] netconvert options for importing an osm map

[kavita pandey]

I import an osm map and converted into .net.xml file using netconvert
command .
while this conversion , i read all the options provided by netconvert. I
selected the following options

--junctions.join true
--try-join-tls true
--remove-edges.by-vclass
pedestrian,bicycle,moped,motorcycle,truck,trailer,bus,coach,tram,rail_urban,rail,rail_electric,evehicle
--remove-edges.isolated true
--tls.guess true
--no-turnarounds.tls true

I am also looking for the option --proj.utm but then i found in tutorial
"import openstreetmap" that netconvert option automatically uses UTM
transformation for WGS84 coordinate system .

Could you please help me in finalizing the options to be chosen while
netconvert.
Is something missed out , which is important or from the above mentioned
list -- not recommended ...........

For different traffic scenario's , results can be different. So to have
real results , this is an important point.
kindly help
thanks a lot

rgds
sims

[Jakob Erdmann]

our current default options for importing osm are:
--geometry.remove,--roundabouts.guess,--ramps.guess,--junctions.join,--osm.railway.oneway-default,--tls.guess-signals,--tls.discard-simple,--tls.join

instead of --remove-edges.by-vclass ... you could also use
--keep-edges.by-vclass passenger

i would advise you to avoid use of --tls.guess for osm networks and use
--tls.guess-signals instead (it fits better with the way tls are
represented in osm).

be prepared to look over the generated network critically to fix broken
junctions and tls plans.

regards,
Jakob

Post by kavita pandey
I import an osm map and converted into .net.xml file using netconvert
command .
while this conversion , i read all the options provided by netconvert. I
selected the following options
--junctions.join true
--try-join-tls true
--remove-edges.by-vclass
pedestrian,bicycle,moped,motorcycle,truck,trailer,bus,coach,tram,rail_urban,rail,rail_electric,evehicle
--remove-edges.isolated true
--tls.guess true
--no-turnarounds.tls true
I am also looking for the option --proj.utm but then i found in tutorial
"import openstreetmap" that netconvert option automatically uses UTM
transformation for WGS84 coordinate system .
Could you please help me in finalizing the options to be chosen while
netconvert.
Is something missed out , which is important or from the above mentioned
list -- not recommended ...........
For different traffic scenario's , results can be different. So to have
real results , this is an important point.
kindly help
thanks a lot
rgds
sims
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for
all
things parallel software development, from weekly thought leadership blogs
to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
sumo-user mailing list
https://lists.sourceforge.net/lists/listinfo/sumo-user

[Jakob Erdmann]

No. sorry for the misunderstanding default options means: in our script
tools/import/osm/osmBuild.py these are the options we assume by default. If
you call netconvert on the commandline you need to add all of them
explicitly.

thanks for ur valuable reply.
default options means if am not writing these options , automatically all
the default option values are true.
When i import the network with --junctions.join option as true or not
writing this option (bcz default) , both xml files are different.
So finally i will use these options only
--keep-edges.by-vclass passenger
--remove-edges.isolated true
--no-turnarounds.tls true
and the following options which i want to use are default options
--junctions.join , --try-join-tls , --tls.guess-signals . So no need to
mention.
What about other default options. should i keep as it is or specify them
as false.
rgds
sims

Post by Jakob Erdmann
--geometry.remove,--roundabouts.guess,--ramps.guess,--junctions.join,--osm.railway.oneway-default,--tls.guess-signals,--tls.discard-simple,--tls.join
instead of --remove-edges.by-vclass ... you could also use
--keep-edges.by-vclass passenger
i would advise you to avoid use of --tls.guess for osm networks and use
--tls.guess-signals instead (it fits better with the way tls are
represented in osm).
be prepared to look over the generated network critically to fix broken
junctions and tls plans.
regards,
Jakob

Post by kavita pandey
I import an osm map and converted into .net.xml file using netconvert
command .
while this conversion , i read all the options provided by netconvert. I
selected the following options
--junctions.join true
--try-join-tls true
--remove-edges.by-vclass
pedestrian,bicycle,moped,motorcycle,truck,trailer,bus,coach,tram,rail_urban,rail,rail_electric,evehicle
--remove-edges.isolated true
--tls.guess true
--no-turnarounds.tls true
I am also looking for the option --proj.utm but then i found in tutorial
"import openstreetmap" that netconvert option automatically uses UTM
transformation for WGS84 coordinate system .
Could you please help me in finalizing the options to be chosen while
netconvert.
Is something missed out , which is important or from the above mentioned
list -- not recommended ...........
For different traffic scenario's , results can be different. So to have
real results , this is an important point.
kindly help
thanks a lot
rgds
sims
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored
by Intel and developed in partnership with Slashdot Media, is your hub
for all
things parallel software development, from weekly thought leadership
blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
sumo-user mailing list
https://lists.sourceforge.net/lists/listinfo/sumo-user