[sumo-user] Netconvert: importing "extra" OSM attributes

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[sumo-user] Netconvert: importing "extra" OSM attributes

Sasan Amini-2
Dear all,

I have a question regarding the attributes, more specifically 3 attributes, one can import from OSM using NETCONVERT. 
1) loop detectors: I was trying to import the traffic detectors form OSM which I have added manually as monitoring stations using JOSM. But I can't find a way to import them in my network or as an additional file. Is it possible to import them at all?
2) One other issue is the number of lanes. In JOSM one can add a key to differentiate the number of lanes in opposite direction (lanes:backward). But I think NETCONVERT reads only the key "lanes" to get the number of lanes in both directions. 
3) Bus lanes are also defined with a key "lanes:psv" in OSM. However, the vehicle types allowed/disallowed on the lanes are not affected by this key. 
The bigger problem is actually to find a platform where several people can edit large networks together. Any tips on this aside JOSM are much appreciated.  

Best,
Sasan

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Reply | Threaded
Open this post in threaded view
|

Re: [sumo-user] Netconvert: importing "extra" OSM attributes

Jakob Erdmann
1) currently not possible. Also, according to https://wiki.openstreetmap.org/wiki/Key:monitoring:traffic, the osm objects reference a position next to the road rather than being assigned to an osm way (which would be more useful for extracting detectors).
2) lanes:backward is being evaluated (also lanes:forward and lanes). Note, that 'lanes' must be set in order for the other tags to be evaluated
3) lanes:psv is currenlty not evaluated. However the tags 'busway:right', 'busway:left', 'busway:both' are read

regards,
Jakob

Am Do., 10. Sept. 2020 um 16:04 Uhr schrieb Sasan Amini <[hidden email]>:
Dear all,

I have a question regarding the attributes, more specifically 3 attributes, one can import from OSM using NETCONVERT. 
1) loop detectors: I was trying to import the traffic detectors form OSM which I have added manually as monitoring stations using JOSM. But I can't find a way to import them in my network or as an additional file. Is it possible to import them at all?
2) One other issue is the number of lanes. In JOSM one can add a key to differentiate the number of lanes in opposite direction (lanes:backward). But I think NETCONVERT reads only the key "lanes" to get the number of lanes in both directions. 
3) Bus lanes are also defined with a key "lanes:psv" in OSM. However, the vehicle types allowed/disallowed on the lanes are not affected by this key. 
The bigger problem is actually to find a platform where several people can edit large networks together. Any tips on this aside JOSM are much appreciated.  

Best,
Sasan
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Reply | Threaded
Open this post in threaded view
|

Re: [sumo-user] Netconvert: importing "extra" OSM attributes

Sasan Amini-2
Hi Jakob,

thanks for the explanation. I made the bus lane and the lane numbers work. However, regarding the detectors, I disagree with you. The monitoring stations are actually defined on the nodes in JOSM. So in my opinion, they are similar to traffic lights. 

Best,
Sasan

On Thu, Sep 10, 2020 at 8:52 PM Jakob Erdmann <[hidden email]> wrote:
1) currently not possible. Also, according to https://wiki.openstreetmap.org/wiki/Key:monitoring:traffic, the osm objects reference a position next to the road rather than being assigned to an osm way (which would be more useful for extracting detectors).
2) lanes:backward is being evaluated (also lanes:forward and lanes). Note, that 'lanes' must be set in order for the other tags to be evaluated
3) lanes:psv is currenlty not evaluated. However the tags 'busway:right', 'busway:left', 'busway:both' are read

regards,
Jakob

Am Do., 10. Sept. 2020 um 16:04 Uhr schrieb Sasan Amini <[hidden email]>:
Dear all,

I have a question regarding the attributes, more specifically 3 attributes, one can import from OSM using NETCONVERT. 
1) loop detectors: I was trying to import the traffic detectors form OSM which I have added manually as monitoring stations using JOSM. But I can't find a way to import them in my network or as an additional file. Is it possible to import them at all?
2) One other issue is the number of lanes. In JOSM one can add a key to differentiate the number of lanes in opposite direction (lanes:backward). But I think NETCONVERT reads only the key "lanes" to get the number of lanes in both directions. 
3) Bus lanes are also defined with a key "lanes:psv" in OSM. However, the vehicle types allowed/disallowed on the lanes are not affected by this key. 
The bigger problem is actually to find a platform where several people can edit large networks together. Any tips on this aside JOSM are much appreciated.  

Best,
Sasan
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Reply | Threaded
Open this post in threaded view
|

Re: [sumo-user] Netconvert: importing "extra" OSM attributes

Jakob Erdmann
Just to make sure I'm not misunderstanding your point: Are they defined on nodes that belong to a <way> which defines the road or are they defined on stand-alone nodes (not part of the road, i.e. to map the physical location of the sensor)? In the first case, they would indeed be usable.

Am Do., 10. Sept. 2020 um 23:08 Uhr schrieb Sasan Amini <[hidden email]>:
Hi Jakob,

thanks for the explanation. I made the bus lane and the lane numbers work. However, regarding the detectors, I disagree with you. The monitoring stations are actually defined on the nodes in JOSM. So in my opinion, they are similar to traffic lights. 

Best,
Sasan

On Thu, Sep 10, 2020 at 8:52 PM Jakob Erdmann <[hidden email]> wrote:
1) currently not possible. Also, according to https://wiki.openstreetmap.org/wiki/Key:monitoring:traffic, the osm objects reference a position next to the road rather than being assigned to an osm way (which would be more useful for extracting detectors).
2) lanes:backward is being evaluated (also lanes:forward and lanes). Note, that 'lanes' must be set in order for the other tags to be evaluated
3) lanes:psv is currenlty not evaluated. However the tags 'busway:right', 'busway:left', 'busway:both' are read

regards,
Jakob

Am Do., 10. Sept. 2020 um 16:04 Uhr schrieb Sasan Amini <[hidden email]>:
Dear all,

I have a question regarding the attributes, more specifically 3 attributes, one can import from OSM using NETCONVERT. 
1) loop detectors: I was trying to import the traffic detectors form OSM which I have added manually as monitoring stations using JOSM. But I can't find a way to import them in my network or as an additional file. Is it possible to import them at all?
2) One other issue is the number of lanes. In JOSM one can add a key to differentiate the number of lanes in opposite direction (lanes:backward). But I think NETCONVERT reads only the key "lanes" to get the number of lanes in both directions. 
3) Bus lanes are also defined with a key "lanes:psv" in OSM. However, the vehicle types allowed/disallowed on the lanes are not affected by this key. 
The bigger problem is actually to find a platform where several people can edit large networks together. Any tips on this aside JOSM are much appreciated.  

Best,
Sasan
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Reply | Threaded
Open this post in threaded view
|

Re: [sumo-user] Netconvert: importing "extra" OSM attributes

Sasan Amini-2
it can be created on any nodes, either on the ways or an isolated node. I define them on nodes that are located on ways. Here is a screenshot that may help. I am just not sure if it can be located on a certain lane and not the way, but that is trivial.  

image.png

On Fri, Sep 11, 2020 at 8:35 AM Jakob Erdmann <[hidden email]> wrote:
Just to make sure I'm not misunderstanding your point: Are they defined on nodes that belong to a <way> which defines the road or are they defined on stand-alone nodes (not part of the road, i.e. to map the physical location of the sensor)? In the first case, they would indeed be usable.

Am Do., 10. Sept. 2020 um 23:08 Uhr schrieb Sasan Amini <[hidden email]>:
Hi Jakob,

thanks for the explanation. I made the bus lane and the lane numbers work. However, regarding the detectors, I disagree with you. The monitoring stations are actually defined on the nodes in JOSM. So in my opinion, they are similar to traffic lights. 

Best,
Sasan

On Thu, Sep 10, 2020 at 8:52 PM Jakob Erdmann <[hidden email]> wrote:
1) currently not possible. Also, according to https://wiki.openstreetmap.org/wiki/Key:monitoring:traffic, the osm objects reference a position next to the road rather than being assigned to an osm way (which would be more useful for extracting detectors).
2) lanes:backward is being evaluated (also lanes:forward and lanes). Note, that 'lanes' must be set in order for the other tags to be evaluated
3) lanes:psv is currenlty not evaluated. However the tags 'busway:right', 'busway:left', 'busway:both' are read

regards,
Jakob

Am Do., 10. Sept. 2020 um 16:04 Uhr schrieb Sasan Amini <[hidden email]>:
Dear all,

I have a question regarding the attributes, more specifically 3 attributes, one can import from OSM using NETCONVERT. 
1) loop detectors: I was trying to import the traffic detectors form OSM which I have added manually as monitoring stations using JOSM. But I can't find a way to import them in my network or as an additional file. Is it possible to import them at all?
2) One other issue is the number of lanes. In JOSM one can add a key to differentiate the number of lanes in opposite direction (lanes:backward). But I think NETCONVERT reads only the key "lanes" to get the number of lanes in both directions. 
3) Bus lanes are also defined with a key "lanes:psv" in OSM. However, the vehicle types allowed/disallowed on the lanes are not affected by this key. 
The bigger problem is actually to find a platform where several people can edit large networks together. Any tips on this aside JOSM are much appreciated.  

Best,
Sasan
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
[hidden email]
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user