Re: [Talk-in] Understanding "unprojection"
Sorry, to come to your other questions: > I haven't published this script online because I'm afraid it'll get used recklessly and cause excess load on the target tile server.It generates a Z/X/Y URL list of tiles at multiple zoom levels. Then I used a download manager to download the tiles with some time gap (so I don't trigger a server lockout), with z/x/ folder paths maintained. A python library does this, where it takes a bounding box and a zoom, and generates z/x/y at zooms for the bounding box. Is your script doing something different from this? Warmly, Aruna ___ Talk-in mailing list Talk-in@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-in
Re: [Talk-in] Understanding "unprojection"
Hey Nikhil! Thanks a lot for taking the time to answer this. I did not know about these verifiers and validators at all, so I learnt a little bit more about GIS weirdness. : ) I ran the geojson through the verifier, and tried running my script with the updated geojson. Unfortunately, it seems to be something else - I am not sure if tile boundaries or other complications with the mbtiles files is causing this issue, since these polygons aren't able to be cut up from any mbtiles file that I ran them on. The question is now present on the GIS StackExchange at https://gis.stackexchange.com/questions/301975/mbtiles-extracts-does-not-work-with-my-geojson . Thanks again, Nikhil! : ) Warmly, Aruna ___ Talk-in mailing list Talk-in@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-in
[Talk-in] Understanding "unprojection"
Hi everyone! I am working with the mbtiles-extracts library: https://github.com/mapbox/mbtiles-extracts. Given an mbtiles file and a geojson, the library extracts mbtiles cutouts of the polygons in the geojson. Except, it does not work for some geojsons. As documented in https://github.com/mapbox/mbtiles-extracts/issues/10, it does not work for any polygon present in the following geojson for the mbtiles listed below: - MBTILES: Pretty much every tileset on https://osmlab.github.io/osm-qa-tiles/historic.html. Can definitely replicate it using for https://s3.amazonaws.com/mapbox/osm-qa-tiles/historic/2008-Q1-qa-tiles.mbtiles - GEOJSON: https://gist.github.com/arunasank/c98ef28abd51b54579c7609f8ebc1de1 When I debug, I see that: * This function: https://github.com/mapbox/mbtiles-extracts/blob/master/index.js#L175 returns a falsy value for all the features in the above geojson, resulting in a falsy value here: https://github.com/mapbox/mbtiles-extracts/blob/master/index.js#L58-L62 Any help in understanding why these polygons are different from other polygons, or if there's a pattern I am missing, would be really helpful! If there are other mailing lists where this could be answered, please point me to them. Warmly, Aruna ___ Talk-in mailing list Talk-in@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-in
