At 2012-01-15 05:35, Mike N wrote:
On 1/15/2012 8:28 AM, Nathan Edgars II wrote:
Actually the script also expanded the W to West. But my point is that it
is a TIGER entry error, and any future script needs to take into account
that these exist and people may have already fixed them to the
At 2012-02-06 16:19, Paul Johnson wrote:
On Mon, 2012-02-06 at 17:14 -0600, Martijn van Exel wrote:
On Mon, Feb 6, 2012 at 5:06 PM, Nick Hocking nick.hock...@gmail.com
wrote:
[..]and copy in the TIGER 2011 name from the TMS overlay (remembering
to un-abreviate as you go).
As a
At 2012-01-15 10:11, Ian Dees wrote:
In order to assist with road name checking I've set up a Mapnik layer
rendering from TIGER 2011 ROADS data.
I also stumbled across the fact that the Census is making some of TIGER
available as a WMS, too: http://wiki.openstreetmap.org/wiki/TIGER_2011#WMS
On Fri, Feb 17, 2012 at 7:14 AM, Alan Mintz
alan_mintz+...@earthlink.net wrote:
Better quality will result if we verify from additional sources, like those
available from many counties.
The best quality will result if we grab a GPS unit and a camera and GO
there ourselves. Just sayin' :)
On Mon, Jan 16, 2012 at 6:34 PM, Val Kartchner val...@gmail.com wrote:
In my area I know of two separate streets named E Avenue and an E
Street.
Boston has E St, intersecting W 1st St, between D St and F St as you'd
expect. But W 1st St *crosses* E 1st St at the grid discontinuity (extends
On Fri, Feb 17, 2012 at 8:35 AM, Toby Murray toby.mur...@gmail.com wrote:
On Fri, Feb 17, 2012 at 7:14 AM, Alan Mintz
alan_mintz+...@earthlink.net wrote:
Better quality will result if we verify from additional sources, like those
available from many counties.
The best quality will result if
At 2012-01-18 13:43, Nick Hocking wrote:
http://www.openstreetmap.org/?lat=35.996927lon=-114.925865zoom=18layers=M
TIGER 2011, google maps, and some other sources show the intersection
as
Shootout Place and Cattle Ranch Place. However TIGER 2010 and
Google Streetview indicate the inersection is
On 2/17/2012 10:05 AM, Martijn van Exel wrote:
On the topic of TIGER layers: Harry Wood made an interesting
suggestion in the comments section of my blog post on road analysis
(see other post): wouldn't it be interesting to crowdsource
particularly problematic (in terms of alignment) areas of
At 2012-02-17 06:35, Toby Murray wrote:
On Fri, Feb 17, 2012 at 7:14 AM, Alan Mintz
alan_mintz+...@earthlink.net wrote:
Better quality will result if we verify from additional sources, like those
available from many counties.
The best quality will result if we grab a GPS unit and a camera
Found some more evidence.
In GISMO, if you zoom far enough in, the segment in question gets a label -
Shootout Pl.
I also found street centerlines at
http://gisgate.co.clark.nv.us/gismo/freedataNEW.htm in crscl-shp.zip
(streets_l dated 2012-01-27) which confirms the name Shootout Place.
On 02/17/12 22:01, Paul Johnson wrote:
On Fri, Feb 17, 2012 at 12:02 AM, Alan Mintz
alan_mintz+...@earthlink.net mailto:alan_mintz%2b...@earthlink.net
wrote:
At 2012-01-15 05:35, Mike N wrote:
On 1/15/2012 8:28 AM, Nathan Edgars II wrote:
Actually the script also
On Fri, Feb 17, 2012 at 12:01 PM, Paul Johnson ba...@ursamundi.org wrote:
but overall, the automation saved countless hours of manual name expansion
for the minor cost of having to deal with a very small number of largely
regionally-isolated edge cases.
Can someone explain the original point
At 2012-02-17 12:50, Mike N wrote:
On 2/17/2012 3:02 AM, Alan Mintz wrote:
if the name has been edited by a human, it should not be updated by a
bot, or even another human unless they are willing to prove their edit.
I've edited thousands of names based on photo surveys and official
record
On 2/17/2012 4:41 PM, TC Haddad wrote:
For example: in Portland all the expanded quadrant names (NE,NW, SE, SW)
really detract from the experience of using osm extracts on handheld
GPS. All the streets in an area of interest end up looking like they
have the same name because all that fits on
On Fri, Feb 17, 2012 at 1:41 PM, TC Haddad tchad...@gmail.com wrote:
On Fri, Feb 17, 2012 at 12:01 PM, Paul Johnson ba...@ursamundi.orgwrote:
but overall, the automation saved countless hours of manual name
expansion for the minor cost of having to deal with a very small number of
largely
On Fri, Feb 17, 2012 at 2:32 PM, Nathan Edgars II nerou...@gmail.comwrote:
If the directional prefixes are not generally used as part of the name,
they should probably not be in the name tag, but instead as an address tag
(I've used addr:direction e.g. http://www.openstreetmap.org/**
You're assuming the street signs make sense. Do you preserve signs with
mistakes or omissions?
In Wilsonville, OR, there are some signs for St Moritz Loop and St. Moritz
Loop. Yes, with and without the period, and both expand to Saint. There
are also plenty of signs that leave out the
Southwest Town Center Loop West comes to mind as a great example of just
plain brain damaged street naming Wilsonville tends to have.
On Fri, Feb 17, 2012 at 2:55 PM, Dion Dock dion_d...@comcast.net wrote:
You're assuming the street signs make sense. Do you preserve signs with
mistakes or
Nathan Edgars II nerou...@gmail.com wrote:
On 2/17/2012 4:41 PM, TC Haddad wrote:
For example: in Portland all the expanded quadrant names (NE,NW, SE,
SW)
really detract from the experience of using osm extracts on handheld
GPS. All the streets in an area of interest end up looking like
On Fri, Feb 17, 2012 at 2:42 PM, Paul Johnson ba...@ursamundi.org wrote:
On Fri, Feb 17, 2012 at 1:41 PM, TC Haddad tchad...@gmail.com wrote:
On Fri, Feb 17, 2012 at 12:01 PM, Paul Johnson ba...@ursamundi.orgwrote:
but overall, the automation saved countless hours of manual name
expansion
On 02/18/12 01:43, TC Haddad wrote:
On Fri, Feb 17, 2012 at 2:42 PM, Paul Johnson ba...@ursamundi.org
mailto:ba...@ursamundi.org wrote:
On Fri, Feb 17, 2012 at 1:41 PM, TC Haddad tchad...@gmail.com
mailto:tchad...@gmail.com wrote:
On Fri, Feb 17, 2012 at 12:01 PM, Paul Johnson
On 2/17/2012 5:44 PM, Paul Johnson wrote:
On Fri, Feb 17, 2012 at 2:32 PM, Nathan Edgars II nerou...@gmail.com
mailto:nerou...@gmail.com wrote:
If the directional prefixes are not generally used as part of the
name, they should probably not be in the name tag, but instead as an
On 02/18/12 02:28, TC Haddad wrote:
On Fri, Feb 17, 2012 at 4:10 PM, Rich ric...@nakts.net
mailto:ric...@nakts.net wrote:
it wouldn't be the device renderer (in most cases) but the the tools
used to process the data - for example, mkgmap would do the
shortening for garmin maps
On 18 February 2012 00:43, TC Haddad tchad...@gmail.com wrote:
On Fri, Feb 17, 2012 at 2:42 PM, Paul Johnson ba...@ursamundi.org wrote:
Sounds like a problem for the renderer to solve. It's possible for
renderers to easily create abbreviations when full words are not desired,
but impossible
On 15 January 2012 14:35, Mike N nice...@att.net wrote:
On 1/15/2012 8:28 AM, Nathan Edgars II wrote:
Actually the script also expanded the W to West. But my point is that it
is a TIGER entry error, and any future script needs to take into account
that these exist and people may have already
At 2012-02-17 13:41, TC Haddad wrote:
Can someone explain the original point of name expansion? Is it so that
devices that give audio directions using text-to-speech can read fluently?
Or was it really all about saving time?
Because there are other use cases where expanded names are not
26 matches
Mail list logo
