Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gnome-maps gnome-maps
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 147
    • Issues 147
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-mapsgnome-maps
  • Issues
  • #291
Closed
Open
Issue created Aug 23, 2020 by Marcus Lundblad@mlundbladMaintainer

Not possible to set negative elevation when editing OSM objects

Currently in the OSM edit dialog we have some fields classified as integers, these are rendered as combo boxes. At the momement they are all limited to >= 0. The result is that if you edit a place with a negative value for the "ele" tag, such as a sea trench, or places on land, but below sea level. They are set to zero in the view and it's not possible to go lower. We should probably introduce a distinction for rendering editable fields as signed or unsigned integers, as a tag like "population" we still want to prevent setting a negative value.

Assignee
Assign to
Time tracking