Re: [Xastir] Shapefile Problem
Thanks Tom, Since I got back home a couple of hours ago I've done some serious reading and had already renamed the sample file you mentioned to match the dbf name. I looked at the database structure and found that for c_aus20no08.dbfawk, the structure (field names) is identical with your example. The z and mz databases each have less fields and I have removed the fields that don't exist from their dbfawk files. I *think* I'm starting to head in the right direction in this regard. With regard to dbfinfo and dbffields and their use as mentioned in readme.maps, I find that those files haven't compiled, but I've yet to investigate why. configure.log looks logical but I'll likely recompile xastir from scratch so I can more closely watch any error messages that may arise. I'll take a look at the wiki. This is certainly new to me and I suspect to quite a few others down this way. Thanks for your help. Ray vk2tv Tom Russo wrote: > On Fri, Nov 21, 2008 at 06:07:47PM -0600, we recorded a bogon-computron > collision of the <[EMAIL PROTECTED]> flavor, containing: > >> On Fri, Nov 21, 2008 at 2:28 PM, Ray Wells <[EMAIL PROTECTED]> wrote: >> >> >> >>> We have dbf files with the county files. >>> >> Not dbf, dbfawk. That's an xastir-specific file that goes with a set >> of shapefiles to influence how those files are displayed. As best I >> can recall, the behavior you describe sounds like how xastir displays >> a shapefile with no corresponding dbfawk. >> > > Yes, it is. Not only that, the weather alert stuff is entirely dependent on > proper dbfawk files being set up for the associated shapefiles -- the dbfawk > files provided with Xastir will only make the NOAA US shapefiles work > properly. You'll have to set up a complete new dbfawk for the > Australia-specific shapefiles. > > You can look at the nwsc_ddmmyy.dbfawk file in /usr/local/share/xastir/config > for how the US county data is used; odds are good you can copy that one to > another name and modify it only slightly to get your shapefiles working. > > One must set a "key" for each shape that will be used to match that > shape against the county in the alert (the alert "title"). For the US, that > key is something like NM_C004 for county # 004 in state NM. The > nwsc_ddmmyy.dbfawk file combines the "STATE" and "FIPS" fields in the dbf > file > to construct the key. It will almost certainly be different for the > Australia > shapefiles. You will also need to be sure to set the dbfinfo and dbffields > variables appropriately. > > The Xastir wiki page > http://www.xastir.org/wiki/index.php/HowTo:DBFAWK > is the wikified version of my dbfawk tutorial, but it doesn't go into > the weather alert stuff (mainly because that stuff was already set up for > US users and few would need to modify it). The essential dbfawk feature > that's not described in that document is the "key" field, which is used > only for weather alerts. The dbfinfo and dbffields variables are documented > there, though. > > ___ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Shapefile Problem
On Fri, Nov 21, 2008 at 06:07:47PM -0600, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, Nov 21, 2008 at 2:28 PM, Ray Wells <[EMAIL PROTECTED]> wrote: > > > > We have dbf files with the county files. > > Not dbf, dbfawk. That's an xastir-specific file that goes with a set > of shapefiles to influence how those files are displayed. As best I > can recall, the behavior you describe sounds like how xastir displays > a shapefile with no corresponding dbfawk. Yes, it is. Not only that, the weather alert stuff is entirely dependent on proper dbfawk files being set up for the associated shapefiles -- the dbfawk files provided with Xastir will only make the NOAA US shapefiles work properly. You'll have to set up a complete new dbfawk for the Australia-specific shapefiles. You can look at the nwsc_ddmmyy.dbfawk file in /usr/local/share/xastir/config for how the US county data is used; odds are good you can copy that one to another name and modify it only slightly to get your shapefiles working. One must set a "key" for each shape that will be used to match that shape against the county in the alert (the alert "title"). For the US, that key is something like NM_C004 for county # 004 in state NM. The nwsc_ddmmyy.dbfawk file combines the "STATE" and "FIPS" fields in the dbf file to construct the key. It will almost certainly be different for the Australia shapefiles. You will also need to be sure to set the dbfinfo and dbffields variables appropriately. The Xastir wiki page http://www.xastir.org/wiki/index.php/HowTo:DBFAWK is the wikified version of my dbfawk tutorial, but it doesn't go into the weather alert stuff (mainly because that stuff was already set up for US users and few would need to modify it). The essential dbfawk feature that's not described in that document is the "key" field, which is used only for weather alerts. The dbfinfo and dbffields variables are documented there, though. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM "I have the power to channel my imagination into ever-soaring levels of suspicion and paranoia." -- Ineffective daily affirmation ___ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
[Xastir] Shapefile Problem
In the last few days weather warnings have been made available for aprs in Australia. Those of us running xastir have encountered a common problem in that the warning area is not defined and coloured (filled) on the display. The object icon is displayed. If auto-fill is enabled in Map Properties the entire map is grey, with black county outlines. Many of us have been attempting various configuration options to overcome this issue and we'd appreciate any guidance from those more experienced with shapefiles. I have the various files - shp, prj, shx and dbf files in maps/Counties. At least some others have an identical directory structure. What we are seeing are the shire (county) outlines and the shire names. We have loosely touched on the possibility of the Australian data being in an incompatible format. Ray vk2tv ___ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Shapefile Problem
On Fri, Nov 21, 2008 at 2:28 PM, Ray Wells <[EMAIL PROTECTED]> wrote: > We have dbf files with the county files. Not dbf, dbfawk. That's an xastir-specific file that goes with a set of shapefiles to influence how those files are displayed. As best I can recall, the behavior you describe sounds like how xastir displays a shapefile with no corresponding dbfawk. -Jason kg4wsv ___ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
[Xastir] Shapefile Problem
On Fri, Nov 21, 2008 at 2:47 AM, Ray Wells <[EMAIL PROTECTED]> wrote: > > Those of us running xastir have encountered a common problem in that the > > warning area is not defined and coloured (filled) on the display. The > > object icon is displayed. If auto-fill is enabled in Map Properties the > > entire map is grey, with black county outlines. This sounds like you need dbfawk files to go with your county files. Tom has a tutorial on creating dbfawks. You may want to take this over to the xastir list ([email protected]) for a more precisely targeted audience. -Jason kg4wsv We have dbf files with the county files. Those using UIView report the warnings are working as intended, it's ALL xastir users who are having the problem which is why I wondered about the possibility of the data format being "wrong". I'll have a look for Tom's info. I realised my list mistake after I hit send and have resent to the xastir list. Ray vk2tv ___ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
