<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>Hi Carine,</div>
<div id="AppleMailSignature">Thanks for this excellent feedback. We are looking to make some changes and improvements to GeodesyML in the coming weeks.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">This feedback you've provided will be very useful. I hope we can address all these concerns in the coming weeks. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">I'll let you know when we have a new version to trial.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Kind Regards,</div>
<div id="AppleMailSignature">Nick</div>
<div id="AppleMailSignature"><br>
<div><span style="background-color: rgba(255, 255, 255, 0);"><b>Nicholas Brown</b></span></div>
GNSS Operations and National Geodesy Team Leader<br>
<div><span style="background-color: rgba(255, 255, 255, 0);">Geoscience Australia</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
</div>
<div>On 26 Oct 2016, at 00:10, Carine Bruyninx (ROB) <<a href="mailto:C.Bruyninx@oma.be">C.Bruyninx@oma.be</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>Dear Fran,</span><br>
<span></span><br>
<span>We have been trying to map the site logs of the EPN and EPN densification (about 1300 site log files) in the GeodesyML format and our main concerns are related to (hoping we got it all right):</span><br>
<span></span><br>
<span>- fields that are mandatory in GeodesyML (mostly expecting a double) and are not in the site log.</span><br>
<span></span><br>
<span>- fields in the site log that have values such as "<5" while GeodesyML only accepts a double</span><br>
<span></span><br>
<span>- TIME/DATE format incomptability:</span><br>
<span>GeodesyML accepts CCYY-MM-DDThh:mm:ssZ or CCYY-MM-DD</span><br>
<span>Site log accepts CCYY-MM-DDThh:mmZ or CCYY-MM-DD</span><br>
<span></span><br>
<span>- Site log section 3:</span><br>
<span>Our site logs have two fields (deg C) +/- (deg C) for the temperature stabilisation info from site log, while GeodesyML has only one. But we discussed this already in a previous mail.</span><br>
<span></span><br>
<span>- Site log section 6:</span><br>
<span>GeodesyML requests a double as input to "Input Frequency" even if an internal frequency is used.</span><br>
<span></span><br>
<span>- Section 8.5.1:</span><br>
<span>GeodesyML asks for a date input, which is not standard foreseen in site log</span><br>
<span></span><br>
<span>- Site log Section 11:</span><br>
<span>We choose to put site log Section 11 in ‘siteContact’ and additionally, put the first contact also in put in mandatory ‘siteMetadataCustodian’.</span><br>
<span></span><br>
<span>- Site log Section 12:</span><br>
<span>GeodesyML allows for only one contact person in ‘siteOwner’, while Site log allows multiple.</span><br>
<span></span><br>
<span>- Site log Sections 11 and 12:</span><br>
<span>Fields: Prefered Abbreviation and Additional Information are missing in GeodesyML. So information is lost when converting to GeodesyML</span><br>
<span>and</span><br>
<span>The address in GeodesyML is split in deliveryPoint, city, postcode, country while in the site log, these fields are not always separated. Impossible to complete GeodesyML automatically. Need to split also fields in site log to accommodate GeodesyML.</span><br>
<span></span><br>
<span></span><br>
<span>In addition, we would like to see an extension of GeodesyML to allow providing the url to the file with individual antenna calibrations, if available.</span><br>
<span></span><br>
<span></span><br>
<span>Best regards,</span><br>
<span>Carine</span><br>
<span></span><br>
<span>Op 20/10/2016 om 15:29 schreef Fran Boler:</span><br>
<blockquote type="cite"><span>Greetings All-</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Following the IGS Workshop in Sydney in April this year, we issued a</span><br>
</blockquote>
<blockquote type="cite"><span>call for Use Cases for the Site Log XML effort in an e-mail to this</span><br>
</blockquote>
<blockquote type="cite"><span>list. In April, the eGeodesy team announced the release of GeodesyML</span><br>
</blockquote>
<blockquote type="cite"><span>Beta 0.3 to this list.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>There hasn't been any disussions or updates since then, and I do</span><br>
</blockquote>
<blockquote type="cite"><span>apologize that I have not been able to devote time to this effort</span><br>
</blockquote>
<blockquote type="cite"><span>personally, and neither has UNAVCO been able to task the staff with</span><br>
</blockquote>
<blockquote type="cite"><span>implementation. However, I am hoping that some groups have had the</span><br>
</blockquote>
<blockquote type="cite"><span>chance to make progress toward our goals. Could I request a brief update</span><br>
</blockquote>
<blockquote type="cite"><span>from anyone who has been working towards implementing GeodesyML and the</span><br>
</blockquote>
<blockquote type="cite"><span>Site Log XML schemas and the machine-to-machine exchange of metadata?</span><br>
</blockquote>
<blockquote type="cite"><span>And for those like us at UNAVCO who have not started implementation but</span><br>
</blockquote>
<blockquote type="cite"><span>do still intend to work towards the goals, please respond indicating</span><br>
</blockquote>
<blockquote type="cite"><span>your intentions. Please reply to the entire list.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>I hope to be able to assemble an agenda and hold a teleconference in the</span><br>
</blockquote>
<blockquote type="cite"><span>next few weeks to review where we are in this effort, revisit the tasks,</span><br>
</blockquote>
<blockquote type="cite"><span>and propose timeline for progress.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Thanks for your continued support of this effort.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Best,</span><br>
</blockquote>
<blockquote type="cite"><span>Fran</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<span></span><br>
<span></span><br>
<span>-- </span><br>
<span>-----------------------------------------------------------------</span><br>
<span>Carine Bruyninx Email : <a href="mailto:epncb@oma.be">
epncb@oma.be</a></span><br>
<span>EUREF Permanent Network Central Bureau <a href="http://www.epncb.oma.be/">http://www.epncb.oma.be/</a></span><br>
<span></span><br>
<span>Royal Observatory of Belgium Phone : +32-(0)2-3730292</span><br>
<span>Av. Circulaire 3 Fax : +32-(0)2-3749822</span><br>
<span>B-1180 Brussels Email : <a href="mailto:C.Bruyninx@oma.be">
C.Bruyninx@oma.be</a></span><br>
<span>BELGIUM <a href="http://www.gnss.be/">http://www.gnss.be/</a></span><br>
<span>-----------------------------------------------------------------</span><br>
<span>_______________________________________________</span><br>
<span>IGS-DCWG mailing list</span><br>
<span><a href="mailto:IGS-DCWG@igscb.jpl.nasa.gov">IGS-DCWG@igscb.jpl.nasa.gov</a></span><br>
<span><a href="https://igscb.jpl.nasa.gov/mailman/listinfo/igs-dcwg">https://igscb.jpl.nasa.gov/mailman/listinfo/igs-dcwg</a></span><br>
</div>
</blockquote>
</body>
</html>