Wow, it is fast! I could see it had my test-route drawn and ready before the scrolling animation to the start had even finished.
Maps.earth – free and open-source web maps
101–110 of 117 posts
Re: Maps.earth – free and open-source web maps
#102Earlier quoted context omitted.
OSM doesn't have a server per se (other than the OSM API server). It's a dataset for the most part. Headway lets you bring up a server that will render maps tiles, allows you to search for places and get routes between places. It's trying to be a user-friendly UI for various pieces of the OSM ecosystem. There are a lot of amazing pieces of software out there that work with OSM data, but there isn't an easy way to bri…
There no frontend to bring up an OSM? Literally you need a single line to load one up: (new map('map_div')).addLayer(new TileLayer('http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png'))
Note that the {s} part is for backwards compatibility, and that https://tile.openstreetmap.org is enough, or maybe even a tiny bit faster, now that we have http 2.
Re: Maps.earth – free and open-source web maps
#103A few things that I notice in the area where I'm somewhat active as an OSM contributor:
- You probably shouldn't render guideposts or route markers on the map, or at least not with generic "info" icon.
- Things with access=private are likely not terribly relevant to people looking at the map. This will include things like parking spots or gardens.
- Lots of shots and amenities have icons, but doctors don't. Neither do fire stations.
- Sports pitches are shown as nodes, but may be better shown as areas, since they often cover quite extensive swaths of ground that's otherwise empty with just an icon in the middle. Same with playgrounds, schools, and kindergartens, gardens, and parks.
- For buildings and building parts, if you don't make use of the parts in any way (such as showing roofs, height, etc.) perhaps just disregard the parts and only render the building outlines. This, combined with the fact that geometries seem to be simplified, even at the highest zoom levels, results in a bit of a mess of lines at times where some outlines are simplified differently from others that should actually share parts of the same edges and thus overlap perfectly. (e.g. https://maps.earth/place/openstreetmap%3Avenue%3Away%2F11120... or https://maps.earth/place/openstreetmap%3Avenue%3Away%2F11120...). Same thing with the geometry simplification also happens with adjacent geometry that should actually not have gaps (e.g. semidetached houses or garages next to houses). Lots of buildings that are actually rectangular also get quite weird angles.
- Tunnels are quite subtle. And while at least roads in tunnels don't overlap buildings that are actually above them (like with Carto) it's still hard to make out what's above and what's below in such cases (e.g. https://maps.earth/place/openstreetmap%3Astreet%3Apolyline%3...). Culverts for waterways are handled better than roads in tunnels in this case.
Overall though, this seems like a quite nice map style. Closer to Google Maps in that it emphasizes roads, but some people like the less detailed look (and it works better with vector maps, I guess, to have fewer polygons to render).
Re: Maps.earth – free and open-source web maps
#104I have found an error in a street name. Where could I report it?
Re: Maps.earth – free and open-source web maps
#105Re: Maps.earth – free and open-source web maps
#106Earlier quoted context omitted.
Thanks! MapTiler looks great, but a bit on the pricey side for our use case.
We picked it specifically because Mapbox was too expensive. We pay like between 20 and 30 euros each month for tens of thousands of transactions. You can also buy tile sets and serve your own vector tiles, but it isn't worth the hassle for us.
Have you ever compared it to https://github.com/Overv/openstreetmap-tile-server ?
Re: Maps.earth – free and open-source web maps
#107Works surprisingly well! One note for walking directions: It doesn't seem to take elevation gain into account in choosing between alternate routes. Probably a not an easy thing to implement.
Re: Maps.earth – free and open-source web maps
#108Earlier quoted context omitted.
We picked it specifically because Mapbox was too expensive. We pay like between 20 and 30 euros each month for tens of thousands of transactions. You can also buy tile sets and serve your own vector tiles, but it isn't worth the hassle for us.
Have you ever compared it to https://github.com/Overv/openstreetmap-tile-server ?
No. We no longer want to bother with monthly updates and the overhead of maintaining our own tile server over <30€/month. We tried to make our own raster tile server several years before vector tiles were a thing, using tilecache, then tilestache and just gave up because of the storage and hardware requirements. Plus there's a lot of work involved in customizing your maps - we didn't want to show the standard OSM map built for mappers in mind but a transport oriented map for fleet tracking. MapTiler has almost everything we want except good Africa coverage.
Re: Maps.earth – free and open-source web maps
#109I have found an error in a street name. Where could I report it?
On https://www.openstreetmap.org
See the tutorial there or https://learnosm.org/en/beginner/start-osm/
Re: Maps.earth – free and open-source web maps
#110Thanks for this. I'm curious to know: why did you include two routing engines (OTP and valhalla)? Wouldn't e.g. OTP sufficient and use much less resources compared to 2 setups? And why not reuse one of the existing open source map or directions front-ends?
Looks like they use either mapbox gl is or maplibre gl js to render the map
I meant there are many ready-to-use map UIs out there already, like the UI from OTP or valhalla itself. No need to reinvent the wheel.
E.g. see https://valhalla.openstreetmap.de/
Or https://github.com/Qwant/erdapfel
Or https://graphhopper.com/maps2 & https://github.com/graphhopper/graphhopper-maps (disclaimer: I'm a contributor there)