NC-JPN is a national committee of Japan.
We have discussed on this item, and direct the following.
(1) write a “workflow” as a total view.
(2) specify elements of each step as system correction, GCP, etc.
(3) need 3-dimensinal information for high accuracy pointing.
(4) check to satisfy specifications on the orbit.
(5) check geometric conversion.
(6) clarify what we should check on the document.
Please consider the sensor characteristics, for example, line sensor (push-bloom type), line sensor with time integration, small area sensor (scan type) and whole area sensor. They may need specific pointing management.
Thank you for your comment.
We transfer this information to Japan Space Systems, the project organization for this subject.
It is stated that the scope covered by this standard is limited to pointing management of optical remote sensors used for earth surface observation. So, is this standard trying to standardize the relationship between pointing requirements and mission requirements?
Thank you for your comment.
We transfer this information to Japan Space Systems, the project organization for this subject.
The workflow should be consider in a life-cycle.
We can refer the followings:
– ISO 14040:2006, Environmental management — Life cycle assessment — Principles and framework https://www.iso.org/standard/37456.html
– ISO 14044:2006, Environmental management — Life cycle assessment — Requirements and guidelines https://www.iso.org/standard/38498.html
Does your comment “The workflow should be consider in a life-cycle.” refer to the definition of the term life cycle in “3 Terms and definitions” of ISO 14040:2006, “consecutive and interlinked stages of a product system, from raw material acquisition or generation from natural resources to final disposal”?
My meaning is “a life-cycle is requirement-design-manufacture-test-operation/services.
The URLs may be not adequate.
I would like to say that a workflow should be a total life-cycle of development.
I beg your understanding.
There is a explanation video in “3-5 Reference Architecture Model for Industry 4.0 and International Collaboration” in this forum.
From the time point 25:46 minutes, he explains a life-cycle in the architecture.
Thank you for giving me more information.
The video shows System Architecture China that has a cubic structure. One axis is “life-cycle”.
I think I got a visual image about “a life-cycle in the architecture”.
Thank you for your reply.
I understand “a life-cycle is requirement-design-manufacture-test-operation/services”.
“Purpose and justification” says that the development of this standard will create the markets of meteorology, agriculture, fishery, transportation, etc. I do support such idea to help industry grow with the usage of earth observation data.
Hence I come to have a question from the user point of view, “What change will this standard bring to the end users?”
Here is an example.
Tellus is a popular Japanese earth observation data platform. It provides, for example, ALOS AVNIR-2 image data. Its image product format is described in the details as in the link below https://www.eorc.jaxa.jp/ALOS/alos-ori/doc/AVNIR-2_ORI_format_jp.pdf
(in Japanese)
The header file includes many information already. I’d like to know “What will this standard add or change to the current available information?”
NC-JPN is a national committee of Japan.
We have discussed on this item, and direct the following.
(1) write a “workflow” as a total view.
(2) specify elements of each step as system correction, GCP, etc.
(3) need 3-dimensinal information for high accuracy pointing.
(4) check to satisfy specifications on the orbit.
(5) check geometric conversion.
(6) clarify what we should check on the document.
Please consider the sensor characteristics, for example, line sensor (push-bloom type), line sensor with time integration, small area sensor (scan type) and whole area sensor. They may need specific pointing management.
Thank you for your comment.
We transfer this information to Japan Space Systems, the project organization for this subject.
It is stated that the scope covered by this standard is limited to pointing management of optical remote sensors used for earth surface observation. So, is this standard trying to standardize the relationship between pointing requirements and mission requirements?
Thank you for your comment.
We transfer this information to Japan Space Systems, the project organization for this subject.
The workflow should be consider in a life-cycle.
We can refer the followings:
– ISO 14040:2006, Environmental management — Life cycle assessment — Principles and framework
https://www.iso.org/standard/37456.html
– ISO 14044:2006, Environmental management — Life cycle assessment — Requirements and guidelines
https://www.iso.org/standard/38498.html
Does your comment “The workflow should be consider in a life-cycle.” refer to the definition of the term life cycle in “3 Terms and definitions” of ISO 14040:2006, “consecutive and interlinked stages of a product system, from raw material acquisition or generation from natural resources to final disposal”?
My meaning is “a life-cycle is requirement-design-manufacture-test-operation/services.
The URLs may be not adequate.
I would like to say that a workflow should be a total life-cycle of development.
I beg your understanding.
There is a explanation video in “3-5 Reference Architecture Model for Industry 4.0 and International Collaboration” in this forum.
From the time point 25:46 minutes, he explains a life-cycle in the architecture.
Thank you for giving me more information.
The video shows System Architecture China that has a cubic structure. One axis is “life-cycle”.
I think I got a visual image about “a life-cycle in the architecture”.
Thank you for your reply.
I understand “a life-cycle is requirement-design-manufacture-test-operation/services”.
“Purpose and justification” says that the development of this standard will create the markets of meteorology, agriculture, fishery, transportation, etc. I do support such idea to help industry grow with the usage of earth observation data.
Hence I come to have a question from the user point of view, “What change will this standard bring to the end users?”
Here is an example.
Tellus is a popular Japanese earth observation data platform. It provides, for example, ALOS AVNIR-2 image data. Its image product format is described in the details as in the link below
https://www.eorc.jaxa.jp/ALOS/alos-ori/doc/AVNIR-2_ORI_format_jp.pdf
(in Japanese)
The header file includes many information already. I’d like to know “What will this standard add or change to the current available information?”
Please consider to provide GCP examples in “(2) specify elements of each step as system correction, GCP, etc.” Here is sample information about GCP.
https://www.researchgate.net/publication/228806397_GCP_Requirement_For_High-Resolution_Satellite_Mapping
https://www.usgs.gov/landsat-missions/ground-control-points
https://www.isprs-ann-photogramm-remote-sens-spatial-inf-sci.net/V-2-2020/15/2020/isprs-annals-V-2-2020-15-2020.pdf
Thank you for the information of GCP.