> Alan Mintz alan_mintz+...@earthlink.net
> For FM 1960, I'd use:> network=US:TX> ref="FM 1960"
I'd prefer to put all of the network information in the "network" tag, keeping the "ref" tag as a pure container for "the unique designation within the network":
network=US:TX:FARM
ref=1960
Similar
Trying to figure out how to tag certain things in Massachusetts and was looking
for some clarification on appropriate tagging.
1. The things on the Mass Pike that people tend to call rest areas should be
tagged highway=services, I think.
2. Highway depots, salt sheds, fiber optic lines, and micro
On Tue, Aug 23, 2011 at 10:20 AM, Metcalf, Calvin (DOT)
wrote:
> Trying to figure out how to tag certain things in Massachusetts and was
> looking for some clarification on appropriate tagging.
> 1. The things on the Mass Pike that people tend to call rest areas should be
> tagged highway=services
The scheme sounds simple enough at first but is it robust and usable? If
not what would it take to make it so? Here are some of my thought on it.
The way I see it you take the last element of the network tag (FARM in this
case) and that is the network.
Ref is the ID in that network
The first par
On Mon, 2011-08-22 at 23:53 -0600, Martijn van Exel wrote:
> Hi all,
>
> Is there a ready-made, reasonably frequently updated planet extract
> for the contiguous US available somewhere? Right now I am merging the
> partial US extracts made available by Geofabrik, but I'd love to be
> able to get i
These are based off of Lambertus's work here:
http://garmin.openstreetmap.nl
I wrote scripts to joined them myself to lessen the impact of doing a
large join on Lambertus's server. I've also cut them in large longitude
swaths that should fit conveniently on removable media.
ht
6 matches
Mail list logo
