Live data from Hacker News

OpenLayers

openlayers.org

21–30 of 89 posts

Re: OpenLayers

#21
post #18

We used openLayers, ran in to performance issues, switched to Leaflet, and couldn't be happier. Just our experience, for what it's worth.

I used Leaflet and had to do some things with realtime visuals in D3 as overlay for Leaflet, because of performance issues.

Re: OpenLayers

#22
post #4

Earlier quoted context omitted.

Well, I think it has better (official) WebGL support than leaflet, but most all the developers I know are jumping to Mapbox by default. EDIT: My favorite open source library right now is maptalks. Basically mapbox sort of functionality and rendering, but totally free.

In what way is mapbox-gl not free? It's developed in the open, and works with all types of layers. I switched to mapbox-gl the moment it came out, because I already was making my own vector tiles as needed for interactive maps. There is only one issue I encountered in the short few years it's been my go-to choice, which is that there are no plugins to integrate Google Streetmaps or Streetview. There are however, for…

Maybe I misunderstood, do you only pay for the tiles on mapbox? I’m just accustomed to having to use a restricted api key with mapbox.

If that’s the case I’m totally ditching maptalks for all it’s quirks.

And I don’t know of any libraries for google street view integration, but a dev I work with has done a fantastic job of integrating street view with map box. I’ll try to dig up some of his code

Re: OpenLayers

#23
post #18

We used openLayers, ran in to performance issues, switched to Leaflet, and couldn't be happier. Just our experience, for what it's worth.

We had the exact opposite problem! We built a custom webgl rendering layer on top of leaflet to get around leaflet's performance issues. We have now switcher to openlayers and very happy. Guess it depends on the exact use case.

Re: OpenLayers

#24

Earlier quoted context omitted.

Interesting, thanks. Unfortunately, those tiles are pretty ugly compared to Mapbox, but it might be an option if I can't find anything else. Edit: Also it's $1,000 for commercial use, even to use with OSM data?

You can style the tiles or use your own. Where did you find the $1000 quote? I know you can have them hosted unlimited for $245/month but I was fairly sure it was free for self-hosted use.

Update: So if you run the server locally and select maps, you're presented with this screen, saying you need a key from openmaptiles.com: https://i.imgur.com/NTb5zIL.jpg.

If you select "commercial product or company web", you're asked to pay for it: https://i.imgur.com/TrAmju4.jpg

If you select any of the non-commercial ones, the newest map data you get is from 2017 (!).

I'm not against paying, but it's not free!

Re: OpenLayers

#25

Earlier quoted context omitted.

Interesting, thanks. Unfortunately, those tiles are pretty ugly compared to Mapbox, but it might be an option if I can't find anything else. Edit: Also it's $1,000 for commercial use, even to use with OSM data?

You can style the tiles or use your own. Where did you find the $1000 quote? I know you can have them hosted unlimited for $245/month but I was fairly sure it was free for self-hosted use.

Forgot to answer about styling. Yes, looks like custom styles with the production package (which has hillshading, which ends up making the maps look much nicer) is much better. For some reason their main demos don't show off their best map styles.

Re: OpenLayers

#26

Earlier quoted context omitted.

In what way is mapbox-gl not free? It's developed in the open, and works with all types of layers. I switched to mapbox-gl the moment it came out, because I already was making my own vector tiles as needed for interactive maps. There is only one issue I encountered in the short few years it's been my go-to choice, which is that there are no plugins to integrate Google Streetmaps or Streetview. There are however, for…

Maybe I misunderstood, do you only pay for the tiles on mapbox? I’m just accustomed to having to use a restricted api key with mapbox. If that’s the case I’m totally ditching maptalks for all it’s quirks. And I don’t know of any libraries for google street view integration, but a dev I work with has done a fantastic job of integrating street view with map box. I’ll try to dig up some of his code

For some layers my projects do pay for MapBox tile service, but for other projects I use OSM extracts and self-made vector tiles. Mapbox charges only for the tile services, and there are multiple data sources out there, with which mapbox-gl works. It honestly the smart thing to do, as without such flexibility, I wouldn't be using their services or libraries at all.

> but a dev I work with has done a fantastic job of integrating street view with map box. I’ll try to dig up some of his code

This would be a pretty popular library, I am sure! The issue is that the Google EULA prohibits the use of their data directly, it has to be accessed using Google Maps SDK. So Google Mutant Leaflet plugin has to use the API to download the tiles and then exposes the Google Layer a custom Leaflet Layer, but it works :) On the mapbox issue tracker, they close all issues inquiring for help in implementing such a custom layer, so if your coworker did this, I'm sure it was a non-trivial exercise, kudos to him! :)

Re: OpenLayers

#27
What is the advantage of having the documentation CC-BY 3.0 licensed ? In cases where documentation is generated from the code it seems more convenient to use the same license for both.

Re: OpenLayers

#28
post #18

We used openLayers, ran in to performance issues, switched to Leaflet, and couldn't be happier. Just our experience, for what it's worth.

What kind of performance/use case did you have? I haven't touched leaflet since the giant rewrite.

Re: OpenLayers

#29
When compared to the other two major OSS libraries I would say:

- Leaflet. Widely known, suitable for mostly simple use cases.

- Mapbox GL JS. State of the art library based on WebGL. Mapbox started off with a fork/extension of Leaflet called Mapbox.js but over time has moved on and created the Mapbox GL JS library from the ground up. Very fast, but requires a GPU due to WebGL.

- OpenLayers. Often used by more professional users. Probably the most features complete library. Also usable without a GPU.

Re: OpenLayers

#30

When compared to the other two major OSS libraries I would say: - Leaflet. Widely known, suitable for mostly simple use cases. - Mapbox GL JS. State of the art library based on WebGL. Mapbox started off with a fork/extension of Leaflet called Mapbox.js but over time has moved on and created the Mapbox GL JS library from the ground up. Very fast, but requires a GPU due to WebGL. - OpenLayers. Often used by more profes…

Thank you so much for this, I was wondering what the differences were. I've used Leaflet, but not OpenLayers or Mapbox.
Post reply on HN