Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[sumo-user] Surprising underground edges from OSM with --osm.layer-elevation

Hello,

I'm trying to generate elevation data from OSM using:

    netconvert --osm.elevation --osm.layer-elevation 6.0 ...

My understanding is that this should put OSM nodes and ways without a "layer" attribute on ground level, those with "layer=1" at 6m elevation, etc. But I'm observing some results that I can't make sense. Some ways are elevated or, worse, placed underground.

For example, way 538879518 has no layer attribute. Its constituent nodes are 34710075406186415 and 5215366122, none of which have a layer attribute set.

When I run this through netconvert, it splits this way into two edges whose lanes have heights ranging from -1.91m to -5.01m:

    <edge id="538879514#0" from="34710075" to="406069108" name="Queens Quay West" priority="7" type="highway.secondary">
        <lane id="538879514#0_0" index="0" disallow="tram rail_urban rail rail_electric pedestrian ship" speed="11.11" length="3.57" shape="1007.90,351.67,-1.91 1006.33,350.86,-5.01">
            <param key="origId" value="538879514"/>
        </lane>
    </edge>
    <edge id="538879514#1" from="406069108" to="5215360015" name="Queens Quay West" priority="7" type="highway.secondary">
        <lane id="538879514#1_0" index="0" disallow="tram rail_urban rail rail_electric pedestrian ship" speed="11.11" length="10.74" shape="1001.54,348.65,-5.01 991.57,344.67,-4.98">
            <param key="origId" value="538879514"/>
        </lane>
    </edge>

I would have expected this way to be at ground level.

What's going on here? Why is this (surface level) way being placed below ground? Is this a bug? Is there a workaround?

Thanks!
  - Dan

Back to the top