[IGS-DCWG-100] NRCan XML Site Log File Feedback and GSAus Recommendation.....

Thu Feb 12 07:02:27 PST 2015

DCWG Members,

We agree that the IGS should have an XML formatted site log.  We would like to see an Issue Of Data Station (IODS) counter (0-7) added to the current specification. This counter would increment every time there is a significant site log change and it would be used to synchronize real-time RTCM-MSM observation streams and IGS station site logs.  

Otherwise, the SOPAC XML site logs look fine and we are happy to adopt the work of the DCWG.

We are also interested in the SOPAC "Real Time Site Log". We believe that a summary of the site log could be used to: verify RINEX file headers (for example, by the NRCan Ultra Rapid process) and used by real-time applications to verify the RTCM-MSM observation data streams etc.

We agree with the GSAus recommendation that the discussion concerning XML formatted geodetic information could/should be broadened. 

NRCan are willing to contribute to the development of an XML formatted Geodetic Position Report.  We see a need for this message as there does not appear to be an widely adopted standard.  

>From a quick review it looks like there are several existing formats that define a geodetic position or at least a geographic position record. 

For example:

1) ISO 19111 (Mike Craymer from NRCan is a member of this group)
2) GIS vendors have defined a GML format
3) NGS (OPUS) have defined an XML Position Report format
4) RTCM and NMEA are currently developing and documenting a real-time Geodetic Position and Baseline Vector Messages 
5) GSAus and others

If there is interest in defining an XML Geodetic Position Report Message, and other geodetic messages, we will participate.

Regards,

Ken MacLeod and Stuart Elson
Natural Resources Canada

-----Original Message-----
From: igs-dcwg-bounces at igscb.jpl.nasa.gov [mailto:igs-dcwg-bounces at igscb.jpl.nasa.gov] On Behalf Of igs-dcwg-request at igscb.jpl.nasa.gov
Sent: February 11, 2015 06:20
To: igs-dcwg at igscb.jpl.nasa.gov
Subject: IGS-DCWG Digest, Vol 6, Issue 3

Send IGS-DCWG mailing list submissions to
	igs-dcwg at igscb.jpl.nasa.gov

To subscribe or unsubscribe via the World Wide Web, visit
	http://igscb.jpl.nasa.gov/mailman/listinfo/igs-dcwg
or, via email, send a message with subject or body 'help' to
	igs-dcwg-request at igscb.jpl.nasa.gov

You can reach the person managing the list at
	igs-dcwg-owner at igscb.jpl.nasa.gov

When replying, please edit your Subject line so it is more specific than "Re: Contents of IGS-DCWG digest..."

Today's Topics:

   1. [IGS-DCWG-99] Re: Proposed scope [SEC=UNCLASSIFIED]
      (Melinda Squibb)

----------------------------------------------------------------------

Message: 1
Date: Tue, 10 Feb 2015 16:48:05 -0800
From: Melinda Squibb <msquibb at ucsd.edu>
Subject: [IGS-DCWG-99] Re: Proposed scope [SEC=UNCLASSIFIED]
To: Nicholas.Brown at ga.gov.au, IGS-DCWG at igscb.jpl.nasa.gov
Cc: artur.oruba at gugik.gov.pl, Meertens at unavco.org,
	mark.caissy at nrcan-rncan.gc.ca, Gary.Johnston at ga.gov.au,
	ybock at ucsd.edu, mize at unavco.org
Message-ID: <54DAA6C5.9060709 at ucsd.edu>
Content-Type: text/plain; charset="windows-1252"

Nicholas,

The design of the sitelog xml was before my time here but I have written other schemas and corresponding software representing our data.  I tend to make mine simpler (I agree completely with the multiple definitions and multiple namespaces complaints) - to use fewer schemas.

The enumerations for this set of schemas for sitelogs haven't been maintained, but certainly need to be updated.
There should also be an automated process for updating the receiver and antenna types
  (I have been doing this manually for our processing metadata schema set which is not really sustainable).

We should add the omitted fields that you mentioned, but I would prefer to make all these changes at once, rather than piecemeal.

Our processing metadata schema set is available at:
http://sopac.ucsd.edu/ns/geodesy/2014/
It does have more up-to-date enumerations(in listTypes.xsd).
This does not have all sitelog fields from the database, only those that are relevant to our processing.

Do you have a link to your GeodesyML schema?

   -Mindy

On 2/9/15 4:35 PM, Nicholas.Brown at ga.gov.au wrote:
>
> Hi all,
>
> My name is Nicholas Brown from Geoscience Australia.
>
> Based on discussions I have had with Gary Johnston and other 
> jurisdictional representatives we believe there is an opportunity to 
> broaden the scope of the IGS DCWG Project to include more than just 
> site log metadata.
>
> Please review our thoughts and suggestions below and feel free to ask 
> any questions.
>
> We recognise that endorsing something much broader than just the IGS 
> Site Log XML schema may seem to be an extra word load, however, 
> development of Standards in isolation could prove to be more costly in 
> the long run.
>
> *Scope and Suggestions *
>
> ?Currently IGS have defined the scope of the IGS DCWG Project to be 
> the development of Standard (close to SOPAC Site Log schema) to 
> provide a means of ?transmitting IGS site log metadata between data 
> centers using XML?.
>
> ?We believe this is a good opportunity (and time) to think more 
> broadly than just the IGS site logs.
>
> ?As Gary Johnston mentioned to me following a presentation he saw from 
> Bernd Richter who was presenting on the importance of  metadata, there 
> is a need for Standards not just for Site Logs but for all Geodesy 
> data and these Standards need to be well integrated with other 
> international standards. This will provide for metadata transfer of 
> all Geodesy data and associated information.
>
> ?In recent years, Australia and New Zealand, under the auspices of the 
> Intergovernmental Committee on Surveying and Mapping (ICSM), have 
> continued to develop a standards-based data model to facilitate the 
> encoding and transfer of geodetic data. This has led to the creation 
> of a draft Geography Markup Language (GML) Application Schema known as 
> *GeodesyML*, for the transfer of geodetic information.
>
> ?GeodesyML incorporates the geodetic elements most commonly 
> transferred in the context of national datum establishment and 
> maintenance.
>
> ?While GeodesyML doesn?t currently cover all aspects of geodesy or 
> space geodesy techniques (e.g. SLR, VLBI), it has been developed in 
> such a way to make it both extensible and compatible with other XML 
> schemas.
>
> ?*We propose that IGS endorse GeodesyML, a superset of the SOPAC Site 
> Log XML schema.*
>
> ?The benefits of adopting a GML Application Schema to express geodetic 
> and IGS site log information are numerous, one of which is that it 
> permits immediate implementation and adoption in OGC WFS compliant web 
> services.  Another is that it the endorsement and use of GeodesyML 
> would allow for the IGS site log metadata component to be developed 
> and implemented in the short term now, and other components of the ML 
> model later with the confidence that other metadata (Geodesy metadata 
> and other international Standards) will logically link be directly 
> compatible with other components of the model.
>
> ?We recognise that the development of the transfer of IGS site log 
> metadata by XML is a priority.
>
> ?Geoscience Australia is currently undertaking this staged 
> development. Last year we implemented the Site Log component of 
> GeodesyML (based predominantly on SOPAC Site Log Schema) along with 
> OGC compliant web services to facilitate the transfer of IGS site log 
> data between Australian and New Zealand jurisdictions.
>
> ?GeodesyML is currently a beta model in undergoing active development.
>
> ?This year we are extending our capability to include other components.
>
> ?The components of GeodesyML currently undergoing development and 
> enhancement include those which relate to dynamic reference frames, 
> deformation models, time series, and the SOPAC site log schema.
>
> *We would be more than happy to make GeodesyML available for review 
> along with documentation, the web service scripts we have developed 
> and code base relevant to marshalling and persistence of IGS xml site
> logs.*
>
> Finally, as requested, please find below some specific parts of the 
> SOPAC XML schema that we would like to be reviewed.
>
> *Review of SOPAC Site Log XML Schema*
>
> ?The schema lacks elements ?Previous Site Log? and ?Modified/Added 
> Sections? both present in the Form section of the plain text format.
>
> ?Some enumerations (e.g., igsReceiverModelCodeType) are incomplete, 
> causing schema validation to fail on valid data. If these enumerations 
> change more frequently than the schema structure, perhaps they can be 
> factored out into schematron files, which can be kept up-to-date 
> independently of the schema definition.
>
> ?Imports of gnssReceiver.xsd and gnssAntenna.xsd bring into scope some 
> old (2003) definitions of gnssReceiverType and gnssAntennaType, 
> resulting in multiple definitions of these types.
>
> ?Multiple namespaces are unnecessary. A single target namespace for 
> all elements would simplify the schema definition.
>
> I thank you for your time in reading our request and review of the 
> SOPAC Site Log XML Schema and look forward to discussing it with you 
> in the near future.
>
> Kind Regards,
>
> Nicholas Brown
>
> Geoscience Australia
>
> *Nicholas Brown
> *A/g Geodesy Section Leader  |  Geodesy Section
>
> Geodesy and Seismic Monitoring Group *|* *GEOSCIENCE AUSTRALIA*
>
> *__________________________________________________**__________*
>
> Phone: +61 2 6249 9831    Fax:  +61 2 6249 9999
>
> Email: Nicholas.Brown at ga.gov.au <mailto:Nicholas.Brown at ga.gov.au>Web: 
> www.ga.gov.au <http://www.ga.gov.au/>
>
> Cnr Jerrabomberra Avenue and Hindmarsh Drive Symonston ACT
>
> GPO Box 378 Canberra ACT 2601 Australia
>
> *Applying geoscience to Australia?s most important challenges*
>
> Geoscience Australia Disclaimer: This e-mail (and files transmitted 
> with it) is intended only for the person or entity to which it is 
> addressed. If you are not the intended recipient, then you have 
> received this e-mail by mistake and any use, dissemination, 
> forwarding, printing or copying of this e-mail and its file 
> attachments is prohibited. The security of emails transmitted cannot 
> be guaranteed; by forwarding or replying to this email, you 
> acknowledge and accept these risks.
> ----------------------------------------------------------------------
> ---------------------------------------------------
>

--
Mindy Squibb
msquibb at ucsd.edu
SOPAC
Mailing Address:
Mail Code 0225
9500 Gilman Drive
University of California, San Diego
La Jolla, CA 92093-0225
858-534-8487
IGPP/SIO Location:
Bldg T-31
8860 Biological Grade

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://igscb.jpl.nasa.gov/pipermail/igs-dcwg/attachments/20150210/3319a425/attachment.html 

------------------------------

_______________________________________________
IGS-DCWG mailing list
IGS-DCWG at igscb.jpl.nasa.gov
http://igscb.jpl.nasa.gov/mailman/listinfo/igs-dcwg

End of IGS-DCWG Digest, Vol 6, Issue 3
**************************************