Gee, what a lot of good chatter here on this list! However, neither this list
(nor this requestor) have heard a peep about changing a couple dozen Amtrak
route network=* tags so all have value Amtrak. Too easy? I might simply ask
forgiveness rather than permission or for feedback, though
>There is a talk-us-massachusetts@ and I think review of your proposed
>mechanical edit should include that list.
Okay. This is pretty preliminary still, I just decided that feedback
was a good idea. Does that list overlap enough with this one that you
forwarding the message would be sufficient?
There is a talk-us-massachusetts@ and I think review of your proposed
mechanical edit should include that list.
I suspect people would be amenable, but it would be good to publish the
code, and the proposed files to upload, so that they can be reviewed.
(I'm not clear on the rules for mechanical
There is some question about the overall accuracy of the height data in
this import, but I think the units are correct in meters. For example,
the Landmark Building [1] is a known height of 305 feet / 92 meters. [2]
Mapillary view (from a distance) [3] .
Microsoft measured it at 101
Hello Mike,
I think that you have made the same mistake as they made with the
Tampa/Clearwater, FL Microsoft building data import: The height is given in
feet and inches, but you used metre scheme (x.y) instead of x'y". An
example:
This commercial building
In accordance with Step 6 / item 4 of the imports checklist, the import
and QA is now completed.
Thanks to Microsoft for making building and height data available and
multiplying the efforts of a few local mappers!
On 3/14/2018 10:21 PM, Mike N wrote:
FYI, this is proceeding with 2
Many POIs in Massachusetts have reasonable address information stored
as a single value in the address tag (mostly from imports before the
'addr:*' scheme was established). Something like 1/2 of the uses of
'address' in OSM are in MA. I'd like to do a mechanical edit that
parses the individual
7 matches
Mail list logo
