-
Notifications
You must be signed in to change notification settings - Fork 77
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
Layer submission process, per-layer metadata #135
Comments
And we should ask for all these fields if they can be found, as described in #134:
|
@jywarren I want to work on it |
Please do! Thanks!
…On Fri, Mar 8, 2019, 11:45 PM Avkaran Singh ***@***.***> wrote:
@jywarren <https://github.com/jywarren> I want to work on it
thanks : )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ_X5u3NhaBZmOheB_NMbhmSX0-Bcks5vUzxagaJpZM4bltsH>
.
|
@jywarren please explain to me more about this what I have to do? I am not getting a point. I know Only I have to write documentation about this 3 point But Don't know How to start please give me way |
Noting "requests" urls as in #138 too! |
Noting bounding box metadata ideas in #110 (comment) ! |
We should create a clear process for:
Maybe an issue template, and maybe a table or JSON file showing all layers with metadata existing/missing? See metadata issue in #134 ! 👍
And see new layer issues here:
new-layer
The text was updated successfully, but these errors were encountered: