+1 on a parallel/complementary database.
we have lots of Civil War sites here in Georgia that would be fun to
map. it's a timely topic during the sesquicentennial years.
jack
On 3/26/2011 5:57 PM, Richard Welty wrote:
On 3/26/11 5:53 PM, Russ Nelson wrote:
Richard Welty writes:
In some cases, portions of the sites are still extant, and could be shown on
current maps; other portions are no longer in existence, and should show up
only on historical maps, or rendered in a different color, as a historical
overlay. So, the tagging would need to distinguish between the two
On Sat, Mar 26, 2011 at 4:57 PM, Richard Welty rwe...@averillpark.net wrote:
i'm debating whether or not i want to set up a parallel database, using
the OSM design, to contain historical data that can be used in a mashup
with OSM, and opening it up for historically minded mappers to use as
a
I, too, have been thinking that a core+layers approach would be useful in a
number of contexts, primarily conflation between different
databases/datasets. But the same qualities that make it useful for
historical (i.e. Civil War battlefield mapping) might also be useful for
mapping of ephemeral
On Mon, Mar 28, 2011 at 11:14 AM, Steven Johnson sejohns...@gmail.com wrote:
I, too, have been thinking that a core+layers approach would be useful in a
number of contexts, primarily conflation between different
This might be something interesting to do with those servers that the
US local
On 3/28/11 11:22 AM, Richard Weait wrote:
On Mon, Mar 28, 2011 at 11:14 AM, Steven Johnsonsejohns...@gmail.com wrote:
I, too, have been thinking that a core+layers approach would be useful in a
number of contexts, primarily conflation between different
This might be something interesting to
On Mon, Mar 28, 2011 at 10:22 AM, Richard Weait rich...@weait.com wrote:
On Mon, Mar 28, 2011 at 11:14 AM, Steven Johnson sejohns...@gmail.com
wrote:
I, too, have been thinking that a core+layers approach would be useful in
a
number of contexts, primarily conflation between different
At 2011-03-08 06:03, Mike N wrote:
The Motorway Junction tag at
http://wiki.openstreetmap.org/wiki/Motorway_junction has recently had the
exit_to tag added. Old interstate tagging advice at
http://wiki.openstreetmap.org/wiki/Interstate_Highway was to put exit sign
destinations in the name
At 2011-03-23 04:22, Dale Puch wrote:
A quick note, do not confuse public
records as always meaning public domain.
Some states may not have laws specifically preventing agencies from
claiming copyright, not apply to all levels of government, or have
exceptions to which works.
IE. I think it was
At 2011-03-28 09:13, Mike N wrote:
... A different way to ask the question is does it make sense to render
the exit_to at any time?The most likely use of the information is by
navigation utilities - where the actual map rendering will be much more
sparse to limit information to only that
On Mon, Mar 28, 2011 at 12:15 PM, Alan Mintz
alan_mintz+...@earthlink.net wrote:
At 2011-03-23 04:22, Dale Puch wrote:
A quick note, do not confuse public records as always meaning public
domain.
Some states may not have laws specifically preventing agencies from claiming
copyright, not
On 3/28/2011 12:28 PM, Alan Mintz wrote:
In southern California, in my experience, people do not use exit numbers
when giving directions - they use what we would call the name of the
exit, which is usually the name of the street on which the offramp
terminates*. One reason is that exit numbering
Santa Clara county was sued successfully, but not on a federal level. State
of California has the same PD rules and this can be used only for California
state and county data.
Don't have the link available right now but it can be found in the archives
of talk-us
But still you may need to check
On 3/28/11 10:18 AM, Richard Welty wrote:
i will look into where this can be hosted, and look into setting up a
mailing list
for those interested in the project to communicate.
does anyone object to a google groups list named something like
osm-layers?
richard
On Mon, Mar 28, 2011 at 1:40 PM, Richard Welty rwe...@averillpark.net wrote:
On 3/28/11 10:18 AM, Richard Welty wrote:
i will look into where this can be hosted, and look into setting up a
mailing list
for those interested in the project to communicate.
does anyone object to a google groups
On 3/28/11 2:04 PM, Richard Weait wrote:
Yes, but not for the reason you might think. ;-)
Have the conversation here where everybody can participate, or at
least watch in silence. The risk of prematurely splitting off to
another group is that you'll miss some interested parties. If the
In rural areas, the names on the sign tend to be towns that may be
upwards of 10 miles away from the interstate.
Example:
http://www.openstreetmap.org/?lat=39.0631lon=-96.2784zoom=13layers=M
___
Talk-us mailing list
Talk-us@openstreetmap.org
In this picture:
http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg
http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpgWhat
is the proposed tag for the highway=motorway_junction node?
Are we tagging the node with exactly what
On 3/28/2011 3:19 PM, Ian Dees wrote:
In this picture:
http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg
http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpgWhat
is the proposed tag for the highway=motorway_junction node?
On Mon, Mar 28, 2011 at 2:35 PM, Mike N nice...@att.net wrote:
On 3/28/2011 3:19 PM, Ian Dees wrote:
In this picture:
http://www.nomadchallenge.com/wp-content/uploads/2008/08/likelike-highway-honolulu.jpg
On Mon, 2011-03-28 at 14:40 -0500, Ian Dees wrote:
On Mon, Mar 28, 2011 at 2:35 PM, Mike N nice...@att.net wrote:
On 3/28/2011 3:19 PM, Ian Dees wrote:
In this picture:
On Mon, Mar 28, 2011 at 4:00 PM, Andrew Cleveland
evil.salt...@gmail.com wrote:
Though that might be making things more complicated than they need to be.
Yes. It is unreasonable to expect mappers to use special characters.
That is just asking for inconsistencies in our data. IMHO, if it can't
be
Hi Richard,
I *think* the short answer is that you don't have to include the address
point node/way into the interpolated way
I dont know whether or not its the correct way of doing things, but I
know what works with Nominatim
Address points trump interpolation every time
if you have an
On Mon, Mar 28, 2011 at 1:08 PM, Apollinaris Schoell ascho...@gmail.comwrote:
Santa Clara county was sued successfully, but not on a federal level. State
of California has the same PD rules and this can be used only for California
state and county data.
Don't have the link available right now
On 3/28/11 5:13 PM, Antony Pegg wrote:
Hi Richard,
I *think* the short answer is that you don't have to include the
address point node/way into the interpolated way
I dont know whether or not its the correct way of doing things, but
I know what works with Nominatim
Address points trump
On 3/28/2011 5:00 PM, Andrew Cleveland wrote:
Just a nitpick: For exit numbers that consist of both a number and a
letter, should we insert a space? For example 20A vs. 20 A.
The MUTCD (
http://mutcd.fhwa.dot.gov/htm/2009/part2/part2e.htm#section2E31 ) says
Suffix letters shall be used for exit
On 3/28/11 6:21 PM, Nathan Edgars II wrote:
On 3/28/2011 5:00 PM, Andrew Cleveland wrote:
Just a nitpick: For exit numbers that consist of both a number and a
letter, should we insert a space? For example 20A vs. 20 A.
The MUTCD (
http://mutcd.fhwa.dot.gov/htm/2009/part2/part2e.htm#section2E31
On 3/28/2011 12:28 PM, Alan Mintz wrote:
Another is that, for people that have traveled the area extensively, the
name of the exit gives one a far better mental picture of where an exit
is than the postmile-related exit number.
This is an argument where the actual local exit reference would
On Mon, 2011-03-28 at 18:27 -0400, Richard Welty wrote:
On 3/28/11 6:21 PM, Nathan Edgars II wrote:
This seems to be a display choice rather than an actual space in the
exit number.
we should standardize on how we enter them, either space or no space (and no
tricky unicode characters, just
29 matches
Mail list logo
