Re: [GRASS-dev] gunittest test temporal dataset

[Stefan Blumentrath]

Hi again,

 
Looking at my example I see that there is in fact a possibility to check 
existence of an STDS without t.list. See:
https://github.com/NVE/actinia_modules_nve/blob/036a4c85664a9015d5ca13ed6f40bdcc79bbfcb2/src/temporal/t.rast.reclass/t.rast.reclass.py#L294-L316
 
You could basically do:
 
import grass.temporal as tgis
# Initialize TGIS
tgis.init()
# Connect to TGIS DB
dbif = tgis.SQLDatabaseInterfaceConnection()
dbif.connect()

output_strds = tgis.factory.dataset_factory("strds", "MY_STRDS_NAME")
output_strds_exists = output_strds.is_in_db(dbif)
assertTrue(output_strds_exists)
 
Maybe worth considering to add a method for that in the unittest module!?!
 
Cheers,
Stefan
 
 

Gesendet: Montag, 27. März 2023 um 14:15 Uhr
Von: "Luca Delucchi" 
An: "Stefan Blumentrath" 
Cc: "GRASS-dev" 
Betreff: Re: [GRASS-dev] gunittest test temporal dataset

 

Il lun 27 mar 2023, 13:21 Stefan Blumentrath 
mailto:stefan.blumentr...@gmx.de]> ha scritto:

Hi Luca,
 
Hi Stefan,

 
Not that I am aware of. I use to parse output from t.list to check if a STDS 
exists...
 
Yes this was my idea too. Do you have an example?

 
Cheers
Stefan
 
 
Cheers
Luca

 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] gunittest test temporal dataset

[Luca Delucchi]

Il lun 27 mar 2023, 13:21 Stefan Blumentrath  ha
scritto:

> Hi Luca,
>

Hi Stefan,

>
> Not that I am aware of. I use to parse output from t.list to check if a
> STDS exists...
>

Yes this was my idea too. Do you have an example?

>
> Cheers
> Stefan
>
>

Cheers
Luca

>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] GSoC 2023: Contributor Proposals Submission Started | Deadline - April 4th, 2023 1800 UTC

[Veronica Andreo]

FYI :)

GSoC Contributor proposal period has started!

Have a look at GRASS GIS ideas page for 2023 and get in touch if you are
interested: https://trac.osgeo.org/grass/wiki/GSoC/2023


-- Forwarded message -
De: Rajat Shinde via Discuss 
Date: jue, 23 mar 2023 a las 3:09
Subject: [OSGeo-Discuss] GSoC 2023: Contributor Proposals Submission
Started | Deadline - April 4th, 2023 1800 UTC
To: OSGeo-SoC 
Cc: gsoc-adminosgeo.org , OSGeo Discussions <
disc...@lists.osgeo.org>


Dear All,

FYI, the GSoC Contributor proposal period has started. This email is a
gentle reminder to the potential GSoC contributors interested in
participating in GSoC 2023.

*If you are a contributor interested in contributing to the geospatial open
source with OSGeo as an umbrella organization, then this is high time*:

   1. To go through the *OSGeo GSoC 2023 project ideas list* [1]. Make sure
   to check the list frequently, as it is being updated regularly with new
   ideas.
   2. *Contact the project mentors* via the Developers' mailing list or the
   community chat channels to discuss the project idea/ideas of your
   interest.
   3. Start working on the *proposal draft* and share it with the community
   as soon as possible to receive feedback and comments.

Please go through the GSoC Contributors/Students Guide [2] to get an
overall understanding of the problem. *From Google admins:
"GSoC Contributors who engage with their organization early (and often)
are more likely to be accepted and then succeed"*.

Remember to submit your proposal well in advance, so that you can make the
most out of the feedback from mentors and the community at large and refine
your proposal until the final deadline. Read the application instructions
here [3]. The same page contains all the info you need before taking
action, so please read it carefully.

Please note that the contributor application period starts *March 20, 2023
- 18:00 UTC* and all the student proposals must be submitted before *April
4, 2023 - 18:00 UTC*. Please don't wait for the deadline. Refer to the
GSoC Timeline
[4] for more details.

We are looking forward to working with you toward another awesome edition of
 GSoC! Good luck everyone!

Please forward this email to your developer and community mailing list.

Kind regards,
Your OSGeo GSoC Admins

[1]. https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2023_Ideas

[2]. https://google.github.io/gsocguides/student/
[3]. https://wiki.osgeo
.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#Application_instructions
[4]. https://developers.google.com/open-source/gsoc/timeline
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] gunittest test temporal dataset

[Stefan Blumentrath]

Hi Luca,

 

Not that I am aware of. I use to parse output from t.list to check if a STDS exists...

 

Cheers

Stefan

 
 

Gesendet: Montag, 27. März 2023 um 11:31 Uhr
Von: "Luca Delucchi" 
An: "GRASS-dev" 
Betreff: [GRASS-dev] gunittest test temporal dataset

Hi devs,

is there a way to test if a temporal dataset exists or not?
something like assertRasterExists

in the case it doesn't exist it could be useful?

--
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev



___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] gunittest test temporal dataset

[Luca Delucchi]

Hi devs,

is there a way to test if a temporal dataset exists or not?
something like assertRasterExists

in the case it doesn't exist it could be useful?

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev