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

Support custom source types #3326

Closed
7 tasks
lucaswoj opened this issue Oct 7, 2016 · 4 comments
Closed
7 tasks

Support custom source types #3326

lucaswoj opened this issue Oct 7, 2016 · 4 comments

Comments

@lucaswoj
Copy link
Contributor

lucaswoj commented Oct 7, 2016

This is an umbrella issue meant to track the various moving pieces of getting our custom source API ready for primetime. I created a project for this but am having trouble adding issues to it.

@lucaswoj
Copy link
Contributor Author

@remster
Copy link
Contributor

remster commented Jan 9, 2017

Hey Lucas. I just forked mapbox-gl-js to achieve something similar. I need to override some of the VectorTileWorkerSource's behaviour...
The reference to which is hardcoded here as i type this and will hopefully remain in vicinity when you hopefully read this.

I understand that ultimately the ambition is for this mapping:
this.workerSourceTypes = { vector: VectorTileWorkerSource, geojson: GeoJSONWorkerSource };
to be supplied (in one gulp or increments) by the client (whoever constructed the mapboxgl.Map(...)) <- possibly in its c'tor params.

I am asking because as much as i can survive on my fork until your work is complete, i'd hate making wrong assumptions about where this goes. I've been trying to deduct it from your work's outline, say #3034, perhaps didn't read carefully enough, but couldn't really reassure myself.

BTW: is it in active development at present?
Perhaps there is something i could help with.

@lucaswoj
Copy link
Contributor Author

lucaswoj commented Jan 9, 2017

Thanks for asking @remster. You can see the outstanding tasks for this refactor in in https://github.com/mapbox/mapbox-gl-js/projects/2. If you're serious about tackling any of those issues, let me know and I'll be sure to connect you with whatever help/resources you need.

@lucaswoj
Copy link
Contributor Author

lucaswoj commented Jan 9, 2017

Based on current internal priorities, we aren't actively developing the custom source API right now. You can see our roadmap here: https://www.mapbox.com/mapbox-gl-js/roadmap/

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

No branches or pull requests

2 participants