procedural-gl-js
mapbox-gl-js
Our great sponsors
procedural-gl-js | mapbox-gl-js | |
---|---|---|
11 | 13 | |
1,266 | 10,691 | |
- | 0.7% | |
0.0 | 9.8 | |
almost 3 years ago | 8 days ago | |
JavaScript | JavaScript | |
Mozilla Public License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
procedural-gl-js
-
Recreating Real-World Terrain with React, Three.js and WebGL Shaders
Nice writeup, I always like it when the shaders are highlighted like this. I got started in a similar way 7 years ago and have been making 3D terrains with THREE.js & WebGL since.
The real fun begins when you need to implement some sort of Level-of-Detail system and streaming in data to give the illusion of high detail everywhere without sacrificing performance.
Last year I released an open-source framework (https://github.com/felixpalmer/procedural-gl-js) for creating 3D terrains for web applications, you can see Uluru here: https://www.procedural.eu/map/?longitude=131.036&latitude=-2... (unfortunately the aerial imagery from our default provider isn't as high resolution as other places in Europe)
-
Visualization of 40M Cell Towers
Great visualization and approach with compressing the tile data. Do you have a comparison of how much smaller the payload ends up being compared to simply sending PNG files?
I use PNGs to encode elevation data in my 3D mapping library (https://github.com/felixpalmer/procedural-gl-js/) and this does a pretty good job of compressing the data, for example in the ocean the PNG files are also very small as the image is mostly black. Different use case I now as your data is much more sparse, but I wonder how close the PNG compression would be compared to your approach.
-
React Component for 3D Maps
Bug reports are welcome at: https://github.com/felixpalmer/procedural-gl-js/
Also the geocoding quota issue has been resolved
Yeah, the React parts of this are very minimal. I'm not really sure what using it gets you, since it just manages a single div.
The _actual_ library that does all the work is here: https://github.com/felixpalmer/procedural-gl-js
-
Ask HN: What Are You Working On?
- Tiny filesize means library is parsed fast. Package size is less than THREE.js thanks to code stripping
Check it out on Github: https://github.com/felixpalmer/procedural-gl-js/
-
Mountain Peaks in WebGL
> https://github.com/felixpalmer/procedural-gl-js/
> Key features
> Batteries included elevation data. Global 3D data coverage courtesy of nasadem.XYZ
Generally just a choice for the demo - in part because restricting the view distance means less data to download (thus lower cost to serve!). If you switch the phone to portrait you will be able to see the horizon.
The library itself (https://github.com/felixpalmer/procedural-gl-js) lets you configure the angle freely.
Hi HN, Merry Christmas to all!
I made this as a demonstration of the open data available from the Austrian government under the www.basemap.at project. The rendering engine is built on top of THREE.js and can be found here: https://github.com/felixpalmer/procedural-gl-js/
For those in the southern hemisphere, there is also a similar visualization of the national parks of New Zealand: https://felixpalmer.github.io/new-zealand-3d/
That's not a bug, it's Germany! The aerial imagery comes from the Austrian basemap.at dataset, which only covers Austria. If you use imagery that covers multiple countries this isn't an issue, but for this project I wanted to try out the basemap.at data. See https://github.com/felixpalmer/procedural-gl-js/ for more
The imagery comes from the Orthofoto dataset on https://www.basemap.at/ - the actual texturing is done by the Procedural GL JS library https://github.com/felixpalmer/procedural-gl-js
mapbox-gl-js
-
Brave browser simplifies its fingerprinting protections
Good. Brave's fiddling with WebGL causes >50% of my bug reports from 1% of users.
-
Getting Started with MapLibre GL JS
It originated as an open-source fork of Mapbox-gl-js before they switched to a non-open-source license on 8th December 2020.
-
Reimagining projections for the interactive maps era
> too bad it doesn't come with some code
Mapbox changed the license of their code last year I think to a proprietary one. https://github.com/mapbox/mapbox-gl-js/blob/main/LICENSE.txt
It requires a mapbox user license with billing enabled to use this code, let alone make modifications. But the source is viewable on github.
-
MapLibre GL is a free and open-source fork of mapbox-gl-JS
From https://github.com/mapbox/mapbox-gl-js
> Mapbox gl-js version 2.0 or higher (“Mapbox Web SDK”) must be used according to the Mapbox Terms of Service. This license allows developers with a current active Mapbox account to use and modify the Mapbox Web SDK. Developers may modify the Mapbox Web SDK code so long as the modifications do not change or interfere with marked portions of the code related to billing, accounting, and anonymized data collection. The Mapbox Web SDK only sends anonymized usage data, which Mapbox uses for fixing bugs and errors, accounting, and generating aggregated anonymized statistics. This license terminates automatically if a user no longer has an active Mapbox account.
Seems their client code does some things related to "billing, accounting, and anonymized data collection" and they don't want programmers to disable or modify that code.
Is that right? Anyone who has followed this have more information? I haven't used mapbox in a few years but I think it's great technology.
The software stopped being open source from v2 onwards. The new licence makes it merely shared source.
This GitHub issue where this change is announced provides a number of more in-depth explanations why this is a bad thing for most users of the software: https://github.com/mapbox/mapbox-gl-js/issues/10162
-
Ask HN: What Are You Working On?
It's a bummer mapbox isn't open source anymore, now you're (and lots of other peoplare) are stuck pre-2.0.0 :(
https://github.com/mapbox/mapbox-gl-js/blob/main/CHANGELOG.m...
-
Top Javascript Maps API and Libraries
Web-site: https://www.mapbox.com/ GitHub stars: 6.1k, https://github.com/mapbox/mapbox-gl-js Pricing: Free, starts from $2.40 for 1000 loads Map Data Source: Mapbox Dependencies: None License: Mapbox copyright Category: Web Application Examples: https://docs.mapbox.com/mapbox-gl-js/examples/
What are some alternatives?
maplibre-gl-js - MapLibre GL JS - Interactive vector tile maps in WebGL2
cesium - An open-source JavaScript library for world-class 3D globes and maps :earth_americas: [Moved to: https://github.com/CesiumGS/cesium]
h3 - Hexagonal hierarchical geospatial indexing system
ffprobe-wasm - A Web-based FFProbe. Powered by FFmpeg, Vue and Web Assembly!
martin - Blazing fast and lightweight PostGIS, MBtiles and PMtiles tile server, tile generation, and mbtiles tooling.
tangram - WebGL map rendering engine for creative cartography
electron-browser-shell - A minimal, tabbed web browser with support for Chrome extensions—built on Electron.
OpenLayers3 - OpenLayers
maplibre-native - MapLibre Native - Interactive vector tile maps for iOS, Android and other platforms.
rust-starter - Rust Starter Project
maps - A Mapbox react native module for creating custom maps