SiraApp Tool for editing/creating POIs

I am willing to give your tool a chance. You have reached out on the forum, created detailed documentation and are participating in this discussion. But please, do understand that by doing this, you are taking on the responsibility of ensuring that the data that is being added through your account is correct and of sufficient quality and that there is a line of communication between anyone leaving comments on your changesets and your clients.

Please make sure that your clients understand what OpenStreetMap is about. We are not just a place designed for companies to advertise their businesses. We’re an idealistic open source project with the goal of mapping the planet with an ever increasing amount of detail.

I still remain somewhat skeptical that the interests of your clients will align sufficiently with those of OpenStreetMap. There is nothing wrong with companies wanting to put their businesses on our map project, but you have to understand that as long as those businesses don’t know what OSM is about or only care about the narrow goal of increasing their visibility, there are likely going to be issues. There have been countless instances of this going wrong over the years.

7 Likes

@Roboost_OSM I saw your latest changeset. Changeset: 180993395 | OpenStreetMap

Please be aware of the following:

  • The phone number still isn’t formatted correctly
  • You’ve still got that contact:sms issue
  • Your usage of name:ar is not correct
  • You don’t list any sources in your changeset
  • You don’t refer back to your import page or import discussion in your changesets
  • Your profile should indicate that your account is used for an import/organised editing and it should refer to the correct documentation.
  • The changeset description is completely unwieldy. It just needs to be a good summary of what happened in that specific changeset.
  • Your usage of the contact:* keys is dubious and seems more like SEO optimisation to me. Do people really get in contact with that restaurant through for example youtube or tiktok?

I would also like to ask you to create a copy of your documentation on the OSM wiki in case your documentation at any point becomes unavailable to the rest of us

2 Likes

I would like to point out that in this changeset, you moved the location from inside the building outline to outside the building outline, right on top of a road. Changeset: 181003847 | OpenStreetMap

In this changeset you appear to be confused about how to perform a revert. Changeset: 181003965 | OpenStreetMap
While I appreciate the honestly, it does raise some issues with regards to how we can trust that you have to competence required to pull off this project. The import guidelines even raise this very point and explicitly states: ā€œIf you don’t know how to revert an import, don’t conduct the import in the first place.ā€

3 Likes

Hi! The new changeset comments may be a bit too descriptive :laughing:, this one reached the character limit rather easily: Changeset: 181038660 | OpenStreetMap

Consider formatting like so instead: Added [tag], [tag], and [tag] to [business name]

2 Likes

One other note I’ll add and have shared with other app owners who wanted to do a similar thing - I’d suggest that a single account posting the data into OSM may be a business risk to you, because if someone exploits your app in an unexpected way to put bad data into OSM, your account may be temporarily or permanently banned. You may want a series of accounts (or an account created per user, but clearly tied to your organization and documented on OSM) that you post changes under and tie each user to a single account - even if one account serves many users. That would limit the impact to the rest of your users if, for any reason, one of your users manages to create harm that causes suspension of your account, and it may help you trace comments back to the particular business owner more quickly.

@Taya_S

  • The first 3 comments have been adjusted
  • We will reference our documentation in the changeset comment and make it less detailed yet more descriptive
  • Could you please clarify what you mean by adjusting my profile
  • I am using the contact keys as I deem them necessary, these restaurants rely on Tiktok and Twitter nowadays for all communications for business operations like reservation. I would be open to omitting such changes if they are viewed against OSM spirit, I would love to hear your feedback on this point.
  • As for the OSM wiki Under which title and page should we include our documentation we want to make sure we keep this organized.

Thanks for the suggestion, we are in close contact with our clients and our trust on them is built on more than our relationship, our tool acts as intermediary blocking fraudulent before it’s posted onto OSM

There’s currently POIs with English addr:*=* tags being uploaded in Egypt. This could cause routing issues. Could please you look into it?

See node 13732176601

In your last changeset, you still mess up the phone number format. You can see here how others had to fix things for you. Node History: ‪أصل البرجر | Asl Alburger‬ (‪12736119574‬) | OpenStreetMap

Just explain in your OSM profile what you are doing, who you are working for, what your product/account/project is about. Include links to your documentation, etc.

The import catalogue. Though potentially the organised editing catalogue might fit better in this case. I’d love to hear community feedback on that one.

I would also like to know why you haven’t been responding to changeset comments, and why it took you over a week to respond here?

You also haven’t addressed my last message yet. In your documentation you also state that ā€œReversion will occur within 48 hours if necessaryā€, yet despite that you don’t appear to understand how to revert data and have not reverted data you explicitly mentioned was added by accident?

3 Likes

Dear Taya, where do you find this huge amount of patience you seem able to muster?

3 Likes

Hello Taya,

Our profile has been updated.
As for the reverts, we have come to the decision to not allow reverts from our tool and instead we have are going to manage them manually ourselves.

Upon testing we found that quickly checking mistakes ourselves, then editing will be more efficient than our self correcting tool.

We will still commit to the 48hr window promised.

Sorry for the late replies, I was on leave.