[Talk-us-massachusetts] Address Review: Wellfleet & import concerns

[Greg Troxel]

"Alan & Ruth Bragg" <alan.ruth.bragg at gmail.com> writes:

> It would have helped immensely to have a MassDOT street imagery layer
> similar to our "MassGIS L3 Parcels" overlay. Street geometry is often
> difficult to trace in the woods.

I don't know how much work it is, but I would also love to see:

  updated L3 parcels layer

  roads layer as you suggest

> I downloaded the MassDot Street
> https://docs.digital.mass.gov/dataset/massgis-data-massachusetts-department-transportation-massdot-roads
> shp
> file but it was too big to open in JOSM.

I wonder if you can get per-town shapefiles.

> I don't see a problem importing single addresses (not stacked) and match
> street name & buildings' centroid  and do not have a STATUS_CODE of
> "inactive", "not found" or "review".

Turning that into a statement I find easier to understand (sorry, this
is confusing stuff!), do you mean:

  If an address point has the status code ACTIVE or LINKED, and

  the address point is a good match for the centroid of a building
  already in OSM, and

  the street name in the address point is a match (ignoring case only)
  of one of the nearest roads in OSM

  THEN

  that point can be imported, with the address tags attached to the
  building way above

?  That's my current best guess at what "good enough match to import"
means, or at least the first case.

> A maproultte process, allowing me to see an entire street and the addresses
> to be imported would be fine with me. Am I correct that the address "node"
> values will be transferred to the building "way" automatically?

I don't see why this would involve maproulette.  If we have code that
does the above checks and makes a changeset file to add address tags,
and we review it enough to believe that it's right, we can just upload
it (after doc, coding, import review of course).

> Adding new building outlines is going to be needed to complete the address
> import. Does anyone know where to download massgis buildings shape file by
> town?

I think we should be (well, you can of course do what you wnat!)
focusing on getting a substantial part of the address data in shape for
import, and not be concerned that there are a lot of points that will be
skipped on this pass because of missing buildings.  This import is the
hardest that's been done to date in Mass, and I am a firm believer of
decomposing into manageable steps so that some steps can be taken, and
in particular avoiding dependencies that aren't really necessary.

Longer term (after this phase, so could be pretty soon), I think we need
to be revisiting the buildings layer to see about new buildings that
were not there last time (and the roads layer, even if just to make a
discrepancy file, plus addressing the unreviewed oneways).

The buildings layer is a bit tricky, because while 99.9% (or more) of
the buildings impprted are right, there were some phantom buildings (or
buildings that were there at lidar time and are no longer) that have
been deleted by hand.  So we have to not re-add those.  But, the
buildings import is currently the best-done import in MA by a wide
margin - aside from a few buildings to be deleted, there have been no
issues from it and no complaints.

So i don't mean to object to looking at buildings.  I'm just trying to
say that "we can't do addresses until buildings are perfect" seems like
a path to not doing addresses.  The nature of the code will be that we
can run it and get addresses to add, and then in a few months do it
again, and all those will have status "in osm and matches" and hence be
ignored, and then any new addresses, or addresses that newly have
buildings, will be in the "to be imported" file.   So it may make sense
to do

  import addresses when street names match and they match a building

  in parallel
     work on streets
     think about a 2nd phase of buildings

  redo address import to pick up newly allowable addresses every 3
  months or so


I'm getting a little more comfortable with postgis, so should be able to
help with scripts.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 162 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/talk-us-massachusetts/attachments/20180817/00c92bd5/attachment.sig>