Thanks for all your responses. Please find my inline responses below:

why don’t you fit your drivers with cameras, and upload the images to an open platform like Mapillary?

While we agree that this might be easier, we currently don’t have any immediate projects along these lines.

As per the OEG, can you link to the wiki page (under OE/Activities) for this project?

I have updated the wiki page as per OEG. Thanks for your inputs. Once the editing process gets started, I will add blurb to Amazon wiki page as well clarifying the licensing norms.

How do we know that the source that you are using is licence-compatible with OSM? Can you publish that licence, so that it is clear to the community that you do have the right to use that data and there are no potential future problems?

@Amazon we made sure the data source is license-compatible with OSM. We did get into an agreement with Cyclomedia stating the same. Since, the agreement also discusses about pricing and Amazon Private information, it cannot be disclosed publicly. But if OSM board or DWG wants to review it privately to ensure license is in place, we can work with Cyclomedia and our internal teams to provide the same.

In the event that such a dispute is escalated to the Data Working Group, we’d have to favour the publicly available imagery over private imagery that no-one else has access to.

With due respect towards community contributions, totally agree to your inputs over here Andy. For any escalation or a doubt raised by community member, we will respect the community members inputs and revert our edit immediately. Also, to emphasis our process, we will be adding data only if 2019 or recent imagery is available which is estimated to be only in 14% cases. For the rest of 86% cases, our team will be dropping notes for local community members to cross verify and add it to OSM. Also, 100% of the edits made by our team will be cross checked again by our quality check team to avoid errors from our end.

@jguthula: Any intent to expand this beyond Germany? I can see a lot of value in recent street imagery (even if private to Amazon) in other places such as my home country (United Kingdom).

Thanks for your inputs Rob. If our inputs turn out to be fruitful for improving data in Germany, we would love to scale this process to other geographies as well.

Starting tomorrow, we will start using the Cyclomedia imagery to check underlying data quality issues. We will of course incorporate all valuable inputs that you have provided us when doing this activity

Regards, Jothirnadh

Please find my responses below:

For example, it may be possible for pedestrians to walk around a gate. Unless sidewalks have been mapped separately, it may be necessary to add foot=yes in that case.

In case we get the information on non-resident pedestrians to walk around, we can add “foot=yes”. @Minh Nguyen Please confirm if there are any challenges using this tag.

How do you plan to tag a gate at the front of a gated residential community (common in Florida) that allows both residents and delivery vehicles to enter but not the general public?

Only allowed for delivery vehicles and local residents, we can be adding “access=delivery; private” (suggesting as per @Magick93 inputs) restricting route to public transport.

Is access=no/private/permissive/yes sufficient to cover your needs?

Not in all scenarios. In certain cases we are coming across situations where only delivery agents were allowed to travel through. In such situations we can add “access=delivery; private”. Let me know if this is not possible.

Please think about trying to group tasks into reasonable chunks to ease review for community members. It’s a lot easier to look at a geographically compact changeset with a few dozen changes and understand what it is about than it is to review and understand 3 dozen separate changesets.

Thanks for your inputs, ideally we are planning to fix one community in one changeset. But again, if the changeset is taking too much time or too many gates to cover, we will be splitting in to multiple changesets to avoid conflicts.

access=discouraged is very rare, and risks being a subjective tag, which is a big no-no. I suggest you don’t use that until you can address that concert.

Yes, we are expecting the same as well. We didn’t come across any scenarios so far on this, but if we come across explicit sign boards stating the same, then we will be adding “access=discouraged”.

Please follow the Organised Editing Guidelines and write a wiki page about this specific task

Sure will do that once the task is finalised. Will also update the Amazon OSM wiki.

Proposition 1: The multiple-value approach. Use a semicolon character “;” to separate different values. Example: The tag access=private;delivery will effectively keep the general public away but allow delivery vehicles. It’s simple to use and understand, and getting more support over time in software and parties involved.

Thanks for your suggestion @Magick93, following this approach can answer few questions raised earlier. Waiting for more community feedback on this.

I suggest you talk to the StreetComplete team, to see if it should support a “quest” to add access tags to gates, with the possibility of Amazon submitting a patch. SC’s ‘on the ground’ survey support helps OSM, and hence you routing. It’s a form of direct, capacity building support Amazon can do, rather than just another organised editing team.

Thanks for the inputs, will explore this option as well.

Regards, Jothirnadh

Thanks for all the responses. I can totally understand how the road classification can vary from country to country. I have also posted the same content in UK forum (https://forum.openstreetmap.org/viewtopic.php?id=66878), German forum (https://forum.openstreetmap.org/viewtopic.php?pid=756650#p756650) and talk GB mailing list as well. I will wait until this weekend to get more responses from the community members and also to cover as many edge cases as possible. Later this week I will compile all the information from different forums and come up with a list of possible solutions.

Regards, Jothirnadh

Thanks for your comments Nmxosm, happy to know that our actions were really helpful. Please do let us know if there is anything that we can do to improve our editing process.