5 reasons to use Leaflet JS | Introduction to Mapping Libraries

Поделиться
HTML-код
  • Опубликовано: 29 окт 2024
  • НаукаНаука

Комментарии • 8

  • @JaRatr
    @JaRatr 9 месяцев назад

    My favorite part about leaflet is following their quick start guide step-for-step and viewing the gray box it produces. Fun stuff...

  • @johnsnow8252
    @johnsnow8252 Год назад +2

    Totally agree with you. Leaflet is great, simple but powerful, sutiable for building prototype. But I prefer mapbox-gl-js for production😂.

    • @kirkislas4320
      @kirkislas4320 9 месяцев назад +1

      thx for putting me on bruh

  • @meitoli
    @meitoli 2 месяца назад

    thank you for the explanation. New to this. I have this project with all the sea points will have 10 images to show for any point of the sea map. These images are in a 500 gb disk and all the images have the lat and long number in their names to easy like pair with the actual sea point. I was wondering if Leaflet will be a good choice..

  • @mabrarrubaiyatislam5653
    @mabrarrubaiyatislam5653 6 месяцев назад

    So, Which library should I use for heavy data. consider 60 thousand rows of line geometry and 1,80,000 rows of point geometry I need to pull hit and convert to geojson to show in map. it is becomes quite slow.

    • @learnwithmapster
      @learnwithmapster  6 месяцев назад

      I'd be loading that in as part of a base tileset via something like Mapbox and MTS

  • @denischikita
    @denischikita Год назад

    Confusion brings what concept of tiles and controller lib separation. So I just don't agree what leaflet is simple. I found it pretty confusing even on basic tasks. For example I can't customise geocoding input and i cant use my own as source to geocode API, at least there is no clear documentation on it. So I end up with Google Maps, because they have all in one package and fine documented manual.

    • @learnwithmapster
      @learnwithmapster  Год назад

      I would say that Leaflet and Google maps have a similar overall philosophy when it comes to the way the libraries function (compared to Mapbox/Maplibre, for instance). However, Leaflet does have plenty of complexity when it comes to integrating functionalities that aren't core to leaflet, like geocoding, as you mention -- you'd need to use external plugins. Glad you found your solution in Google Maps -- although were you able to plug in your own geocoder there?