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

Add newer Hungarian ortophotos #10224

Closed
wants to merge 4 commits into from
Closed

Conversation

Yogurt4
Copy link
Contributor

@Yogurt4 Yogurt4 commented Apr 30, 2024

A newer layer of the official all-country orthophotos were generated and now are available.

@tordans
Copy link
Collaborator

tordans commented Apr 30, 2024

The aerial imagery is something that has to be added to the editor layer index. They will be pulled from there.

Please make separate PRs for the other changes in here.

@Yogurt4
Copy link
Contributor Author

Yogurt4 commented Apr 30, 2024

Hi,

The aerial imagery is something that has to be added to the editor layer index. They will be pulled from there.

And where can I find that? This file was the only one I found the old layers in, both by name and by id.

Please make separate PRs for the other changes in here.

I don't understand why Github made a PR with 4 commits (including my previous PR that is already merged in the main repo). Or is it compulsory to create a new fork for each modification?

@danieldegroot2
Copy link
Contributor

danieldegroot2 commented Apr 30, 2024

where can I find that?

See https://github.com/osmlab/editor-layer-index/tree/gh-pages/sources/europe/hu

or create issue here https://github.com/osmlab/editor-layer-index/issues ('new issue' button, top right)

is it compulsory to create a new fork for each modification?

No, you can create a new branch on your existing fork for separate PRs to the same repo. See https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
But in this case you should create a fork of editor-layer-index repo instead and add a new branch there.

@tordans
Copy link
Collaborator

tordans commented May 3, 2024

I will closed this PR with reference to #10224 (comment)

@tordans tordans closed this May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants