[Talk-us-maine] Fwd: Local consensus

Alan & Ruth Bragg alan.ruth.bragg at gmail.com
Sat May 16 15:28:02 UTC 2020


Hi Alex,
I think you've done a great job with your imports. Must be an order of
magnitude improvement in OSM. Maine was embarrassingly behind Google Maps.
------------------------------------------
My opinion: Option C and semicolon


Removing tiger tags makes sense to me. I often select them by searching for
something like
 user:"Alan Bragg" and "tiger:cfc"=* and then removing the tiger tags.

They are still available in the "history" Ctrl-H
Editing a tiger road often involves moving it several hundred meters and
changing the name. Often, I draw a new road, select the old and new roads
and use Ctrl-Shift-G just to retain the history. Sometimes I just delete
the road if it makes no sense.

Above, I'm referring to roads that have not been edited since the original
tiger import.
We used semicolon (;) in MA, it's explicit. hyphen (-) implies a range.

I've found many roads where the E911 road name differs from the addr:street
name. I usually change one of the names to the most grammatically correct
in case of punctuation or capitalization.
Ground truth is hard to find from your armchair.  Private roads usually
don't have street name signs.

Other issues that interest me are
possibility of a building import.
address nodes that are not seen in the latest imagery.
addresses that are far from the buildings or along the roadside.
how to report to the state after discovering E911 road geometry that
doesn't significantly match imagery.
I like to realign roads that don't match imagery and reduce the density of
nodes. Especially when there are two nodes either side of and intersection.
I like the "simplify way" (shift Y) and "improve way accuracy mode" (W) in
JOSM

I'm curious about the "Fire Roads" in Maine. Usually impossible to see in
imagery and often not visible in street views.

The  "MapWithAI" plug-in is active in my JOSM. I'm not using it but it does
add a lot of clues to potential errors in the validation window.
I find the "coloured streets" Map Paint Style very helpful.
The OSMOSE QA tool set to severity=All, and topic=addr with a check mark on
"street numbers" is also a big help.
I haven't checked the osm inspector in a while to see if it's been
refreshing data frequently.

Alan


On Sat, May 16, 2020 at 8:55 AM Alex Hennings <blackboxlogic at gmail.com>
wrote:

> Team Maine,
>
> I'd like to start a record of local consensus on a few issues in Maine and
> I think this mailing list might be an accessible place to start the
> conversation. Some of these issues have been discussed in private, I'd like
> to make them non-private. Maine's OSM Wiki
> <https://wiki.openstreetmap.org/wiki/Maine> would be good place to keep
> the results. I've BCC'd a few people who may want to join the mailing list.
> Please invite others.
>
> Some topics I'd like to start with:
>
> Extra Tags add noise and clutter
>
>    - Tiger:*=
>    - Source=
>    - GNIS:*=
>    - ele=
>    - Others?
>
> Options:
>
>    - A) Preserve them because they are historic, useful, and not in the
>    way
>    - B) A mechanical edit to remove them all
>    - C) When modifying an element for other reasons, remove these also
>    - D) Some other option?
>
> Discussion:
> I propose option C. I have found some of these tags useful. I would
> propose keeping gnis:feature_id= and tiger:reviewed=no (until the element
> has been reviewed). Are there other tags people would like to retain?
>
>
> Address Format
> When an element has multiple numbers, I propose *not using* - (hyphen) in
> addr:housenumber. Instead, prefer a semicolon separated list, or separate
> elements.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us-maine/attachments/20200516/05124dd8/attachment.htm>


More information about the Talk-us-maine mailing list