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

CRSs supported in vector import #10750

Closed
mahmoudadel54 opened this issue Jan 14, 2025 · 0 comments · Fixed by #10751
Closed

CRSs supported in vector import #10750

mahmoudadel54 opened this issue Jan 14, 2025 · 0 comments · Fixed by #10751
Assignees
Milestone

Comments

@mahmoudadel54
Copy link
Contributor

Image

Clarify for the Import functionality what format strictly require 4326, it seems there is an error in how parenthesis are used in the info text above

@mahmoudadel54 mahmoudadel54 self-assigned this Jan 14, 2025
mahmoudadel54 added a commit to mahmoudadel54/MapStore2 that referenced this issue Jan 14, 2025
…6 in import vector layers

Description:
- edit translations
@mahmoudadel54 mahmoudadel54 linked a pull request Jan 14, 2025 that will close this issue
12 tasks
@mahmoudadel54 mahmoudadel54 added this to the 2025.01.00 milestone Jan 14, 2025
mahmoudadel54 added a commit to mahmoudadel54/MapStore2 that referenced this issue Jan 15, 2025
MV88 pushed a commit that referenced this issue Jan 21, 2025
* #10750: clarify the formats that stricktly require 4326 in import vector layers
Description:
- edit translations

* #10750: remove unnecessary space in translations
@ElenaGallo ElenaGallo self-assigned this Jan 22, 2025
mahmoudadel54 added a commit that referenced this issue Feb 20, 2025
* #10750: clarify the formats that stricktly require 4326 in import vector layers
Description:
- edit translations

* #10750: remove unnecessary space in translations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants