Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harmonize and improve the way we specify supported projection in configuration #9249

Open
6 tasks
MV88 opened this issue Jun 26, 2023 · 0 comments
Open
6 tasks

Comments

@MV88
Copy link
Contributor

MV88 commented Jun 26, 2023

Description

this issue was created from here

Currently there is cluncky way of specifying which projections a tool can use,
we should do a review on the current implementation and change the way we express that configuration.

currently you have to define extra projection in projectionDefs array
add them in localConfig of the tool

"additionalCRS": {
  "EPSG:3003": {
    label: "Monte Mario"
  }
},
"filterAllowedCRS": [ "EPSG:4326", "EPSG:3857"],

some tools to consider

  • CRSSelector
  • LongitudinalProfileTool
  • MousePosition

it can be enough
to have this

"avaliableCRS": [
  { "label": "EPSG:4326", "value": "EPSG:4326" },
  { "label": "EPSG:3857", "value": "EPSG:3857" },
  { "label": "EPSG:3003", "value": "EPSG:3003" }
]

What kind of improvement you want to add? (check one with "x", remove the others)

  • Minor changes to existing features
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

Other useful information

@MV88 MV88 added this to the 2023.02.00 milestone Jun 26, 2023
@MV88 MV88 mentioned this issue Jun 26, 2023
12 tasks
@tdipisa tdipisa removed this from the 2023.02.00 milestone Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants