This branch is located much farther south in Richmond, not inside the YVR terminal. I've moved it.

Most of these were in the wrong spot, duplicated an existing object, or simply don't exist. I've fixed them all, but please be more careful before you do an import like this.

I drove up here and checked today, and these roads are definitely still under construction. I don't know what source you used that indicated these roads were complete, but that source is apparently not reliable. I've reverted this changeset.

I went over and checked today, and this road is still under construction, so I've reverted this changeset. Whatever source you used is not reliable.

This changeset created a number of objects that duplicate existing objects, especially on Vancouver Island. Can you please remove the duplicates and use the existing objects in the new relations?

What is your source that indicates these roads are now open? The last time I checked, they were still closed.

This road was still under construction when I drove past it a couple of weeks ago. Do you have someone in this area that reports it is now open?

There isn't anything along this stretch of highway, let alone any motels, so I'm assuming this was a mistake and I'll revert these.

This is another problematic changeset. It creates objects that are supposed to all be in Canada, but some are in the US and one is in Africa. Also, a number of these duplicate existing objects, some are in the wrong location, and some are on the exact same location as other existing objects. Please revert this changeset and correct all of these issues before uploading this data again or any future data.

I just noticed that there are a number of these that are scattered across the planet, including about a dozen in the US. This makes no sense for branches of a Canadian bank. This should probably be reverted

Is this an import? The names seem dubious and the address fields are broken. A spot-check of a few seems to indicate that these are CIBC branches, but that isn't indicated either in the name of the objects or using the "brand" or "operator" tags.

Agreed. "boundary_type" doesn't even seem to be a documented key, let alone that with a value of "border_type".

Are you sure the garden is only that smaller area and not the area surrounding it that had previously been mapped? The larger area seems a lot like a garden to me.

Why are you mixing names in the name tag? "Juniper Trail" is now the official name of this trail, and "FM Radio" has already been tagged as an alternate name. Likewise with some other trails that have been formalized in the Quimper area.

This changeset extended Tulista Park too far west and south than it's actual boundaries, so I've reverted it to it's actual boundary

This edit created a duplicate of Gorge Park, so I've removed the one created in this changeset

Hi Paul,
When I've been there in the past (several times geocaching), there haven't been any signs (either literal or figurative) indicating that it was private property, so that aspect honestly never crossed my mind. However, now that I look into it more, I can't find any evidence that the area is public and it more than likely is private land. I see a user has already edited the ways in that area to add access=private, which is probably appropriate.
Andrew

This changeset also contains some damaging edits that removed detailed mapping of turning loops and needs to be reverted

As I said, I visited the location in person, and have confirmed that the majority of these roads are not under construction yet. Further, I've yet to see any evidence that the proposed layout has been drastically changed as per the changes you had made. What you can see in the Bing imagery is simply some equipment shaping the ground in the area. The location of a piece of equipment does not mean that's where the road will be. Further, you still had mapped Turnstyle Crescent extending farther than is currently open. These are all examples of why you can't map a situation like this remotely from aerial imagery. You should leave mapping like this to the local mappers, who can visit in person and map the reality. As a result of the numerous incorrect changes you made, I've reverted your changes and then updated the small portions that have actually changed. Please do not make any more changes in that area, because you simply don't have access to enough information to adequately map the changing area. In the future, please do not guess about the situation in an area. If you don't know for sure, it's better to not make any changes.

Please also communicate this to your fellow Telenav employees. I've seen others making the same damaging mistake and had to revert those changes.