[IDV #AJV-432941]: IDV Level II ingest

Hi Bob,

We do not use the lat/lon inside the data for the radar location, but
instead a table to provide it. You can add a local table following
these steps:

1 create a local nexradstns.xml and put it in .unidata\idv\DefaultIdv:
   you can reference
https://github.com/Unidata/IDV/blob/master/src/ucar/unidata/idv/resources/stations/nexradstns.xml

2 In your local nexradstns.xml add your radar information:

<station idn="008391" id="VVVV" name="bbbbb" st="BJ" co="v"
lat="39:48:31" lon="116:28:19" elev="13"/>

3 in .unidata\idv\DefaultIdv edit idv.rbi
   <resources name="application.resource.locations">
   <resource location="%USERPATH%/nexradstns.xml" id="nexrad"/>
   </resources>

4 after load your radar file and before click the create display button,
you can change the location in the properties tab. The
resulting display should be in the location you want.

Yuan

On Fri, Apr 29, 2022 at 7:09 AM Bob Stafford <address@hidden>
wrote:

> New Client Reply: IDV Level II ingest
>
> Thanks for the response.
>
> I've solved the immediate problem which was I had the ray index in
> message 31 starting at 0 instead of 1. So IDV now loads my data, but
> plots it at longitude=0 and latitude=0.
>
> Please could you tell me how IDV locates data it receives, does it use
> an external table in the same way that GR2Analyst does for example? I
> believe the long/lat in my message 31 data is correct, however I'm not
> currently generating a message 18 since most of that does not apply to
> our radars, does IDV use the long/lat from message 18 to plot the data
> at the correct location?
>
> I've uploaded the file in case it helps with the location of the data.
>
> Thanks
>
> Bob S.
>
> On 4/28/22 15:49, Unidata IDV Support wrote:
> >> Hi
> >>
> >> My name is Bob Stafford I'm a software engineer at EEC working on our
> >> EDGE radar software package. One of the features of our package is to
> >> export our radar data in Level II Message 31 format and this works with
> >> some packages, for example GR2Analyst can read our LevelII files with no
> >> problem.
> >>
> >> However it's been brought to our attention that IDV will not read our
> >> level II files.
> >>
> >> I was wondering if anyone would be able to assist me with identifying
> >> why IDV will not read our files and what I need to change to make it
> work.
> >>
> >> If you can assist I'd be happy to send you one of our files for
> analysis.
> >>
> >> The backtrace we're getting from IDV is this in case it helps
> >>
> >> *visad.VisADException: java.lang.ArrayIndexOutOfBoundsException:
> >> index=-1 shape=360*
> >>
> >> *at
> ucar.unidata.data.radar.CDMRadarAdapter.init(CDMRadarAdapter.java:507)*
> >>
> > Hi Bob,
> >
> > You can upload a sample file here:
> >
> > https://ramadda.unidata.ucar.edu/repository/alias/idvupload
> >
> > Yuan
> >
> > Ticket Details
> > ===================
> > Ticket ID: AJV-432941
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> > ===================
> > NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available through
> the web.  If you do not want to have your interactions made available in
> this way, you must let us know in each email you send to us.
> >
> >
>
>
>
> Ticket Details
> ===================
> Ticket ID: AJV-432941
> Department: Support IDV
> Priority: Normal
> Status: Open
> Link:
> https://andy.unidata.ucar.edu/staff/index.php?_m=tickets&_a=viewticket&ticketid=33207
>
>



Ticket Details
===================
Ticket ID: AJV-432941
Department: Support IDV
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.