Skip to content

Latest commit

 

History

History
55 lines (44 loc) · 2.5 KB

README.md

File metadata and controls

55 lines (44 loc) · 2.5 KB

Google libphonenumber plugin for JOSM

The code repository contains only the needed parts for the connection between the parser library and JOSM. Please find the repacked libphonenumber under gabortim/josm-libphonenumber.

For changes, see Changelog.md.

Features

The plugin gives the JOSM validator many tests and quick fixes:

  • validate numbers against location, although the localization is rough as it's a limitation of the JOSM internal territories dataset
  • fixes wrongly separated numbers (comma used instead of semicolon)
  • able to change tagging scheme to the newer contact: prefix one via the validator and via the properties' dialog popup menu
  • moves mobile numbers to mobile tag
  • adds an easy, overpass type download action to the toolbar for downloading all objects with any phone key in the current view
  • (BETA) provides autofix for all the above for a more convenient experience

Installation

Download the phonenumber plugin from JOSM as usual.

Requires Java 17+.

Usage

Just run the validator, the messages will pop up.

To activate the autofix capability:

  1. Enable expert mode - see JOSM wiki
  2. Check the autofix combobox in the validator tab.

Contribution

Contributions are welcomed. When you encounter an issue or have an improvement idea, don't hesitate to report it to GitHub or JOSM Trac :)

I'd like to make the code more testable to extend the test coverage.

Project setup

To be able to sync the project dependencies after cloning, you need a few extra steps, unfortunately.

  1. Go to your GitHub user profile dev settings: https://github.com/settings/tokens
  2. Generate a new classic token with read:packages permission.
  3. Create a gradle.properties file
  4. Add these lines to the file:
    • GH_ACTOR=<your GH username>
      GH_PACKAGE_REPO_TOKEN=<the newly generated token in step 2.>

Translation

Download the latest .pot file from the CI/CD artefacts and translate it locally. After the translation is done, create a Merge Request with the file to the i18n directory.

Existing translations can be modified in the same way.