ideas to increase visibility

[guidorice]

Greetings 👋🏽 I'm interested in contributing here. I will open separate issues, after I get a bit more comfortable with Julia.

Have you considered:

• Move this repo into the https://github.com/JuliaGeo organization? STAC is generally useful in geospatial. It took me a bit to find it here in the JuliaClimate org.
• Publish it to juliapackages and juliahub ?

[Alexander-Barth]

Thank you for your interest!

Concerning point 1 (which was also raised here: https://github.com/JuliaClimate/meta/issues/15#issuecomment-943148422 ), I believe that most users will come from this community and there are several similar packages (package for data access) already in JuliaClimate.

Point 2: yes I agree this package should be registered.

[guidorice]

@Alexander-Barth thanks for that link. I'll close this issue, and in future, hope to be contributing some new ideas and pull requests. 👍🏽

[Alexander-Barth]

That would be great ! As you work for radianearth, maybe you don't mind if I ask you a question (in future) if it should be unclear for me what would be the best way to implement the spec.

Thanks for reaching out!

By the way, here is the request for package registration: https://github.com/JuliaRegistries/General/pull/59089

(the STAC name is a bit too short, but there are other packages with a similar short name. Hopefully it is ok.)

[guidorice]

@Alexander-Barth, sure I will try to help with any questions. I am learning more stac every day :) Co-incidentally, the Cloud-Native Geospatial Outreach Event just happened and there were a number of talks about stac: https://youtube.com/playlist?list=PLQsQNjNIDU87yUFyKy1seaiRps389RPwk Some of the talks give overviews of the various python packages in the ecosystem.

[visr]

@Alexander-Barth do you mind triggering the package registration again? Automatic registration is blocked by the package name, but usually a comment like https://github.com/JuliaRegistries/General/pull/59089#issuecomment-1108567359 (with [noblock] added) is enough. After the 3 day wait we can request a manual merge in #pkg-registration on Slack.

[Alexander-Barth]

OK, I just re-triggered the registration at https://github.com/JuliaRegistries/General/pull/75262 .

Please feel free to leave a comment there if you agree, or not, that STAC is a suitable name for a Julia package.

[visr]

Thanks! Yes I think STAC is good. The only real alternative would be import SpatioTemporalAssetCatalog as STAC, which isn't very catchy. I think your comment should be edited to add [noblock], although I'm not sure that applies if it already gets autoblocked.

The autoblock triggers quite often, and usually nobody really opposes it. But with the traffic in General nobody sees these cases, hence the General repo readme suggest to ask a merge after 3 days in Slack #pkg-registration.

[visr]

@Alexander-Barth could you confirm in #pkg-registration or on the issue in General that you wish to retain the name after the latest suggestion? Just a quick confirmation is enough and they'll merge.

[Alexander-Barth]

Thanks @visr for your help in getting this package registered!