1. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818569 0 1 0 0

  2. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818490 0 1 0 0

  3. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818351 0 1 0 0

  4. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818299 0 1 0 0

  5. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818276 0 1 0 0

  6. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818211 0 1 0 0

  7. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818153 0 1 0 0

  8. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146818012 0 1 0 0

  9. no good match with DEM / opentopomap - the edit should be a better fit, but locals pls. check carefully and pot. correct. TXs.

    Closed
    #146816171 0 1 0 0

  10. no good match with DEM / opentopomap - the edit should be a better fit, but locals pls. check carefully and pot. correct. TXs.

    Closed
    #146816137 0 1 0 0

  11. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146815980 0 1 0 0

  12. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146815891 0 1 0 0

  13. Location did not natch DEM / opentopomap in any way - the edit should be a better fit, but locals pls. check carefully and pot. correct. TXs.

    Closed
    #146814251 0 1 0 0

  14. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146813959 0 1 0 0

  15. was duplicate, in the wrong place anyway

    Closed
    #146813913 0 0 1 0

  16. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146813612 0 1 0 0

  17. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146813588 0 1 0 0

  18. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146813543 0 1 0 0

  19. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146796359 0 1 0 0

  20. ele wrong by a factor of about 3, which hints at feet figures put into the OSM elevation field that requires meter values. Feet figures obviously create havoc in the OSM data.

    Closed
    #146796345 0 1 0 0