-----Original Message-----
From: talk-us-requ...@openstreetmap.org
[mailto:talk-us-requ...@openstreetmap.org]
Sent: Wednesday, June 08, 2011 5:35 PM
To: talk-us@openstreetmap.org
Subject: Talk-us Digest, Vol 43, Issue 14
Send Talk-us mailing list submissions to
talk-us@openstreetmap.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openstreetmap.org/listinfo/talk-us
or, via email, send a message with subject or body 'help' to
talk-us-requ...@openstreetmap.org
You can reach the person managing the list at
talk-us-ow...@openstreetmap.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Talk-us digest..."
Today's Topics:
1. East end of I-44 (Re: shields and overlaps)
(Lord-Castillo, Brett)
2. Re: Which county next? (Dale Puch)
3. Re: FYI - user going around changing highway refs just to put
in the "-" and "/" (Nathan Edgars II)
4. Re: Which county next? (Steve Coast)
5. Re: Which county next? (Steve Coast)
----------------------------------------------------------------------
Message: 1
Date: Wed, 8 Jun 2011 17:07:27 -0500
From: "Lord-Castillo, Brett" <blord-casti...@stlouisco.com>
To: "talk-us@openstreetmap.org" <talk-us@openstreetmap.org>
Subject: [Talk-us] East end of I-44 (Re: shields and overlaps)
Message-ID:
<6eadd79a38ef5c439acb793ad7081d7b843d74d...@sssxchgmb1.stlouisco.net>
Content-Type: text/plain; charset="us-ascii"
> > This shot shows the road as all 4 interstates and US-40 at once.
> > http://maps.google.com/?ie=UTF8&ll=38.617642,-90.181049&spn=0.00824,0.013078&z=17&layer=c&cbll=38.617746,-90.181461&panoid=etjY4kn9oqoecsdYSjoXqw&cbp=12,285.92,,0,5.98
> > (This shot is actually from during the realignment, as shown by the I-64
> > detour sign.)
> > As soon as you hit the end of the bridge, the 4 Interstates start splitting
> > up.
>
> Is there any reassurance signage for I-44 in either direction here? This
> is close enough to the I-44/55 junction that the exit 40C overhead could
> easily be implying that it's 'TO' I-44, like exit 1C on I-255 westbound
> is signed US 50/61/67 despite not leading directly to the latter two.
>
> The mileposts display I-55 rather than I-44; is it MoDOT policy to
> always use the lowest number (if both are the same network)?
MoDOT only puts one symbol on a mile marker. Notice that the bridge actually
leads most directly to I-64/US-40; all the other interstates exit, but the mile
marker and reassurance signage only say I-55. I am not sure how the choice is
made which Interstate to use for the reassurance signs and mile markers.
The MoDOT roads on file at MSDIS say that the bridge is all four interstates.
Either as a 3 Interstate + 1 highway shield or 4 Interstate + 1 highway shield,
it still makes an interesting rendering problem.
Brett Lord-Castillo
Information Systems Designer/GIS Programmer
St. Louis County Police
Office of Emergency Management
14847 Ladue Bluffs Crossing Drive
Chesterfield, MO 63017
Office: 314-628-5400
Fax: 314-628-5508
Direct: 314-628-5407
------------------------------
Message: 2
Date: Wed, 8 Jun 2011 18:11:37 -0400
From: Dale Puch <dale.p...@gmail.com>
To: Alan Mintz <alan_mintz+...@earthlink.net>
Cc: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Which county next?
Message-ID: <banlktik2juux6w8hcg5pjk2mte+eynt...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
A few suggestions:
- A way to move the pointer without submitting the location. In case the
pointer is hiding something. Or perhaps a checkbox to temporarily hide the
pointer
- You have a skip button, but no way to determine why it was skipped.
Perhaps add buttons or check boxes for the reason it was skipped. This will
allow revisiting those items that need it by issue, like if better images
become available, or better methods for identifying the point. Possibly
even manually surveying the points. I think this is an important one to
add. Possible skip reasons I can think of. Poor image, empty parcel,
correct location, can't identify location from sat view (apartment, multiple
entrances, multiple buildings ect.)
- Can you overlay a parcel outline to positively identify which parcel
(and it's limits) this refers to.
On Wed, Jun 8, 2011 at 3:43 PM, Alan Mintz <alan_mintz+...@earthlink.net>wrote:
> At 2011-06-08 10:57, Steve Coast wrote:
>
>> Who says it's being done for driving directions?
>>
>
> Is that/will that not be a popular use for OSM? It does not make walking
> directions impossible - just requires the addition of the driveway to the
> map. OTOH, putting the pin on the front door of a building inside a large
> parcel may well leave a driver lost and quite a distance from where he needs
> to be.
>
>
>
> On 6/7/2011 3:28 PM, Alan Mintz wrote:
>>
>>> "The site allows you to drag a pin from where we think an address
>>> currently is to the front door of the property"
>>>
>>> Is that really where we want the pin to be for driving directions? I've
>>> mostly tended to either putting the address info on a complete landuse
>>> polygon, or if a point, placing it on the driveway, just off the street to
>>> which it connects. I swear I read this somewhere as standard practice, and
>>> it makes sense from a navigation standpoint, particularly for rural parcels,
>>> where a "driveway" can be hundreds of meters long and not mapped.
>>>
>>> San Diego County, CA, USA has a bunch of address data from a SanGIS
>>> import.
>>>
>>> --
>>> Alan Mintz <alan_mintz+...@earthlink.net>
>>>
>>>
>>> _______________________________________________
>>> Talk-us mailing list
>>> Talk-us@openstreetmap.org
>>> http://lists.openstreetmap.org/listinfo/talk-us
>>>
>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-us
>>
>
> --
>
> Alan Mintz <alan_mintz+...@earthlink.net>
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us
>
--
Dale Puch
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openstreetmap.org/pipermail/talk-us/attachments/20110608/94b1458f/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 08 Jun 2011 18:31:24 -0400
From: Nathan Edgars II <nerou...@gmail.com>
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] FYI - user going around changing highway refs
just to put in the "-" and "/"
Message-ID: <4deff83c.5080...@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 5/29/2011 4:08 AM, James Mast wrote:
> I just happened to notice this guy tonight was going around and editing
> the "ref" tags on highways in the US just to replace the space and put
> in the hyphen. (I noticed this when going to load the I-77 NC relation
> to add in speed limits I saw and wrote down on a recent trip to
> Charlotte because he changed a name of a way.) He's done in this in
> several places recently. It *seems* that all he does in the changesets
> is change the "ref" tags or expands the name tags fully (AVE > Avenue).
> Of course, it's one of those guys that uses Potlatch2 and doesn't even
> put in a comment.. (I really hate those kinds of people). The user is
> 'chdr'. http://www.openstreetmap.org/user/chdr
Another real doozy: http://www.openstreetmap.org/browse/way/33263209/history
------------------------------
Message: 4
Date: Wed, 08 Jun 2011 15:34:00 -0700
From: Steve Coast <st...@asklater.com>
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Which county next?
Message-ID: <4deff8d8.7020...@asklater.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 6/8/2011 12:43 PM, Alan Mintz wrote:
> Is that/will that not be a popular use for OSM? It does not make
> walking directions impossible - just requires the addition of the
> driveway to the map. OTOH, putting the pin on the front door of a
> building inside a large parcel may well leave a driver lost and quite
> a distance from where he needs to be.
Ah I see. Well the question is really whether the centroid is better
than the front door. My argument would be no, the centroid is usually in
a pretty random place. The front door with some clever processing will
get you the house and also the driveway shapes.
Steve
>
>
>> On 6/7/2011 3:28 PM, Alan Mintz wrote:
>>> "The site allows you to drag a pin from where we think an address
>>> currently is to the front door of the property"
>>>
>>> Is that really where we want the pin to be for driving directions?
>>> I've mostly tended to either putting the address info on a complete
>>> landuse polygon, or if a point, placing it on the driveway, just off
>>> the street to which it connects. I swear I read this somewhere as
>>> standard practice, and it makes sense from a navigation standpoint,
>>> particularly for rural parcels, where a "driveway" can be hundreds
>>> of meters long and not mapped.
>>>
>>> San Diego County, CA, USA has a bunch of address data from a SanGIS
>>> import.
>>>
>>> --
>>> Alan Mintz <alan_mintz+...@earthlink.net>
>>>
>>>
>>> _______________________________________________
>>> Talk-us mailing list
>>> Talk-us@openstreetmap.org
>>> http://lists.openstreetmap.org/listinfo/talk-us
>>
>> _______________________________________________
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/talk-us
>
> --
> Alan Mintz <alan_mintz+...@earthlink.net>
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us
>
------------------------------
Message: 5
Date: Wed, 08 Jun 2011 15:34:56 -0700
From: Steve Coast <st...@asklater.com>
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Which county next?
Message-ID: <4deff910.4030...@asklater.com>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
On 6/8/2011 3:11 PM, Dale Puch wrote:
> A few suggestions:
>
> * A way to move the pointer without submitting the location. In
> case the pointer is hiding something. Or perhaps a checkbox to
> temporarily hide the pointer
>
Huh... I'll look at that.
> * You have a skip button, but no way to determine why it was
> skipped. Perhaps add buttons or check boxes for the reason it
> was skipped. This will allow revisiting those items that need
> it by issue, like if better images become available, or better
> methods for identifying the point. Possibly even manually
> surveying the points. I think this is an important one to add.
> Possible skip reasons I can think of. Poor image, empty parcel,
> correct location, can't identify location from sat view
> (apartment, multiple entrances, multiple buildings ect.)
>
Yes, there are lots of possible reasons. In the end though it's a
tradeoff between a fun and simple UI and data capture.
> * Can you overlay a parcel outline to positively identify which
> parcel (and it's limits) this refers to.
>
Nope, can't do that.
>
>
> On Wed, Jun 8, 2011 at 3:43 PM, Alan Mintz
> <alan_mintz+...@earthlink.net <mailto:alan_mintz%2b...@earthlink.net>>
> wrote:
>
> At 2011-06-08 10:57, Steve Coast wrote:
>
> Who says it's being done for driving directions?
>
>
> Is that/will that not be a popular use for OSM? It does not make
> walking directions impossible - just requires the addition of the
> driveway to the map. OTOH, putting the pin on the front door of a
> building inside a large parcel may well leave a driver lost and
> quite a distance from where he needs to be.
>
>
>
> On 6/7/2011 3:28 PM, Alan Mintz wrote:
>
> "The site allows you to drag a pin from where we think an
> address currently is to the front door of the property"
>
> Is that really where we want the pin to be for driving
> directions? I've mostly tended to either putting the
> address info on a complete landuse polygon, or if a point,
> placing it on the driveway, just off the street to which
> it connects. I swear I read this somewhere as standard
> practice, and it makes sense from a navigation standpoint,
> particularly for rural parcels, where a "driveway" can be
> hundreds of meters long and not mapped.
>
> San Diego County, CA, USA has a bunch of address data from
> a SanGIS import.
>
> --
> Alan Mintz <alan_mintz+...@earthlink.net>
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org <mailto:Talk-us@openstreetmap.org>
> http://lists.openstreetmap.org/listinfo/talk-us
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org <mailto:Talk-us@openstreetmap.org>
> http://lists.openstreetmap.org/listinfo/talk-us
>
>
> --
>
> Alan Mintz <alan_mintz+...@earthlink.net>
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org <mailto:Talk-us@openstreetmap.org>
> http://lists.openstreetmap.org/listinfo/talk-us
>
>
>
>
> --
> Dale Puch
>
>
> _______________________________________________
> Talk-us mailing list
> Talk-us@openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openstreetmap.org/pipermail/talk-us/attachments/20110608/f74bde19/attachment.html>
------------------------------
_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
End of Talk-us Digest, Vol 43, Issue 14
***************************************
_______________________________________________
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
