Stefan
Stefan
I can confirm what @dbrgn wrote above. The Overpass API (over http with json/geojson response) is a well known "entry point" to get data out of OSM (see User's Manual...
> (though it will lead to fragmentation with some people contributing to GoingElectric, some to OpenChargeMap and some to OpenStreetMap...) I'm not sure about how much the fragmentation will be...
Concerning documentation I updated https://github.com/geometalab/OSMDeepOD/blob/master/README.md with a new section "Material".
I can't believe that the core code to read GeoPackage in geopackage-js package is that big. I quickly looked into geopackage-js package and here's definitely some other bloat code in...
@KostyaEsmukov commented on 24 Nov 2018: > it's ok, I guess I'll do that then. :) Any updates on this issue? Because if no, we'll do that then perhaps:-O.
FYI: See also issue #50 .
Sorry for insisting but e.g. #29 is closed just because it's referring to this overdue open issue. Allow me to make an understatement: The lack of support from Mapbox of...
@ericfischer : Thanks. We're reviewing the spec revision now. It's really not just me waiting for this update (also of TileJSON) it's for the sake of innovation based on established...
I'm glad to see mbtiles 1.3 released! https://github.com/mapbox/mbtiles-spec Now I hope there will be soon a similar update of this TileJSON spec.!
I support this issue to use 'Fee' at Service level. I've investigated a bit: 7.2.4.3 General service metadata obviously does to ISO 19128 WMS spec. (not to WMTS - but...