Potential Settler Sponsor here! about procedural-gl-js HOT 3 OPEN

Hi,

I'm glad to hear you like the repo and excited that you're considering a substantial sponsorship. Thank you! To answer your questions:

• There is a React wrapper available here: https://github.com/felixpalmer/procedural-gl-react
• I have not tried, but in principle I don't see why not. It would be awesome to get a community contribution on this and the React wrapper should act as a good starting point.
• Not sure exactly what you mean here, could you elaborate?
• Just yesterday I released a new version which enables this, see https://github.com/felixpalmer/procedural-gl-js/wiki/Data-sources for details. I believe this should work with Mapbox on a technical level, but I am not aware of Google Maps providing elevation tiles
• Yes, any raster tile data layer can be used, again https://github.com/felixpalmer/procedural-gl-js/wiki/Data-sources has details.
• Like with A-frame, this has not been implemented

If you're serious about the sponsorship, I would consider building A-frame & WebXR wrappers, but otherwise it is fairly low priority for me, not to mention the fact that it would require investment into hardware from my side.

from procedural-gl-js.

Hi, sorry for the delay.
Well I was playing with procedural-gl on react with hooks. I left a issue on the repo there. Maybe you can help.

Do you have any planned roadmap?

There are some features I would like to see as future sponsor:

• More detail on maximum zoom (on my tests it only show low quality tiles)
• Wrapping this on A-frame (would mean full compatibility with WebXR)
• Better documentation on how to use other tile and elevation providers
• Way to show labels of roads, cities, parks, etc
• Create callback on interaction with overlays or markers
• Control of light parameters (to create night and day effects)
• Way to import/export KMZ files
• Planet view and more LOD levels

Well this might be too much, but this library deserves it :)

from procedural-gl-js.

The current focus is on getting the word out about the library and supporting those who building something serious with it. As such, the roadmap is currently somewhat in flux. Regarding your list:

• Maximum zoom is already being tracked here #24
• A-frame I covered in my previous reply
• It should mostly be a case of changing some URLs, I believe it is covered here: https://github.com/felixpalmer/procedural-gl-js/wiki/Data-sources (if there is a specific provider that is problematic then please create a separate issue)
• You can add custom overlays (see e.g. https://www.procedural.eu/overlays.html) and in the future I plan on adding the ability to add a vector tile source
• There already is such a callback https://www.procedural.eu/module-Features.html#.onFeatureClicked
• I've toyed with this in the past, but it isn't high priority right now.
• My feeling is that it is simpler to just support geojson, and if KMZ or another format is required then a converter can be used by the consumer of the library. I don't think it is worth bloating the library with a converter that won't be used by all
• See my thoughts on this here: #12

from procedural-gl-js.