Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Endpoints to implement #4

Open
11 of 15 tasks
gmaclennan opened this issue Jan 14, 2016 · 4 comments
Open
11 of 15 tasks

Endpoints to implement #4

gmaclennan opened this issue Jan 14, 2016 · 4 comments

Comments

@gmaclennan
Copy link
Member

gmaclennan commented Jan 14, 2016

iD Editor relies on the following OSM API v0.6 endpoints:

The following are defined in iD/connection.js but I am unclear how they are actually used, perhaps conflict resolution?

  • GET /api/0.6/[node|way|relation]/#id
  • GET /api/0.6/[way|relation]/#id/full
  • GET /api/0.6/[node|way|relation]/#id/#version
  • GET /api/0.6/[node|way|relation]/#id
  • GET /api/0.6/[node|way|relation]/#id/history
  • GET /api/0.6/changesets?user=[user_id]
@gmaclennan gmaclennan mentioned this issue Jan 14, 2016
@ghost
Copy link

ghost commented Feb 14, 2016

  • PUT /api/0.6/changeset/create
  • POST /api/0.6/changeset/#id/upload
  • PUT /api/0.6/changeset/#id/close
  • GET /api/0.6/[node|way|relation]/#id

@ghost
Copy link

ghost commented Feb 14, 2016

  • GET /api/0.6/[node|way|relation]/#id/#version

@ghost
Copy link

ghost commented Feb 19, 2016

  • GET /api/0.6/[node|way|relation]/#id/history

@gmaclennan
Copy link
Member Author

Noticed that iD also uses /api/0.6/changesets. Not entirely sure how it is using that data or whether it is important to implement. No point whilst we have no user ids.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant