Re: [Talk-us] MassGIS Road Import - Lanes

[Greg Troxel]

Bill Ricker  writes:

> On Fri, Sep 23, 2016 at 2:27 PM, Spencer Gardner
>  wrote:
>> Is anyone on here familiar with the process that was used to upload MassGIS
>> road data for the state of Massachusetts? I'm noticing a lot of incorrect
>> lane information on one-way residential streets and wondering if the bulk
>> import process could be the cause. I'd love to hear if anyone else has come
>> across this.
>
> Not intimately knowledgeable here, but aware. I recall there was
> widespread problem with one-way streets because the import was
> inconsistent in one-way polarity. Those are i hope mostly fixed by
> now. I don't recall discussion of lanes, though.

A nit: asq I understand it, the road data is maintained by MassDOT
(formerly > EOT, Executive Office of Transportation), and made available
by MassGIS:
  
http://www.mass.gov/anf/research-and-tech/it-serv-and-support/application-serv/office-of-geographic-information-massgis/datalayers/eotroads.html

The one-way issue was due to a belief at the time that the EOT/MassGIS
dataset had information about whether a road was oneway but not the
direction, because the direction was somehow proprietary data from some
external provider.  As a result the one-way roads had a FIXME and have
largely been corrected.

> My own street is similar, one-way and we have 1 travel lane plus both
> side parking in reality and it's coded as lanes = 2.

I am unclear on lanes.  It would help to analyze a significant number
(10-25?) of roads, comparing what's in OSM to reality and also what's in
the latest state data.  There could be differences in definition of
what's a travel lane vs parking between OSM and MassDOT.
  https://wiki.openstreetmap.org/wiki/Key:lanes

Definitely at the time, and arguably still, the EOT/MassGIS road data
was vastly better than TIGER.  The geometry is excellent, and road
naming is very accurate -- I've only found one or two errors.

If there is some pervasive issue with lanes, a mechanical edit could
make sense.  But I would like to tread carefully there.

I've added talk-us-massachusetts which is probably more appropriate for
the details.


signature.asc
Description: PGP signature
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] MassGIS Road Import - Lanes

[Greg Morgan]

On Sat, Sep 24, 2016 at 2:30 AM, Greg Morgan  wrote:

> I don't live there but Mapillary user marc has nice coverage for some of
> the roads in question[1].  I am _guessing_ that a formula was developed
> based on the width value that Massgis had in their data. Looking at
> Mapillary while in JOSM, it almost looks like there is a one off error or a
> condition in one area of Massachusetts did not apply to another area of
> Massachusetts.  Again these are just guesses!  If you look at Massachusetts
> Avenue via JOSM/Mapillary, the street looks like lanes = 2 except for a
> turning lane here and there.
>
>
Oh! Oh!  I forgot to add, thank you for the mappers that imported Massgis.
  I'd rather have a usable map with street names and actual streets than a
map of perfect emptiness.  We has a wonderful useful map verses areas full
of "here be dragons".[2]



> Massachusetts Avenue
> width = 18.9; lanes = 3
> https://www.openstreetmap.org/way/8615119
>
> Hancock Street
> width = 12.2; lanes = 2
> https://www.openstreetmap.org/way/8615674
>
> width = 7.6; lanes = 1
> https://www.openstreetmap.org/way/8614912
>
> [1] https://www.mapillary.com/app/user/marc?lat=42.
> 382047952522356=-71.18021987120689=12.90517848549394=map=
> L9nOys_VqYuhOjcZ0Z9I9A
>
> [2]
https://en.wikipedia.org/wiki/Here_be_dragons




> On Fri, Sep 23, 2016 at 11:27 AM, Spencer Gardner <
> spencergard...@gmail.com> wrote:
>
>> Is anyone on here familiar with the process that was used to upload
>> MassGIS road data for the state of Massachusetts? I'm noticing a lot of
>> incorrect lane information on one-way residential streets and wondering if
>> the bulk import process could be the cause. I'd love to hear if anyone else
>> has come across this.
>>
>> For reference, see http://www.openstreetmap.org/way/8615602
>>
>> I haven't scoured the rest of the state, but Cambridge is riddled with
>> one-way residential streets that all have lanes=2 when there's clearly only
>> a single travel lane.
>>
>> Thanks
>>
>> ___
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>>
>>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] MassGIS Road Import - Lanes

[Greg Morgan]

I don't live there but Mapillary user marc has nice coverage for some of
the roads in question[1].  I am _guessing_ that a formula was developed
based on the width value that Massgis had in their data. Looking at
Mapillary while in JOSM, it almost looks like there is a one off error or a
condition in one area of Massachusetts did not apply to another area of
Massachusetts.  Again these are just guesses!  If you look at Massachusetts
Avenue via JOSM/Mapillary, the street looks like lanes = 2 except for a
turning lane here and there.

Massachusetts Avenue
width = 18.9; lanes = 3
https://www.openstreetmap.org/way/8615119

Hancock Street
width = 12.2; lanes = 2
https://www.openstreetmap.org/way/8615674

width = 7.6; lanes = 1
https://www.openstreetmap.org/way/8614912


[1]
https://www.mapillary.com/app/user/marc?lat=42.382047952522356=-71.18021987120689=12.90517848549394=map=L9nOys_VqYuhOjcZ0Z9I9A

On Fri, Sep 23, 2016 at 11:27 AM, Spencer Gardner 
wrote:

> Is anyone on here familiar with the process that was used to upload
> MassGIS road data for the state of Massachusetts? I'm noticing a lot of
> incorrect lane information on one-way residential streets and wondering if
> the bulk import process could be the cause. I'd love to hear if anyone else
> has come across this.
>
> For reference, see http://www.openstreetmap.org/way/8615602
>
> I haven't scoured the rest of the state, but Cambridge is riddled with
> one-way residential streets that all have lanes=2 when there's clearly only
> a single travel lane.
>
> Thanks
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] MassGIS Road Import - Lanes

[Bill Ricker]

On Fri, Sep 23, 2016 at 2:27 PM, Spencer Gardner
 wrote:
> Is anyone on here familiar with the process that was used to upload MassGIS
> road data for the state of Massachusetts? I'm noticing a lot of incorrect
> lane information on one-way residential streets and wondering if the bulk
> import process could be the cause. I'd love to hear if anyone else has come
> across this.


Not intimately knowledgeable here, but aware. I recall there was
widespread problem with one-way streets because the import was
inconsistent in one-way polarity. Those are i hope mostly fixed by
now. I don't recall discussion of lanes, though.

My own street is similar, one-way and we have 1 travel lane plus both
side parking in reality and it's coded as lanes = 2.

IDK how or why.

As to the Bulk import , at the time, MASSGIS had better data than
TIGER so that was the basis in MASS. I'm cc'ing a couple folk who
might remember if lanes was odd in MASS GIS.
But if we're lucky someone from MASSGIS will speak up.

-- 
Bill Ricker
bill.n1...@gmail.com
https://www.linkedin.com/in/n1vux

___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us