I'm not really speaking for/against abbreviations in general, just
adding information. It would definitely be Pkwy and Blvd. The USPS has
documented standards for prefixes, suffixes and any other fixes you
may want. 208 pages worth:
http://pe.usps.com/cpim/ftp/pubs/pub28/pub28.pdf
Toby
On Tue,
On Tue, Aug 3, 2010 at 2:49 AM, Toby Murray toby.mur...@gmail.com wrote:
On Tue, Aug 3, 2010 at 1:18 AM, Nathan Edgars II nerou...@gmail.com wrote:
How do you abbreviate Boulevard? Blvd or Bv? How about Parkway? Pkwy,
Pky, or Py? The same road (Central Florida Parkway) has all three on
signs
One more specific question below:
On Mon, 2 Aug 2010, Kevin Atkinson wrote:
On Mon, 2 Aug 2010, Alan Mintz wrote:
See below for general comments:
Some Examples)
To encode South 700 East in Salt Lake City:
name = S. 700 East
name_prefix = included
alt_name = South 700 East
I would
On Tue, Aug 3, 2010 at 2:57 AM, Nathan Edgars II nerou...@gmail.com wrote:
On Tue, Aug 3, 2010 at 2:49 AM, Toby Murray toby.mur...@gmail.com wrote:
On Tue, Aug 3, 2010 at 1:18 AM, Nathan Edgars II nerou...@gmail.com wrote:
How do you abbreviate Boulevard? Blvd or Bv? How about Parkway? Pkwy,
On Tue, Aug 3, 2010 at 9:11 AM, Richard Weait rich...@weait.com wrote:
I see these abbreviation errors in other map products. I have a
navigation device that announces County Road 33 as Co-Road
Thirty-three Surely we can aspire to do better than propagating the
errors of other projects?
I'm almost done with this script. It's not a full bot, but instead
modifies an osm file which I will read back into JOSM and upload the
changed parts (or if that doesn't work use one of the upload scripts).
Changes in what It will do noted below.
On Sat, 31 Jul 2010, Kevin Atkinson wrote:
On Tue, Aug 3, 2010 at 4:05 PM, Kevin Atkinson ke...@atkinson.dhs.org wrote:
I'm almost done with this script. It's not a full bot, but instead modifies
an osm file which I will read back into JOSM and upload the changed parts
(or if that doesn't work use one of the upload scripts). Changes in
On Tue, Aug 3, 2010 at 3:57 PM, Richard Weait rich...@weait.com wrote:
On Tue, Aug 3, 2010 at 4:05 PM, Kevin Atkinson ke...@atkinson.dhs.org
wrote:
I'm almost done with this script. It's not a full bot, but instead
modifies
an osm file which I will read back into JOSM and upload the
On Tue, 3 Aug 2010, Richard Weait wrote:
Whoa. Are you considering adding a period . to the key? Might that
mess up postgres? From
http://www.postgresql.org/docs/8.2/static/sql-syntax-lexical.html
The period (.) is used in numeric constants, and to separate schema,
table, and column names.
On Tue, 3 Aug 2010, Val Kartchner wrote:
On Tue, 2010-08-03 at 14:05 -0600, Kevin Atkinson wrote:
I'm almost done with this script. It's not a full bot, but instead
modifies an osm file which I will read back into JOSM and upload the
changed parts (or if that doesn't work use one of the
OK. So There is clearly no agreement on the abbreviation of road types
(Street, Way, etc). So what about these specific exceptions. I will
assume silence means agreement :)
Rather than United Stated Highway 29 Frontage Road just U.S. 29
Frontage Road or maybe US 29 Frontage Road.
Why.
On 3 Aug 2010, at 22:32 , Kevin Atkinson wrote:
OK. So There is clearly no agreement on the abbreviation of road types
(Street, Way, etc). So what about these specific exceptions. I will assume
silence means agreement :)
Rather than United Stated Highway 29 Frontage Road just U.S.
On Tue, 3 Aug 2010, Kevin Atkinson wrote:
OK. So There is clearly no agreement on the abbreviation of road types
(Street, Way, etc). So what about these specific exceptions. I will assume
silence means agreement :)
So to be clear. This mail has nothing to do with my proposed changes, or
13 matches
Mail list logo