[Xastir] ShapeFile Zone duplicates?

[Lynn W. Deffenbaugh (Mr)]

Thank you for pointing out my obsolete file.  Don't ask me how I managed 
to be running that one, but running it I was.  I have now loaded up 
c_01de10 and it still has some duplicate zones in different records, but 
at least it doesn't have any duplicates owned by different CWAs.

I believe I'll adopt the xastir approach for now (because it's easiest) 
and just use the first instance of the zone from the file.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  Here's the list of duplicated zones in the "c_01de10" file.  
There's similar multi-record zones in fz01de10.shp, mz01jn10.shp (DTX's 
LCZ422 has 55 records!), and z_01de10.shp, but I'm just going to ignore 
the issue until someone that knows what things SHOULD look like tells me 
what DOESN'T look that way!

c_01de10.shp[2497] is AKQ's VAC036 [2248] is AKQ's VAC036

c_01de10.shp[2562] is AKQ's VAC115 [2561] is AKQ's VAC115

c_01de10.shp[2572] is AKQ's VAC735 [2570] is AKQ's VAC735

c_01de10.shp[3215] is CHS's GAC179 [2897] is CHS's GAC179

c_01de10.shp[2896] is CHS's GAC191 [2541] is CHS's GAC191

c_01de10.shp[2595] is CHS's SCC013 [2537] is CHS's SCC013

c_01de10.shp[3230] is LWX's MDC005 [2544] is LWX's MDC005

c_01de10.shp[2557] is LWX's MDC017 [844] is LWX's MDC017

c_01de10.shp[3229] is LWX's MDC025 [2509] is LWX's MDC025

c_01de10.shp[2556] is LWX's VAC099 [2157] is LWX's VAC099

c_01de10.shp[2682] is OKX's NYC047 [2533] is OKX's NYC047

c_01de10.shp[3262] is TAE's FLC037 [3261] is TAE's FLC037

c_01de10.shp[3252] is TAE's FLC045 [2601] is TAE's FLC045

c_01de10.shp[2538] is TAE's FLC063 [2536] is TAE's FLC063

c_01de10.shp[3243] is TAE's FLC131 [3195] is TAE's FLC131

c_01de10.shp[2663] is TAE's GAC253 [2599] is TAE's GAC253


On 3/1/2011 5:30 PM, Curt, WE7U wrote:
> On Tue, 1 Mar 2011, Lynn W. Deffenbaugh (Mr) wrote:
>
>> As many of you know, I've been working on Shapefile support in 
>> APRSISCE/32 and have recently uncovered an unexpected "feature" in 
>> one of the NWS shapefiles, specifically c_15jl09.shp.  It seems that 
>> this shapefile has multiple objects for a single zone ID and even 
>> better, a few of those multiple objects are actually the 
>> responsibility of different CWAs (namely FLC087 and VAC099).
>
> That file is out of date.  Check the currently active file "c_01de10" 
> to see if it has the same issues.  You might also check newer ones 
> (which are not supposed to be used yet) listed on the NWS site.
>
> One thing I discovered recently while conversing with David (kd7myc) 
> about these files is that there's an activation date for each of the 
> files, and you want to be using the one that is currently active.  
> There may be newer ones but you aren't supposed to use them until the 
> date listed.  A bit confusing.
>
> If you find problems like you describe in the active (or newer) files, 
> report them to the people putting the files out.  Some years back I 
> reported that some polygons in the shapefiles crossed the -180 degree 
> longitude boundary.  People at NOAA did respond to my e-mail, saying 
> that their CAD software allowed it, and the resulting polygons were as 
> intended.  Not the result I was looking for, but they did respond 
> which was nice.
>
>
>> I was wondering how xastir handles this when attempting to light up 
>> an area for an NWS message-specified zone?  Currently I just run with 
>> the first one, but am considering actually merging the multiple 
>> definitions into one and activating the composite results.
>
> We use the first match we find.
>