Re: [Xastir] OSM Example DBFAWK File
On Fri, 9 Jul 2010, James Ewen wrote: I was looking to see if I could find the issues you are trying to point out, but it is a little difficult to find right where you are looking at. I suspect the problem with the west and north borders of Whatcom county may have been due to the way the Shapefile extracts where done rather than present in the OSM database itself. The misspelling of Insterstate at Snoqualmie Pass along I-90 is most likely in the master database. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
Hi Curt, I like yours better than my poor attempt last night. One tweak I would do though is set the fill_color to 10 for TYPE=forest on _natural.dbfawk For Ireland the administrative database seems to have multiple levels (2,4,6,7,10 and 'blank') to represent the same thing, though Level 2 seems to be the border with the North of Ireland, and some Sea 'borders'. Thanks John On 8 Jul 2010, at 22:35, Curt, WE7U wrote: On Thu, 8 Jul 2010, Keith Kaiser wrote: Those are not too bad Curt, very nice in fact. Now for my long time dream color the county boardsred. County Borders? Look at the *_administrative.dbfawk file. http://www.xastir.org/wiki/HowTo:DBFAWK has the colors. I don't know if they separated the county borders adequately from other items, but try editing the four levels in the dbfawk file one at a time to see if you can get the effect you're after. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
On Fri, 9 Jul 2010, Keith Kaiser wrote: It sounded good. I changed one item at a time, then small groups, then finally everything. None of my changes actually translated to a change of the map... yet I know these dbfawk files do work. H! Where did you put the dbfawk file? There are two locations, corresponding to two different methods. System config area: Read only on startup Per-map w/naming like the map: Read each time you enable a map I've so far been experimenting with the 2nd method with OSM, where I have washington_*.dbf and washington_*.dbfawk to go with it. I can see changes quickly that way. If I don't see changes for some reason I can always restart Xastir and then see them. I don't know when that becomes necessary but it seemed I needed to do that every once in a while with my experiments. I might have been fooling myself though and it might have just been errors in my syntax at the time, 'cuz I don't think any caching goes on for the dbfawk files that are per-map. Other things I've noticed (maybe previously covered) is that the Kansas map for example extends into Missouri and the other way too. Another thing is not all the lines are where they should be. For example the county line between Platte and Clay counties in Missouri is off by .5 mile or more. An OSM problem most likely, not an Xastir one. I see problems in Washington already too. See about updating the OSM database with the fixes so that everyone benefits. Here I saw problems with the Canadian border -and- the west border of Whatcom county, plus a typo: Insterstate 90 at Snoqualmie Pass. I'm sure I'll find more as I play. If someone who's familiar with OSM knows the easiest method for updating the database, please let all of us know. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
On Fri, 09 Jul 2010 21:59:11 Curt, WE7U wrote: Here I saw problems with the Canadian border -and- the west border of Whatcom county, plus a typo: Insterstate 90 at Snoqualmie Pass. I'm sure I'll find more as I play. If someone who's familiar with OSM knows the easiest method for updating the database, please let all of us know. Well, you don't update the database per se. You edit the map and submit your changes. The first thing you need to do is create an OSM editor account. This identifies you as a person who wishes/chooses to edit the maps. Go here, and click sign up in the top right corner. http://www.openstreetmap.org/ The easiest way to edit the data is probably the Flash-based browser editor called Potlatch. Log in to OSM using the account you just created... (Go here, and click on log in in the top right corner. http://www.openstreetmap.org/) ...then move the map to the area you are interested in. At the top of the map is a tab marked Edit. Click on it, then select Edit with save. Now you can see the lines and points of the vector data in your browser. They are live and editable. Find the object you wish to change and click on it. Its properties will appear in the lower half of the window and are simple tag/value pairs. For the case of a typo, find the tag/value with the typo, click on it, fix it and hit enter. Now hit 'Save' at the bottom right. Done! You might need to wait for a short time for your changes to be propagated through the database and various mirrors, but you knew that. That was a whirlwind guide to editing the data. I strongly suggest you take some time and read the Beginners' Guide in its entirety here: http://wiki.openstreetmap.org/wiki/Beginners%27_Guide Also, if you don't like Flash (and/or don't like Potlatch) then try any of the other editors such as JOSM or Merkaartor. There are two important rules when dabbling with OSM data. 1) Don't copy other maps or data sources. 2) Have fun! 73, Andrew ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
On Fri, Jul 9, 2010 at 6:59 AM, Curt, WE7U curt.w...@gmail.com wrote: Here I saw problems with the Canadian border -and- the west border of Whatcom county, plus a typo: Insterstate 90 at Snoqualmie Pass. I'm sure I'll find more as I play. If someone who's familiar with OSM knows the easiest method for updating the database, please let all of us know. The easiest solution is to do what Andrew has already done... get you to fix it yourself. I was looking to see if I could find the issues you are trying to point out, but it is a little difficult to find right where you are looking at. If you are looking at the OSM map, in the bottom right, there are a couple links. Hit the permalink, and the URL will change. Copy the URL, and paste that into a message. Anyone clicking on that URL link will be taken to the exact view that you were looking at. Here's a link to Point Roberts. http://www.openstreetmap.org/?lat=48.9903lon=-123.0332zoom=13layers=00B0FTF This is the Cycle Map rendering. I chose that since the Cycle Map rendering shows county outlines. If you look, you can see the county outline (dotted line) doesn't quite follow the coast line. This is because there was a bulk import of Tiger data for the USA. As we all know, the Tiger data is less than perfect. The good thing about OSM is that anyone can create a user account, and with a little pointing and clicking, fix the poor Tiger data, and make the OSM map better. James VE6SRV ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
[Xastir] OSM Example DBFAWK File
On Thu, 8 Jul 2010, James Ewen wrote:
So, you state that you would like to have better looking maps, and you
hate the existing esoteric dbfawk files, but then sum it up by giving
up and just asking someone else to create a dbfawk file that may or
may not make things look the way you like, and even at that not have
the ability to render the final image in a visually pleasing manner?
I haven't had time to look at dbfawk's for OSM Shapefiles (until
just now), but figured somebody would get around to it sooner or
later. What will happen is this: Somebody will spend the time to
do it and get Xastir to render the maps. Somebody else will come
along and say: Why don't the maps look like, or as nice as, the
ones we get online in raster format?. That has happened with
Tigermaps in the past.
The good news is that I just went here (found the link in an earlier
message to the Xastir list by yours truly):
http://wiki.openstreetmap.org/wiki/Shapefiles
and downloaded the Cloudmade Shapefiles for North
America/USA/Washington in the form of washington.shapefiles.zip
(at 58.8 MB). Unzipped into my maps directory, indexed new maps in
Xastir, and I have blazingly fast vector OSM maps in Xastir. Of
course no labels on anything yet (one of the limitations of
Shapefiles is that there is no standard for the DBF file
order/contents).
So... With a small amount of time I should be able to run a few
commands like:
dbfinfo washington_highway.shp | head
Info for washington_highway.shp
4 Columns, 343960 Records in file
TYPE string (20,0)
NAME string (115,0)
ONEWAY string (10,0)
LANES integer (11,0)
Then write up a quick dbfawk for each that will display the files in
the correct font size, colors, etc. dbfinfo is from the
shapelib/contrib directory and I've had that installed for years.
What is needed by any interested parties in doing the same, or
improving the dbfawk work done by others: Shapelib:
Install compile, including the contrib area. Text editor of your
choice. Simple huh?
Here's Tom's dbfawk tutorial:
http://pages.swcp.com/~russo/shape_web/tutorial.html
and the Xastir Wiki page that I think he's moving it to (the Wiki
link listed in the above tutorial page is wrong):
http://www.xastir.org/wiki/HowTo:DBFAWK
Included below is the washington_highway.dbfawk file I just
created. I couldn't get the lanes variable set properly from the
LANES field in the dbf file, so I hard-coded the values. Perhaps
someone can take this example file, pretty it up a bit, fix the
few problems, and duplicate/extend it for the rest of the Shapefiles
available from the OSM Shapefiles download area.
Have fun, and please remember to contribute you mods back to the
group so that everyone can benefit!
--
Curt, WE7U. http://www.eskimo.com/~archer
APRS: Where it's at!http://www.xastir.org
Lotto: A tax on people who are bad at math. - unknown
Windows: Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me: I picked the coordinate system!
-
# $Id: $
#
# Copyright (C) 2003-2010 The Xastir Group
#
# This dbfawk file is used to map arbitrary dbf data that accompanies
# a shapefile into Xastir canoncical values of:
# key - search key
# lanes - width of feature (usually a road but applies to
# rivers, etc. too)
# color - color to draw the road
# name- name of the road for labels
# filled - whether a polygon is drawn filled or not
# fill_color - color to fill polygon with
# pattern - line pattern for road, river, etc. (0 - solid; 1 -
# dash; 2 - double dash)
# display_level - highest zoom level at which to display the
# feature
# label_level - highest zoom level at which to display the label
# symbol - 3 char 'TIO': table, ID, overlay
# NOTE: This file format is modeled after awk but is nowhere near awk
# compatible.
#
# This file is used to map OSM shapefiles by Cloudmade which are
# named *_highway.dbf.
# BEGIN is called once per dbf file which contains multiple records.
BEGIN {
# dbfinfo is the signature of the dbf file listing the column names in order.
# dbfinfo should match the dbf file that we say this dbfawk file goes with.
dbfinfo=TYPE:NAME:ONEWAY:LANES;
# dbffields is which of the above fields we actually want to look at.
# No point reading dbffields that are not looked at further.
dbffields=TYPE:NAME:ONEWAY:LANES;
}
# BEGIN_RECORD is called once per dbf record which contains multiple
# fields.
# Use this rule to re-initialize variables between records.
# use color 11 to highlight stuff that isn't properly mapped.
BEGIN_RECORD {key=; lanes=1; color=8; fill_color=11; name=; filled=0; pattern=0;
display_level=8192; label_level=32; label_color=8; font_size=0; symbol=}
# per-field rules are applied to the dbffields
Re: [Xastir] OSM Example DBFAWK File
Hi,
I've a few dbfawk's done. The OSM patches were released before I got back to
looking at them further.
http://www.ei7ig.org/xastir/dbfawk/
I must have neglected to post the link to the list previously, apologies
Regards
de John
EI7IG
On 8 Jul 2010, at 09:33, Curt, WE7U wrote:
On Thu, 8 Jul 2010, James Ewen wrote:
So, you state that you would like to have better looking maps, and you
hate the existing esoteric dbfawk files, but then sum it up by giving
up and just asking someone else to create a dbfawk file that may or
may not make things look the way you like, and even at that not have
the ability to render the final image in a visually pleasing manner?
I haven't had time to look at dbfawk's for OSM Shapefiles (until
just now), but figured somebody would get around to it sooner or
later. What will happen is this: Somebody will spend the time to
do it and get Xastir to render the maps. Somebody else will come
along and say: Why don't the maps look like, or as nice as, the
ones we get online in raster format?. That has happened with
Tigermaps in the past.
The good news is that I just went here (found the link in an earlier
message to the Xastir list by yours truly):
http://wiki.openstreetmap.org/wiki/Shapefiles
and downloaded the Cloudmade Shapefiles for North
America/USA/Washington in the form of washington.shapefiles.zip
(at 58.8 MB). Unzipped into my maps directory, indexed new maps in
Xastir, and I have blazingly fast vector OSM maps in Xastir. Of
course no labels on anything yet (one of the limitations of
Shapefiles is that there is no standard for the DBF file
order/contents).
So... With a small amount of time I should be able to run a few
commands like:
dbfinfo washington_highway.shp | head
Info for washington_highway.shp
4 Columns, 343960 Records in file
TYPE string (20,0)
NAME string (115,0)
ONEWAY string (10,0)
LANES integer (11,0)
Then write up a quick dbfawk for each that will display the files in
the correct font size, colors, etc. dbfinfo is from the
shapelib/contrib directory and I've had that installed for years.
What is needed by any interested parties in doing the same, or
improving the dbfawk work done by others: Shapelib:
Install compile, including the contrib area. Text editor of your
choice. Simple huh?
Here's Tom's dbfawk tutorial:
http://pages.swcp.com/~russo/shape_web/tutorial.html
and the Xastir Wiki page that I think he's moving it to (the Wiki
link listed in the above tutorial page is wrong):
http://www.xastir.org/wiki/HowTo:DBFAWK
Included below is the washington_highway.dbfawk file I just
created. I couldn't get the lanes variable set properly from the
LANES field in the dbf file, so I hard-coded the values. Perhaps
someone can take this example file, pretty it up a bit, fix the
few problems, and duplicate/extend it for the rest of the Shapefiles
available from the OSM Shapefiles download area.
Have fun, and please remember to contribute you mods back to the
group so that everyone can benefit!
--
Curt, WE7U. http://www.eskimo.com/~archer
APRS: Where it's at!http://www.xastir.org
Lotto: A tax on people who are bad at math. - unknown
Windows: Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me: I picked the coordinate system!
-
# $Id: $
#
# Copyright (C) 2003-2010 The Xastir Group
#
# This dbfawk file is used to map arbitrary dbf data that accompanies
# a shapefile into Xastir canoncical values of:
# key - search key
# lanes - width of feature (usually a road but applies to
# rivers, etc. too)
# color - color to draw the road
# name- name of the road for labels
# filled - whether a polygon is drawn filled or not
# fill_color - color to fill polygon with
# pattern - line pattern for road, river, etc. (0 - solid; 1 -
# dash; 2 - double dash)
# display_level - highest zoom level at which to display the
# feature
# label_level - highest zoom level at which to display the label
# symbol - 3 char 'TIO': table, ID, overlay
# NOTE: This file format is modeled after awk but is nowhere near awk
# compatible.
#
# This file is used to map OSM shapefiles by Cloudmade which are
# named *_highway.dbf.
# BEGIN is called once per dbf file which contains multiple records.
BEGIN {
# dbfinfo is the signature of the dbf file listing the column names in
order.
# dbfinfo should match the dbf file that we say this dbfawk file goes with.
dbfinfo=TYPE:NAME:ONEWAY:LANES;
# dbffields is which of the above fields we actually want to look at.
# No point reading dbffields that are not looked at further.
dbffields=TYPE:NAME:ONEWAY:LANES;
}
#
Re: [Xastir] OSM Example DBFAWK File
Heyho, thanks Curt.
See, that is what i meant: you got the ball rolling in a couple of minutes,
while i was fighting my way and failing to get that dbfinfo running on my Mac.
Thanks a lot!
Thomas VA3TSE
Am 08.07.2010 um 11:19 schrieb Curt, WE7U:
A slightly better version:
--
# $Id: $
#
# Copyright (C) 2003-2010 The Xastir Group
#
# This dbfawk file is used to map arbitrary dbf data that
# accompanies a shapefile into Xastir canoncical values of:
# key - search key
# lanes - width of feature (usually a road but applies to
# rivers, etc. too)
# color - color to draw the road
# name- name of the road for labels
# filled - whether a polygon is drawn filled or not
# fill_color - color to fill polygon with
# pattern - line pattern for road, river, etc. (0 - solid; 1 -
# dash; 2 - double dash)
# display_level - highest zoom level at which to display the
# feature
# label_level - highest zoom level at which to display the label
# symbol - 3 char 'TIO': table, ID, overlay
# NOTE: This file format is modeled after awk but is nowhere near
# awk compatible.
#
# This file is used to map OSM shapefiles by Cloudmade which are
# named *_highway.dbf.
# BEGIN is called once per dbf file which contains multiple records.
BEGIN {
# dbfinfo is the signature of the dbf file listing the column
# names in order. dbfinfo should match the dbf file that we say
# this dbfawk file goes with.
dbfinfo=TYPE:NAME:ONEWAY:LANES;
# dbffields is which of the above fields we actually want to look
# at. No point reading dbffields that are not looked at further.
dbffields=TYPE:NAME:ONEWAY:LANES;
}
# BEGIN_RECORD is called once per dbf record which contains multiple
# fields.
# Use this rule to re-initialize variables between records.
# use color 11 to highlight stuff that isn't properly mapped.
BEGIN_RECORD {key=; lanes=1; color=8; fill_color=11; name=; filled=0;
pattern=0; display_level=8192; label_level=32; label_color=8; font_size=0;
symbol=}
# per-field rules are applied to the dbffields that are read from
# each record.
# select the name given in the record
/^NAME=United States Highway (.*)$/ {name=$(name)US $1; next}
/^NAME=State Highway (.*)$/ {name=$(name)Hwy $1; next}
/^NAME=State Route (.*)$/ {name=$(name)SR-$1; next}
/^NAME=United States Highway (.*)$/ {name=$(name)US $1; next}
/^NAME=United States Highway (.*)$/ {name=$(name)US $1; next}
/^NAME=Interstate (.*) Northbound$/ {name=$(name)I-$1 N; next}
/^NAME=Interstate (.*) Southbound$/ {name=$(name)I-$1 S; next}
/^NAME=Interstate (.*) Eastbound$/ {name=$(name)I-$1 E; next}
/^NAME=Interstate (.*) Westbound$/ {name=$(name)I-$1 W; next}
/^NAME=Interstate (.*)$/ {name=$(name)I-$1; next}
/^NAME=Washington Highway (.*)$/ {name=$(name)Hwy $1; next}
/^NAME=(.+)$/ {name=$1;next}
#/^LANES=(.+)$/ {lanes=$1;}
# TYPE:
/^TYPE=abandoned/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=bridleway/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=construction/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=crossing/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=cycleway/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=driveway/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=footway/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=ford/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=living_street/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
# Note: No display_level or label_level
/^TYPE=motorway/ {lanes=3; color=2; label_level=65536; font_size=3; next}
# Note: No display_level
/^TYPE=motorway_link/ {lanes=3; color=2; label_level=16; font_size=1; next}
/^TYPE=path/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=pedestrian/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=platform/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=primary/ {lanes=2; color=8; display_level=512; label_level=128;
font_size=1; next}
/^TYPE=primary_link/ {lanes=2; color=8; display_level=512; label_level=128;
font_size=1; next}
/^TYPE=raceway/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=ramp/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=residential/ {lanes=1; color=7; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=road/ {lanes=1; color=4; display_level=64; label_level=16;
font_size=1; next}
/^TYPE=secondary/ {lanes=1; color=8; display_level=256; label_level=64;
font_size=1; next}
/^TYPE=secondary_link/ {lanes=1; color=8; display_level=256; label_level=64;
font_size=1;
Re: [Xastir] OSM Example DBFAWK File
On 8 Jul 2010, at 10:41, Curt, WE7U wrote: On Thu, 8 Jul 2010, Curt, WE7U wrote: A slightly better version: Yet better. I just borrowed some of the colors from John Ronan's version, but I also notice that his dbfawk signature doesn't match mine, so his version is probably not for the Cloudmade Shapefiles? Mine were done with Geofabrick.de, should I change? I'm curious now! John ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
On Thu, 8 Jul 2010, John Ronan wrote: Mine were done with Geofabrick.de, should I change? I'm curious now! I looked at the 2nd site listed on the OSM Shapefiles page and it didn't have any U.S. maps, so my choices were more limited. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
Snagged the cloudmade shapefile. That looks pretty reasonable here as well. John On 8 Jul 2010, at 10:53, Curt, WE7U wrote: On Thu, 8 Jul 2010, John Ronan wrote: Mine were done with Geofabrick.de, should I change? I'm curious now! I looked at the 2nd site listed on the OSM Shapefiles page and it didn't have any U.S. maps, so my choices were more limited. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
http://www.vliz.be/vmdcdata/vlimar/downloads.php the last item: SeaVoX Salt and Fresh Water Body Gazetteer seems to be worth a try??? Am 08.07.2010 um 13:16 schrieb Curt, WE7U: On Thu, 8 Jul 2010, John Ronan wrote: Snagged the cloudmade shapefile. That looks pretty reasonable here as well. It seems to have nearly everything. What's missing is a polygon Shapefile for the ocean, or a Shapefile for the landmasses. There's a lot of water around here and a very irregular coastline. It's nice to know where the land ends and the water begins. If one or the other Shapefile existed I could fill it in and then set the background color appropriately. Since there's no Shapefile for either I have to rely on the coastline and roads to decide which parts are land. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
On Thu, 8 Jul 2010, Curt, WE7U wrote: Before I was done I completed tweaked dbfawk files for each of the Cloudmade Shapefiles for Washington State. These can probably be extended to match others in the set and put into the Xastir global dbfawk area, as long as there aren't any conflicts in the DBF signature for other dbfawks we already have. I'll try to get this done in the next day or two. I'm sure they could use some more tweaking, but they're a start. Until I get to it, my sample dbfawk's for OSM Cloudmade-version are here: http://www.eskimo.com/~archer/cloudmade.tgz That address may be temporarily unavailable soon as they want money again and gave me the notice _after_ it had expired. Get the file quickly if you're going to get it! It goes with the Cloudmade Shapefiles for North America/USA/Washington State. The other place I would normally upload files crashed yesterday and the admin is down at the site now repairing it, so perhaps I'll have another URL shortly if the above URL goes silent. John: I made some tweaks since I sent them to you. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] OSM Example DBFAWK File
Those are not too bad Curt, very nice in fact. Now for my long time dream color the county boardsred. On Jul 8, 2010, at 2:49 PM, Curt, WE7U wrote: On Thu, 8 Jul 2010, Curt, WE7U wrote: Before I was done I completed tweaked dbfawk files for each of the Cloudmade Shapefiles for Washington State. These can probably be extended to match others in the set and put into the Xastir global dbfawk area, as long as there aren't any conflicts in the DBF signature for other dbfawks we already have. I'll try to get this done in the next day or two. I'm sure they could use some more tweaking, but they're a start. Until I get to it, my sample dbfawk's for OSM Cloudmade-version are here: http://www.eskimo.com/~archer/cloudmade.tgz That address may be temporarily unavailable soon as they want money again and gave me the notice _after_ it had expired. Get the file quickly if you're going to get it! It goes with the Cloudmade Shapefiles for North America/USA/Washington State. The other place I would normally upload files crashed yesterday and the admin is down at the site now repairing it, so perhaps I'll have another URL shortly if the above URL goes silent. John: I made some tweaks since I sent them to you. -- Curt, WE7U. http://www.eskimo.com/~archer APRS: Where it's at!http://www.xastir.org Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system! ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
