OPUS Projects output-xml converter?

Ditto

I put an e-mail to Carlson and I will talk to Dave Carlson some weekend this summer. Hopefully we can get a UF way to work with projects output.

I could build one for you all.

Send me a sample xml payload/file (preferably somewhat small) and what you want it to look like and I'll have a look. Email in my profile is good.

Are you going to want to be able to edit this stuff as in an Excel sheet or just a [somewhat] static display?
If you wanting the converted output to be a "real" Excel .xlsx file, I would have to do some research on that. I know it's doable but just that I haven't done it.
E.

Thanks!

I don't see an email in your profile?

you can email me at

kevin_r_samuel at y a h o o . c o m

Personally I was looking for a file that has gives either the:

pt#,lat,lon,ellips height

pt#,utmN,utmE,Ortho

pt#,spcN,spcE,Ortho

Basically a simple file to bring the data from OP to a data collector or CAD program. An ascii, csv, or txt format would work just fine for my purposes.

OPUS XML conversion utility

Well... after a few emails with Kevin and some sample data, I have it figured out.
At minimum I can certainly supply what he wants in his earlier reply to me.

Now the question I pose to you all: What you would like to see this thing be able to do.

I discovered while picking apart the xml he sent and comparing it to the human readable version of the same file, that there are many more reference types to be had than the 2 he had in his report. I plan on discovering all these when you open an xml file and let you pick the one you want.

In his particular data set, he had 4 points of his own and 6 CORS stations. At first I was confused since his point were, well, point numbers and the CORS stations were names. So I suppose I should allow the user to decide if they want the CORS stations included in the output. But, what if the user's DC or CAD package doesn't like names for point numbers/descriptors?
The idea for now is to let the user pick things desired to be sent out to a CSV text file and in the order you wish.

I suppose I could throw in a metric to US or international feet conversion as well.

I have a lot of questions about this OPUS stuff having never been involved with it before. Here are a few:

• what is a "TROPO" interval?
• what is the difference between unconstrained marks and constrained ones?
• what is this section called "INCLUDED SOLUTION" and what is that stuff?

I tried some poking around at geodesy.noaa.gov/OPUS looking for some good techno-geek stuff but couldn't find anything. If anyone has some where to point me to for some serious technical stuff, that would be great.

I was looking at his xml section. Wouldn't it be super cool to take all that from-and-to station lat-lon data and build a Google Earth KML file and be able to look at it? That would just be freakin cool in my book!!!

Email or call me or post here to add to the wish list. If someone wants to proto-type up a user interface, that would be super!
E

OPUS XML conversion utility

Here is a link to a video by Mark Silver on OP...

This will give you a feel for the software interface.

OPUS XML conversion utility

Awesome to hear you are stepping to the plate.

There are 4 solutions to compare:
Min Constrained Horizontal
Full Constrained Horizontal
Min Constrained Vertical
Full Constrained Vertical

The program returns a full network adjustment.

The minimal constrained solution is to seek out the weak, the problems. Hold one CORS and solve the whole network, then compare the solutions to the record information. If something falls out, you can choose to hold it in the final solution, the fully constrained solution that holds all the points that passed your initial.

We need to input the NGS data sheets (or customized data entry) for all the points that have data. Then pull in one solution, compare and flag a result. It would be great to pull in the Min Horizontal and the Min Vertical simultaneously and out put results.

The Full Constrained Horizontal and Full Constrained Vertical solutions are finally merged into the final coordinates.

The Tropo stuff is completed by using one of a few tropo models with some time interval plus a CORS 1000 miles away to account for local atmospheric issues. The tropo stuff was a bit confusing as we were told to use one interval but the program uses a different default. I have left my projects at the default.

There are several files that are output. The XML is one option and there are text files as well. Beware when the solutions come through in different orders (not an issue for you I am sure, but one to watch).

KML/KMZ output would be cool. I use alphanumeric for all my coordinate files, so I am not afraid. I also like P,N,E,Z,eN,eE,eZ,eA,D as a format. (error North, East, Elevation, Azimuth) It's the output I use from Carlson SurvNet, then can use a base for the next SurvNet project.

thadd at ese-llc.net for more wordpuke from me. Also I can provide an explanation to the image in the thread [msg=259918]Opus Projects Workflow[/msg]

OPUS XML conversion utility

> Awesome to hear you are stepping to the plate.
I've been called the "doer of dirty deeds" before.

> There are 4 solutions to compare:
> Min Constrained Horizontal
> Full Constrained Horizontal
> Min Constrained Vertical
> Full Constrained Vertical
Where do I find these in the XML data? I see nothing alluding to such. Or is this something I need not concern myself since I'm just looking for data to output?

Perhaps you could send me one of yours - a small one please. Kevin's "small" one was almost 11,000 lines long.

> The Tropo stuff is completed by using one of a few tropo models with some time interval plus a CORS 1000 miles away to account for local atmospheric issues.

So would that imply "TROPO" means pertaining to something tropospheric?

> There are several files that are output. The XML is one option and there are text files as well. Beware when the solutions come through in different orders (not an issue for you I am sure, but one to watch).
I'm only going to mess with XML for now. If my program doesn't see the contents as valid/well-formed XML, it would let you know.

> KML/KMZ output would be cool. I use alphanumeric for all my coordinate files, so I am not afraid. I also like P,N,E,Z,eN,eE,eZ,eA,D as a format. (error North, East, Elevation, Azimuth) It's the output I use from Carlson SurvNet, then can use a base for the next SurvNet project.
P, N, E and I got. Where would I see eN, eE, eZ, eA or a "D"?

Would "D" be for an optional point descriptor one would wish to attach before outputting selected data? If so, I kind of had that in mind already.

> thadd at ese-llc.net for more wordpuke from me. Also I can provide an explanation to the image in the thread [msg=259918]Opus Projects Workflow[/msg]
Thanks. What issue of Am.Surveyor was he talking about? I should probably still have nearby.

E

OPUS XML conversion utility

Quick response as Monday is already heating up...

There would be 4 XML files to work with, each with a different value for each point...

Yes Tropo = Tropospheric Model, and there will be something about some CORS 1000 miles away that can be ignored for our purposes.

Each point should output an error in the report. If you do not choose to add the eN, eE... so be it. I'm not that pushy.

I can add more later, but Monday is pulling me back.

OPUS Projects output-xml AWESOME!!!

More OPUS help please.....

What data should I keep. For example this point 2123 contained within is point data based on NETOWRK_SOLUTION and within that I have a set of data containing reference frames and respective data I suppose he (Kevin) happened to select.

In this sample file I have 4 user points and 6 CORS stations:
Within each point data is contained multiple RINEX solutions. Is this case I have two different reference frames with their own set of data repeated multiple times. No problem.

How am I, i.e. the program supposed to know which one to take? Currently I'm taking them all. Their respective datae seem to be exact at the top the level - depending on the reference frame of course.
Should I just take the first Rinex data and ignore the rest?

You all really have to school me on this. I've got the data captured just fine and dandy. Some seems duplicative.

In any event, I can now get all the data we/you want out of this monster xml payload.

Other than simple meter-feet conversion I'm not planning on changing any data within the resultant set and that would happen to go to output to a CSV or TXT file (doesn't matter to me)..

Which one do I rely on?
Or, should I rely on anything??

In Kevin's payload all points have 4 sets of Rinex and 2 for each reference - except one which only 3.

In just ONE day of research and today's (well, maybe two day and a half) effort and programming I was able to produce this: (coming from Kevin's sample file:)

The baselines to output to a KML/KMZ should be no problem.
I just need to know the format - which I can lookup.

(How the hell do I upload a screen shot?)
This is Kevin's data so perhaps he would recognize it.
[no screen shot]. 2123 and nola were the things I was comparing my stuff and they are exact to what ever decimal place they supplied.

E

OPUS Projects output-xml AWESOME!!!

> More OPUS help please.....
>
> What data should I keep. For example this point 2123 contained within is point data based on NETWORK_SOLUTION and within that I have a set of data containing reference frames and respective data I suppose he (Kevin) happened to select.
>

I would report the user selected reference frame; which in this case is NAD_83(CORS96) (2002.0000)

> In this sample file I have 4 user points and 6 CORS stations:
> Within each point data is contained multiple RINEX solutions. Is this case I have two different reference frames with their own set of data repeated multiple times. No problem.
>
> How am I, i.e. the program supposed to know which one to take? Currently I'm taking them all. Their respective datae seem to be exact at the top the level - depending on the reference frame of course.
> Should I just take the first Rinex data and ignore the rest?

I would only take the data from the section marked "UNCONSTRAINED MARKS" and "CONSTRAINED MARKS" these are the least squares adjusted network positions. Not all users will be interested in the coordinate values of the CORS, but in some cases this may be very pertinent to a particular project. I would not worry about the baselines listed at the top of the report.

>
> You all really have to school me on this. I've got the data captured just fine and dandy. Some seems duplicative.
>
> In any event, I can now get all the data we/you want out of this monster xml payload.
>
> Other than simple meter-feet conversion I'm not planning on changing any data within the resultant set and that would happen to go to output to a CSV or TXT file (doesn't matter to me)..
>
> Which one do I rely on?
> Or, should I rely on anything??
>
> In Kevin's payload all points have 4 sets of Rinex and 2 for each reference - except one which only 3.
>
> In just ONE day of research and today's (well, maybe two day and a half) effort and programming I was able to produce this: (coming from Kevin's sample file:)
>
> The baselines to output to a KML/KMZ should be no problem.
> I just need to know the format - which I can lookup.
>
> (How the hell do I upload a screen shot?)
> This is Kevin's data so perhaps he would recognize it.

This is a sample data set as provided in the training. As far as the kml/kmz formatting I suppose you could look here http://www.earthpoint.us/exceltokml.aspx .

> [no screen shot]. 2123 and nola were the things I was comparing my stuff and they are exact to what ever decimal place they supplied.
>
> E

OPUS Projects output-xml AWESOME!!!

The way I see it the four most likely data sources users will want are:
- X,Y,Z
- lat,lon,ell ht
- utmN,utmE,ortho
- spcN,spcE,ortho

See the highlighted sections in the following image.

Hopefully somebody else will also send you some sample data to test with. I am just beginning to think through this. I hope that any established OP users/lurkers chime in and share items off their wishlists too.

OPUS Projects output-xml AWESOME!!!

That would lead to the real question: who needs XYZ? Lat-Long?

All I want is State Plane and Ortho adjusted to US Survey Feet. I could see keeping the metric option and adding an International Foot Option.

The output of PNEZD CSV would allow for the import into Excel and then a comparison between record and observed values to determine outliers and determine the final constrained stations for the 'final' solution.

OPUS Projects output-xml AWESOME!!!

I have all that data captured - and then some. My quandary is with the solution xml file. Each point has multiple sets of Rinex solutions which appear to have the same data.

Should the program just pick up the first set, skip the other Rinex solutions and go on to the next block of point data? Is that "safe" for my program to do? I don't want to just arbitrarily ignore solution sets.

Mr. Spledeus actually called me last night (more like super early this morning) and did send me a bunch more stuff [sample files] from real-world (i.e. non-training stuff) observations to have a look. We talked until around 0230 or so.

He did suggest I go ahead and allow for unit conversions (metric-feet) on the output.

As far as constrained vs. unconstrained point data goes, I don't see in the XML data how the program could tell the difference. Having just said that, towards the end of XML data is a block called where all the points are listed. The user sites (your points in your case) have no data but he cors point do. This is the only place where they appear to be differentiated.
I wish someone from NOAA/NGS would be following this and chime in or contact me about this stuff.

OPUS Projects output-xml AWESOME!!!

NGS users and CORS site managers may want the xyz.

I am not working state plane, but another low distortion projection defined by the State DOT in our Administrative rules.

Avdshare Audio Converter can Free download Opus converter for Mac or Windows version to convert Opus audio files to MP3, AAC, FLAC, AC3, WAV, WMA, OGG, RA, AU, M4A etc.

jessendeen, post: 396754, member: 12222 wrote: Avdshare Audio Converter can Free download Opus converter for Mac or Windows version to convert Opus audio files to MP3, AAC, FLAC, AC3, WAV, WMA, OGG, RA, AU, M4A etc.

Wrong OPUS. The one you reference is for converting https://en.wikipedia.org/wiki/Opus_(audio_format)&apos ;">Opus audio files, not OPUS result files.