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

Update map component #1

Open
jamiefolsom opened this issue Jan 11, 2017 · 0 comments
Open

Update map component #1

jamiefolsom opened this issue Jan 11, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@jamiefolsom
Copy link
Owner

Neatline currently uses the OpenLayers library, version 2.0 for map rendering. We will consider updating to the most recent version of that library, as well as switching to another library.

Beyond supporting existing Neatline features, any library to be used in the new map component must support a migration path for existing exhibits. Given that OpenLayers version 3 does not support Google maps, and many exhibits use Google maps base layers, we must find a way for those exhibits to continue to work.

In addition, the new version of the map component should make it possible to view, navigate, and search an exhibit using a small screen with a touch interface.

There exists a range of web mapping libraries, and systems and tools with which composite maps are built. We will consider the options available, in addition to OpenLayers version 3, including:

  • Leaflet.js (high-level, dedicated front end web mapping library)
  • Mapbox (full stack mapping platform)
  • CartoDB (full stack mapping platform)
  • D3 (low-level front end visualization library)
@jamiefolsom jamiefolsom self-assigned this Jan 11, 2017
@jamiefolsom jamiefolsom added this to the Sprint 3 milestone Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant