Hey freebeer,
Looks like our import=yes tag got partially deleted on this one. I corrected it.

Do you have your overpass queries shared somewhere? They seem valuable for our own QA processes.

Thanks,
Jeff

Hey, freebeer,

Looks the mapper before us made the tagging mistake but I'm happy to fix it.

Thanks for the feedback,
Jeff

Hi freebeer,

I suspect this way was split from the bridge segment next to it. W is used for wireframe mode in iD so chances are that bridge was selected, then the user hit W and overwrote it.

Thanks for heads up on bad tag, we appreciate the feedback.

-Jeff

No problem. Fixed that as well. I suspect the issue was the users typing out a tag then trying to use the hotkey to hide map data, which in our version of iD was N.

Thanks again for the heads up,
Jeff

Hey Pascal,

This is just a temporary artifact of some awkward gridding on a tasking manager project. The rest will get filled in as the adjacent tasks get done.

-Jeff

Ah, I can talk to them and let them know that it's ok for community members to remove it when they do further editing.

We run through our projects after completing all of the tasks and do cleanup on the whole area so keeping import=yes on a road will help us identify our work during that process, which is why they asked you to keep it for now. However, if you are happy with the road as is, feel free to remove the tag.

-Jeff

Hey freebeer,

Adrian isn't active anymore but was part of my team. I'm not sure what the typo was supposed to be here but I corrected the mistake.

Thanks for letting us know about it!
-Jeff

Still not the right way in the link :)

But perhaps you meant this one way/700956583/history ?

If that is the case, it was a version 1 because the RapiD based way was split during this clean up changeset to add a bridge.

Our initial changesets will have RapiD as the created_by tag. You can view an example of one here changeset/73360105 .

After the data is uploaded in RapiD we clean up the area with JOSM as it works better for large scale cleanup and validation. Generally, this cleanup involves some splitting and merging so you might some version 1 features, but largely the work should be done in the RapiD changeset. So you will see changesets using both RapiD and JOSM spread throughout.

I agree that import=yes is a slight misnomer though. When we began this work a few years ago in Thailand, the concept of AI assisted mapping wasn't really well understood yet so we used the term import as it was the closest analog. However, we consider it a fairly temporary tag that can be removed as people further enhance the data over time. It was just important that we properly marked our data for people to see exactly what was ours.

Thanks again for the feedback!
-Jeff

Hey Joseph,

The way you linked seems to be incorrect so I'm not sure which road you are referring to.

All of our mapping efforts in Indonesia are using RapiD data though. Of course there is human validating as well as hand drawing plenty of missed areas. After the initial mapping we come through using JOSM to run more validation checks and blend together our task squares which is what this changeset is.

If you would like to try RapiD yourself, you can go to mapwith.ai and choose one of the start mapping options.

Hope you check it out :)
-Jeff

Hi Joseph E,

I lead the editing team at Facebook. As freebeer mentioned this is part of our AI assisted mapping of Indonesia so we have been using the import=yes tag to let the community identify our roads.

We always appreciate local feedback on mapping schemas as they tend to be a little different all over. We have been tagging plantations as service roads based on the Indonesia tagging wiki as well as guidance from our partner, HOT Jakarta. I see that user Jeisenbe has just altered the wiki on August 10th and removed plantations from the service road list but before that, it was listed as the appropriate tag for these areas so it seems like there is some disagreement amongst the community. However, if the consensus is to use track instead then we will of course use that going forward.

Thanks for feedback,
Jeff

Hi theworldmapper,

Thanks for your contribution to OSM! It looks like you accidentally duplicated a lot of roads in this area. Can you take a look and clean up any duplicated data?

Thank you!
Jeff

That's a great question!

We are using AI predicted roads as our starting point for this data, but our mappers validate and further edit all of it to ensure quality. So this data is not really a traditional import but rather an accelerated mapping tool.

Since the generated roads require editing, we grid it up using a tasking manager and only generate (and manually draw) roads to the task borders to avoid duplicates.

After a project is completed, we do cleanup work to remove traces of the individual tasks, including merging ways at the border and resolving any conflicting road tagging. Which is what you were seeing with this changeset.

Hope that helps to clear up the workflow.

-Jeff

Hi pitscheplatsch,

This is cleanup work from one of our tasking manager projects. The deletions are from merging together adjacent ways.

-Jeff

Sorry about that, it was an unintentional upload of a project grid. Thanks for fixing it!

Hi Russ,

Yes, we are still actively working in Thailand.

-Jeff

Hi Russ,

Thanks for fixing this. It's an easy mistake to make and can be hard to catch. Its hard to tell from the imagery but it seems like there is a connection at the node below between the two roads. Perhaps a pedestrian connection would be appropriate since its narrow?

node/6160380849

Thanks,
Jeff

Hi mueschel,

Sorry about that. The user was doing some cleanup work on our projects using the grid as a reference and accidentally uploaded it. Thanks for cleaning it up.

-Jeff

Yeah its here https://tasks.hotosm.org/project/5170?task=2977#bottom

I've sent them a message explaining the issue and the associated HOT task was invalidated with an explanation so if they do further crisis mapping they will also get a message on the tasking manager.

Hi Tom,

Good catch, I fixed the alignment of that tertiary.

Thanks,
Jeff