[Xastir] 2008 Tiger Map edge.dbfawk

Richard Polivka r.polivka at sbcglobal.net
Wed Apr 29 16:49:45 EDT 2009 

Keith / Gents,

I am at work and away from my machine. 

When I get home, I will post my .dbfawks, file structures, and layer setups. 

Also, if you want to snoop at the shapefiles, get "qgis" and work with that.

73 from 807,

Richard, N6NKO


--- On Wed, 4/29/09, Tom Russo <russo at bogodyn.org> wrote:
From: Tom Russo <russo at bogodyn.org>
Subject: Re: [Xastir] 2008 Tiger Map edge.dbfawk
To: "Keith Kaiser" <wa0tjt at gmail.com>
Cc: "Xastir - APRS client software discussion" <xastir at lists.xastir.org>
Date: Wednesday, April 29, 2009, 12:39 PM

On Wed, Apr 29, 2009 at 12:27:59PM -0500, we recorded a bogon-computron
collision of the <wa0tjt at gmail.com> flavor, containing:
> I don't think it's in tabblock I think it's in featnames. I
went into  
> both and made the featnames look the same as in edges, still have the  
> same exact behavior as before.

No, I believe you're mistaken there.  "featnames" is in fact not
a shapefile.
It's just a DBF file that is completely useless for Xastir's purposes. 
You 
should not bother downloading tl*featnames.zip, and might as well remove all 
the tl*featnames.* files.

> I'm clearly doing something wrong.

Take my advice:  turn off *all* maps except the edges shapefile.  Then go to
work on your edges.dbfawk file.  When you have it working the way you like,
then systematically turn on shapefiles one by one.  At some point you'll 
suddenly see a change to behavior you don't want --- that shapefile is the
problem, and you'll have to change its dbfawk, too.

tabblock and edges both have features representing the same lines, and I 
believe they have different MTFCC values for those features.  So making 
tabblock and edges have the same rules won't help.  You'll either want
to
disable tabblock or edit its rules to get the right behavior.

> On Apr 29, 2009, at 10:41 AM, Tom Russo wrote:
> 
> > On Wed, Apr 29, 2009 at 09:28:09AM -0500, we recorded a bogon- 
> > computron collision of the <wa0tjt at gmail.com> flavor,
containing:
> >> The mystery continues! I've posted two screen shots of my
Xastir
> >> running, one at zoom level 128 the other at level 151. The 128
level
> >> really is pretty nice, especially note the smaller roads how they
are
> >> grayed out. Now compare them to the 151 level how the same roads
are
> >> now in black.
> >>
> >> http://kaiserklan.com/snapshot_128.png
> >> http://kaiserklan.com/snapshot_151.png
> >>
> >> I can not find the MTFCC=S level that controls this, nor can I
figure
> >> out my original question how to drop these smaller roads off the
map
> >> completely above 150 zoom.
> >
> > I think the issue is that the edges and a second file both contain  
> > shapes
> > for the same road.  This was something I worked out with Dale a week 

> > or two
> > ago.  This is why the roads change color --- one map is drawn on top 

> > of the
> > other, and when the upper one stops being drawn the lower one starts 

> > being
> > visible.
> >
> > I believe that the "tabblock" file is the one with the
duplicate  
> > shapes.  Thing
> > is, I believe it also has different MTFCC codes for them, because it 

> > is using
> > those lines for different purposes (boundaries of tabulation blocks
or
> > something like that).
> >
> > I'm not clear on what value the tabblock file has, but the  
> > duplication of
> > features is confusing to the map user in Xastir.  Try turning off  
> > the tabblock
> > files for your area and see if it gets you the behavior you want.   
> > If tabblock
> > contains some features you really want to see, you'll have to
figure  
> > out
> > how to tweak *its* dbfawk file to hide the features you want to go  
> > away at
> > high zooms.
> >
> > Trying to debug dbfawk files while viewing multiple shapefiles at  
> > once is the
> > path to madness.  What you want to do when working on a dbfawk file  
> > is to
> > deselect all maps in the map chooser except the one associated with  
> > the dbfawk
> > you're debugging.  In this case, the presence of identical shapes
in  
> > multiple
> > files completely confuses the issue.
> >
> >
> >>
> >> On Apr 28, 2009, at 1:00 PM, Tom Russo wrote:
> >>
> >>> On Tue, Apr 28, 2009 at 12:55:11PM -0500, we recorded a
bogon-
> >>> computron collision of the <wa0tjt at gmail.com> flavor,
containing:
> >>>> Renaming doesn't seem to have had any effect. I
renamed, then
> >>>> reindexed all maps but I still have all the roads that
should not  
> >>>> be
> >>>> showing above level 150 showing up at all levels. I tried
closing
> >>>> Xastir, and even rebooting, hmmmm!
> >>>
> >>> Do you have "Enable Map Levels" turned on?
> >>>
> >>> See Map->Enable Map Levels.  If it's not checked, it
should be.
> >>> Unchecked it
> >>> will always display all shapes in a shapefile irrespective of
zoom
> >>> level.
> >>>
> >>>> On Apr 28, 2009, at 11:14 AM, Dick Repasky wrote:
> >>>>
> >>>>>
> >>>>> I think that the problem may be that the dbfawk file
is misnamed  
> >>>>> in
> >>>>> the zip
> >>>>> distro.  Try renaming the file to edges.dbfawk. That
worked for  
> >>>>> me.
> >>>>>
> >>>>> Dick, KC9JLU
> >>>>>
> >>>>>
> >>>>> Keith Kaiser wrote:
> >>>>>> I've got something wrong I just don't
understand...
> >>>>>>
> >>>>>> This is a snipit from the edge.dfbawk file,
please note the types
> >>>>>> of
> >>>>>> roads (Limited Access, secondary, local, 4WD,
Freeway access,
> >>>>>> walkway,
> >>>>>> alley, bike, road median). So where are the
interstate highways,
> >>>>>> state
> >>>>>> highways, etc.?
> >>>>>>
> >>>>>> Also, setting these display_level values had no
effect on the map
> >>>>>> display, they made no changes at all. I still
have way too much
> >>>>>> detail
> >>>>>> at higher zoom levels. What am I doing wrong? Do
I need to have  
> >>>>>> the
> >>>>>> details in map chooser set in some special way?
Currently they  
> >>>>>> are
> >>>>>> set
> >>>>>> (mostly) like this; max zoom = 500, min zoom = -,
fill = auto,
> >>>>>> automap =
> >>>>>> yes
> >>>>>>
> >>>>>> Help!
> >>>>>>
> >>>>>> ....
> >>>>>> # Limited access road
> >>>>>> /^MTFCC=S11/ {lanes=4; color=11;
display_level=64;  
> >>>>>> label_level=64;
> >>>>>> font_size=3; next}
> >>>>>> # secondary road
> >>>>>> /^MTFCC=S12/ {display_level=150; lanes=3;
color=8;  
> >>>>>> label_level=75;
> >>>>>> font_size=2; next}
> >>>>>> # local road
> >>>>>> /^MTFCC=S14/ {display_level=150; label_level=16;
color=48;  
> >>>>>> lanes=1;
> >>>>>> next}
> >>>>>> # 4WD off-road trail
> >>>>>> /^MTFCC=S15/ {lanes=1; color=4; display_level=32;
font_size=1;
> >>>>>> next}
> >>>>>> # Freeway access / service drive
> >>>>>> /^MTFCC=S16/ {color=11; display_level=64; next}
> >>>>>> # walkway / stairway
> >>>>>> /^MTFCC=S17[12]/ {lanes=1; color=12; pattern=2;
display_level=32;
> >>>>>> next}
> >>>>>> # alley / private road
> >>>>>> /^MTFCC=S17[34]/ {lanes=1; color=40; pattern=2;
display_level=64;
> >>>>>> next}
> >>>>>> # bike / bridle path
> >>>>>> /^MTFCC=S18/ {lanes=1; color=40; pattern=2;
display_level=64;  
> >>>>>> next}
> >>>>>> # road median
> >>>>>> /^MTFCC=S20/ {lanes=1; color=40; pattern=2;
display_level=64;  
> >>>>>> next}
> >>>>>> ....
> >>>>>>
> >>>>>> 73's
> >>>>>> Keith Kaiser
> >>>>>> wa0tjt at gmail.com
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Xastir mailing list
> >>>>>> Xastir at lists.xastir.org
> >>>>>>
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
> >>>>>>
> >>>>> _______________________________________________
> >>>>> Xastir mailing list
> >>>>> Xastir at lists.xastir.org
> >>>>>
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
> >>>>
> >>>> 73's
> >>>> Keith Kaiser
> >>>> wa0tjt at gmail.com
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Xastir mailing list
> >>>> Xastir at lists.xastir.org
> >>>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
> >>>
> >>> -- 
> >>> Tom Russo    KM5VY   SAR502   DM64ux         
http://www.swcp.com/~russo/
> >>> Tijeras, NM  QRPL#1592 K2#398  SOC#236       
http://kevan.org/brain.cgi?DDTNM
> >>> In some cultures what I do would be considered normal.
> >>>                                 -- Ineffective daily
affirmation
> >>>
> >>> _______________________________________________
> >>> Xastir mailing list
> >>> Xastir at lists.xastir.org
> >>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
> >>
> >> 73's
> >> Keith Kaiser
> >> wa0tjt at gmail.com
> >>
> >>
> >
> > -- 
> > Tom Russo    KM5VY   SAR502   DM64ux         
http://www.swcp.com/~russo/
> > Tijeras, NM  QRPL#1592 K2#398  SOC#236       
http://kevan.org/brain.cgi?DDTNM
> >  In some cultures what I do would be considered normal.
> >                                  -- Ineffective daily affirmation
> >
> 
> 73's
> Keith Kaiser
> wa0tjt at gmail.com
> 
> 

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
  In some cultures what I do would be considered normal. 
                                  -- Ineffective daily affirmation 

_______________________________________________
Xastir mailing list
Xastir at lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

More information about the Xastir mailing list