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

Generalize iD #6483

Open
quincylvania opened this issue Jun 4, 2019 · 6 comments

Comments

Projects
None yet
5 participants
@quincylvania
Copy link
Collaborator

commented Jun 4, 2019

Currently, iD is designed for mapping OpenStreetMap data exclusively. This severely limits the downstream use cases of the project.

We should make iD a general-purpose GeoJSON editor with an extensive plugin interface. Developers could then customize every part of iD without even needing to fork it. The OpenStreetMap plugin would be the flagship plugin and could live in a separate repo. That way, things like presets and tag deprecations could be hashed out separately from the iD core.

From the perspective of a user editing on osm.org, this change would make no difference.

Some of the components that require generalizing:

  • User authentication
  • Data sources
  • Geometry primitives
  • Presets
  • Map styling
  • Validation rules

@quincylvania quincylvania added this to the 3.0.0 milestone Jun 4, 2019

@bhousel

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

The OpenStreetMap plugin would be the flagship plugin and could live in a separate repo.

Actually I'd prefer for everything substantial to move out of this repo into a new one, and this repo under the openstreetmap organization could just be where the plugin lives.

@manfredbrandl

This comment has been minimized.

Copy link
Contributor

commented Jun 19, 2019

How would translations in Transifex become organized with this change?

@quincylvania

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 19, 2019

@manfredbrandl Most likely the core iD strings and the OpenStreetMap-specific strings would be separated out. The iD strings would remain on transifex while the OSM strings could become a separate transifex project or use another translation platform like the wikibase.

@matkoniecz

This comment has been minimized.

Copy link
Contributor

commented Jun 20, 2019

Would this generic editor use name of OSM editor or is there a plan to create a new name?

@BjornRasmussen

This comment has been minimized.

Copy link
Contributor

commented Jun 20, 2019

It would just be "iD", right?

@quincylvania

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 20, 2019

Would this generic editor use name of OSM editor or is there a plan to create a new name?

@matkoniecz I haven't thought much about the names. I think the core would be "iD" and then plugin could be "iD for OpenStreetMap" or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.