And , I want know , Nomally, when storing data , All file (.txt, .jpg, .tiff , .iso19115 ) will be stored in 1 folder in system or They will be stored in the distribution directorydist (ex : landsat metadata folder, modis metadata folder, image folder ... )?
On Thu, Jul 7, 2016 at 9:04 AM, phuong hao nguyen thi < [email protected]> wrote: > Hello Martin, > Thanks so much. > >>Do you have an idea about how to allow such configuration? > As you suggest , I think I will creat a configue for directory , when the > programe install on a other computer , It will ask the direction that save > geotiff, modis , image ... . How do you feel ? > >>In table 6, we can see that the SummaryRecord title attribute should be > taken from Metadata.identificationInfo.citation.title. We should modify > the code so that it follow those recommendations. > >>I would like to know, how were determined the fields in SummaryRecord > and in Element (or BoundingBox)? Do they come from those files? > The present, I set the title is file name :) (I will correct it as ISO > 19115) but I have to all queryables as in the table or only a few that we > need ? > >> The search should be done on the service side. The server may have a > very large amount of metadata; transfering all of them on the client > side would be too costly. > Was it your question? Maybe I misunderstood? > Yes , It was my question , I have created search on service too, > suspended : bbox, date, format but I don't know how to combine them ? > Do you guide me ? > Thanks > Hao > > On Thu, Jul 7, 2016 at 12:48 AM, Martin Desruisseaux < > [email protected]> wrote: > >> Hello Hao >> >> Le 06/07/16 à 02:37, phuong hao nguyen thi a écrit : >> > In my computer, I place the Geotiff file in forder geotiff and Modis >> file >> > in forder modis. I use ReadXML and scan all file in 2 directory and read >> > them . >> >> Thanks for the indication. I see that the folder are currently >> hard-coded to "/home/haonguyen/data/". This is fine for testing purpose, >> but the final version will of course need to let the user choose his >> directory. Do you have an idea about how to allow such configuration? >> >> >> > The part, mapping from ISO 19115 metadata and the SummaryRecord >> returned by >> > the CSW. I don't understand you. I use ReadXML to read file and set to >> > SummaryRecord . Can you guide me ? >> >> I see that ReadXML extract values from ISO 19115 metadata and gives them >> to the SummaryRecord constructor. This is the idea, but I suggest the >> following modifications: >> >> * Instead of extracting ISO 19115 values in ReadXML, I suggest to >> extract them in the SummaryRecord constructor (the constructor would >> expect an org.opengis.metadata.Metadata object in argument). This >> would avoid the duplication of code that we currently see in >> ReadXML.listModis() and ReadXML.listGeotiff() methods. >> * The Element class should be renamed BoundingBox. >> * The mapping from ISO 19115 to SummaryRecord should follow the OGC >> recommendations: >> o Go on http://www.opengeospatial.org/standards/cat >> o Download document 07-045 (OGC Catalogue Services Specification >> 2.0.2 - ISO Metadata Application Profile (1.0.0)) >> o Scroll down to table 6 at page 41. >> >> In table 6, we can see that the SummaryRecord title attribute should be >> taken from Metadata.identificationInfo.citation.title. We should modify >> the code so that it follow those recommendations. >> >> I would like to know, how were determined the fields in SummaryRecord >> and in Element (or BoundingBox)? Do they come from those files? >> >> * http://schemas.opengis.net/csw/2.0.2/record.xsd >> * http://schemas.opengis.net/ows/1.0.0/owsCommon.xsd >> >> For example, owsCommon.xsd define the BoudingBox type with two elements: >> LowerCorner and UpperCorner. But the Element class in VNSCweb is defined >> with westBoundLongitude, eastBoundLongitude, etc. Can you give me a link >> (other than ISO 19115) where those elements were defined? >> >> >> > And the part search, I want know, Will we search in the client or in >> > service ? >> >> The search should be done on the service side. The server may have a >> very large amount of metadata; transfering all of them on the client >> side would be too costly. >> >> Was it your question? Maybe I misunderstood? >> >> Martin >> >> >> >
