[Support #ZYT-334660]: IDV level II data in google earth

Hi Nolan-

> For what it's worth, I just jumped in some radar data in DORADE format.
> It snapped in a bit more accurately, however, there is still a bit of a
> navigation problem with this data as well, just not as bad as with the
> level II data.

Are you setting it to the currently viewed area before capturing?
The DORADE projection will be different than the Level II and that
may be what you are seeing.

I looked into our map file and we are using the AWIPS shapefile which
I would guess is pretty accurate.  I've noticed in GE that their
map lines sometimes don't line up with physical features.  I also noticed
that their county outlines are pretty coarse compared to the AWIPS files.

I'm glad you are playing around with this export to KMZ feature.
If you don't know, you can save animations as KMZ and import them
into the latest version (4) of Google Earth which supports time
animation.

Don
 
> 
> -----Original Message-----
> From: Unidata IDV Support [mailto:address@hidden]
> Sent: Tuesday, February 13, 2007 3:11 PM
> To: Atkins, Nolan T @ LSC
> Cc: address@hidden
> Subject: [Support #ZYT-334660]: IDV level II data in google earth
> 
> Hi Nolan-
> 
> > I've dumped some level II radar data into Google earth and have
> noticed
> > a navigation problem.  I can get the radar data to overly exactly
> where
> > it should be in Google earth.  I've attached an example image showing
> > county lines generated by the IDV and those in Google earth.  There is
> > about a 5 mile mis match, quite large for radar data.
> 
> I'm guessing that the IDV display in in the native radar projection.
> Google Earth only supports rectilinear projections.  Use the
> Projections->Use Displayed Area menu to set to a lat/lon projection.
> You can then zoom in before saving.
> 
> > I've also attached the .kmz file I generated with the IDV.  Any
> thoughts
> > as to how to get the radar properly navigated?
> 
> Even with the overhead projection, I notice we're still a little off.
> That
> may be due to precision issues in the map file we use.  I'll look into
> this.
> 
> Don
> 
> 
> 
> 
> Ticket Details
> ===================
> Ticket ID: ZYT-334660
> Department: Support IDV
> Priority: Normal
> Status: Open
> 
> 
> 


Ticket Details
===================
Ticket ID: ZYT-334660
Department: Support IDV
Priority: Normal
Status: Open