why did you remove boundary=administrative from Broward county.

as mentioned above, this commit adds an unsupported feature type to OSM mapped with existing tagging that has different meanings so it has too be reverted.

changeset/168722732

also it is important to note that names are not supposed to be used as a description of the feature, for more info see osm.wiki/Names#Names_are_not_for_descriptions

I am sorry but in OSM we do not currently support mapping service areas of a business, though If you wanted you could add the location of the business this service area applies and fill in what information you can about it. for more info see the OSM wiki amenity=social_facility .

for the spots were I was uncertain I left them without any construction tagging and will go back in the near future to determine which parts are under construction; so essentially work still needed.

As previously mentioned, the canal is one conceptual object and thus should have one area representing the area it takes up. It is also significantly easier when edits to one part of the canal do not generate a changeset comment the geographic size of the canal. When an area is attached to a relation of any sort it can be a pain to detach it and update it at a latter time so it is better to do it as a multipolygon from the get go. There is also the fact that when multiple land use areas share parts of polygons but are not mapped as multipoygons there is duplication in the data and that is something I try to avoid in Miami dade county, I also find it significantly easier to update and fix land use when it is mapped as multipolygons rather then simple polygons especially when mapping areas that cover relatively large amounts of space.

As for the grass along the highway it would anyways need to be done as a multipolygon as I am mapping the barriers and other such features along the highways in Miami Dade and as I go I add the land cover along the right of way of the highway and attach the land cover to the barriers added, and as to (as mentioned above) not duplicate geometry I do them as multipolygons; and as such since there is usually one continuous stretch of grass along both sides of a highway it only makes conceptual sense to merge the multipolygons together into one for each section of the highway.

For these reasons, and more, multipolygons are the best way to map land use and land cover in my opinion, and thus we should have /more/ of them, they should be the default in my opinions with the obvious exception of a single land use area not attached to anything else.

Happy mapping,
Udar

It is a multipolygon first and foremost because it is land cover and the best way to do land cover (and land use) is multipolygon, though second of all it is a multipolygon is because parts of it span large areas so editing one of the ways that make up its edge does not make the changeset geographic area unnecessarily large, and last but not least the multipolygon represents the whole of the area the canal takes up and since it is one canal it is one area and thus the best way to represent it, as one single object in the database.

Again adding non multipolygons attached to a multipolygon makes it significantly harder and time consuming to fix and update so I would greatly appreciate it if you would do them as multipolygon from the get go. Again this is land use and thus should be done as multipolygon.

I have asked you this before, when you add landuse attached to multipolygons, please do that landuse as multipolygons.

I have asked you this before, when you add landuse attached to multipolygons, please do that landuse as multipolygons.

I have asked you this before, when you add landuse attached to multipolygons, please do that landuse as multipolygons.

it is one multipolygon as it is the grass along the right of way of Don Shula expressway from Southwest 56th street to Southwest 87th avenue

in June I mapped the grass and shrubbery along Don Shula (in this area) and part of that was relation relation/19302801 , in this commit you attached you residential land use that was mapped as an area to that relation which in most cases makes it significantly harder to work with since area attached to relations are harder to work with.
All I am asking is next time (when doing this in Miami) check if what you are mapping is attached to existing multipolygons mapped by others and if so do your work in multipolygon as a courtesy to the local mappers in Miami doing there best to make the map in our area the best it can be. After all multipolygons are the best way to do land use as they are significantly easier to maintain and fix when the land use changes, plus they reduce the amount of duplication in the data.

next time you add land use attached to already mapped land use that is done as multipolygons please do your land use as multipolygon.

why did you remove the wikidata and Wikipedia links as they seem to be correct.

next time please leave a better change set comment describing what you did in the change set, for more info see osm.wiki/Good_changeset_comments .

also I was wondering why you added ways without tags as ways without tags are not very useful as they do not tell you much of anything about the object

Happy mapping,
Udar

are you sure that little italia is no longer in business.

what was the source for the road names.

so then what floor is "The Gallery At Bay Harbor" on or is that the name of the building part with each of these floors

question about node node/6027891152 , does that mean that the office takes up the whole fifth floor, or am I misunderstanding that.

Based on the description of way/769421858 does that mean that it does not have any name at all or does it have some other name?

Happy mapping,
Udar.