[Talk-us-massachusetts] Hello, and some tagging questions!

[Aria Stewart]

Hey! I’m Aria, working on mapping a bunch in Salem.

I’ve got questions about the best way to approach some situations:

Parks: Salem has three notably different styles of map objects for parks. 
- Lappin Park (https://www.openstreetmap.org/edit#map=20/42.52141/-70.89585) has an outer park area, and inner grass and footpath objects. Lafayette Park (https://www.openstreetmap.org/edit#map=20/42.51753/-70.89327) is similar, though the ‘park’ area goes right up to the centerline of the street. I’m never sure how precise to be vs how space filling.
- Forest River Park (https://www.openstreetmap.org/edit#map=17/42.50658/-70.88447) is a mess of objects that don’t seem to quite line up with my GPS, and seem too distinct — should the green spaces be separate from the park? Or should the parking be on TOP of the park? how about the wetlands? It all overlaps, it’s all part of the park (except maybe Pioneer Village, which is at least fenced off separately, though it’s accessed through the park)
- Palmer cove park (https://www.openstreetmap.org/edit#map=17/42.51452/-70.88898) has some of the same amenities as Forest River Park, but they’re unmarked — is that valuable to go trace out? How should they be layered and tagged?

Textured surface for crossings: is that the textured corners? Or the whole crossing that’s textured? We’ve got a few textured and raised crossings in town, but mostly textured corners and painted markings, and some untextured corners and unmarked crossings. What’s the best practice here?

The MassGIS aerial imagery and the Bing maps imagery are offset from the buildings on the map in town pretty pervasively. What do you trust? how do you deal with sidewalks that cross buildings? Is there a strategy that doesn’t involve moving things?

Thank you for your expertise,

Aria
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us-massachusetts/attachments/20230308/434e9b79/attachment.htm>