t.copy(1grass)

πŸ’– t.copy β€” the glow-up dupe for your space time datasets πŸ’–

okay bestie, welcome to t.copy from the GRASS User's Manual ✨ this one's a lil icon in the temporal toolkit and honestly? she ate.

🌸 NAME 🌸

t.copy β€” makes a copy of a space time raster dataset. periodt πŸ’…


πŸŽ€ KEYWORDS πŸŽ€

temporal, copy, time β€” yes she's filed under all three, very organized of her 🫢


✨ SYNOPSIS ✨

t.copy
t.copy --help
t.copy [-c] input=name  [type=name]  output=name  [--overwrite]
[--help]  [--verbose]  [--quiet]  [--ui]

πŸ¦‹ Flags:

  • -c β€” also copies the maps of the space-time dataset πŸ’– heads up tho: by default the old maps are only registered in the new dataset, so if you actually want the map files themselves duplicated, this is the flag, no cap.
  • --overwrite β€” lets output files overwrite files that already exist πŸ‘‘ dangerous lil queen, use wisely
  • --help β€” prints the usage summary πŸ™ˆ
  • --verbose β€” verbose module output, she'll tell you everything
  • --quiet β€” quiet module output, she'll tell you nothing 🀫
  • --ui β€” forces the GUI dialog to launch πŸ–₯️✨

🌈 Parameters:

  • input=name [required] β€” name of the input space time dataset (the one you're copying, duh)
  • type=name β€” type of the input space time dataset
    • Options: strds, str3ds, stvds
    • Default: strds
  • output=name [required] β€” name of the output space time dataset (the new baddie you're creating)

πŸ’œ DESCRIPTION πŸ’œ

so the whole ~purpose~ of t.copy is to make a copy of a space time dataset. that's it. that's the job. and she does it flawlessly πŸ’…

the new space time dataset lands in the current mapset, but the old one can chill in a different mapset as long as that mapset is in the search path. so like, she's flexible, she's well-traveled, she gets around 🌍

now here's the tea: if you pass the -c flag, the maps of the old space time dataset also get copied over to the current mapset 🫢 but if you don't pass it, the original maps are just simply registered in the temporal database β€” no files moved, just vibes recorded πŸ“

and the new copies? same name as the old maps. no renaming, no rebranding, keeping it consistent, queen behavior πŸ‘‘


πŸ”₯ NOTES πŸ”₯

a fully qualified name for the input space-time dataset is only required if space-time datasets with the same name exist in different mapsets. otherwise bestie, keep it simple, just the name ✨ iykyk


πŸ“ EXAMPLE πŸ“

in the North Carolina sample dataset, with the separately available mapset modis_lst included, we're copying the space-time raster dataset LST_Day_monthly@modis_lst to the current mapset user1. watch her work πŸ˜­πŸ’–

g.mapsets mapset=modis_lst operation=add
t.copy input=LST_Day_monthly@modis_lst type=strds output=LST_Day_monthly

look at that. clean. iconic. no notes 🌟


πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, go show them love too:

  • t.rast.extract
  • t.rast3d.extract
  • t.vect.extract
  • t.info

🌸 AUTHOR 🌸

Markus Metz, mundialis β€” thank you for this absolute gift, we are forever grateful 🫢


🧚 SOURCE CODE 🧚

Available at: t.copy source code (history)

Latest change: Friday Feb 07 19:16:09 2025 in commit: a82a39f673b97fafcfce1604dc3e6015cb96487a

Main index | Temporal index | Topics index | Keywords index | Graphical index | Full index


and that's the whole page bestie, you're officially a t.copy scholar now πŸŽ“βœ¨

okay byeee, this was t.copy(1grass) from the GRASS 8.5.0 Reference Manual, Β© 2003-2026 GRASS Development Team β€” GRASS 8.5.0, mwah πŸ’‹ slay, go copy some datasets responsibly πŸŒˆπŸ’–

πŸ“¦ where this page comes from