initial planning

[slawler]

From planning discussion:

*default item generation: small bounding box (at 0,0) and current datetime

-hecstac
	-ras  (core functionality, stable)
  -extensions
	  - v1
	  - v2
  -item (from prj & files)
	  - geom: current geometry vs unioned geometries ?
	  - datetime: last edited (if available)

  -asset (from any ras file)

	-hms (core functionality, stable)
		-[see ras]

	-event (relatively unstable)
		-extensions
			v1/ focus on results / outputs
		-ras.asset (ras plan output)
		-hms.asset (hms output)

		-ras.item (link: source model item)
		-hms.item (link: source model item)

	-utils
		-hec-text parser
		-s3-converters
		-file-grabber/file-search
		-api
		-validation?

	-collections (relatively unstable)
		-summarize data
		-assets (collection level)

[mdeshotel]

should we share a consts.py and errors.py, for the entire repo? or should ras have its own and hms have its own?

[nick-j-roberts]

I am initially inclined towards having ras and hms have their own constant and error files (would this be subclasses of the Exception class that we would want to raise? or is it something else?), just because trying to import things across directories is annoying in python. Then I think about how events is shown as importing classes from ras and hms and that makes me think that importing from other directories is going to have to happen regardless

[mdeshotel]

yes, subclasses of the Exception class.