Martin Fleischmann

I think that this can be useful elsewhere and should live in GeoPandas. It may also be easier for us to maintain it than for datashader. > One possible idea...

@jbednar GeoPandas talks about geographic data while in reality supports any planar geometry no matter the origin. > Would GeoPandas be ok with stating on the home page that "Geo"...

Hi @brunob, we already have that magic in `xyzservices`. We scrape your JS to get that JSON but the result is slightly adapted to work within our use case. But...

@brunob Yeah, we do that within this GHA https://github.com/geopandas/xyzservices/blob/main/.github/workflows/update_providers.yaml using this [makefile](https://github.com/geopandas/xyzservices/blob/main/Makefile)

What about using YAML instead if we need comments? That feels as a bit more standard solution than JSONC.

I'd be happy to add them, it is certainly in the scope of momepy. Though I am not sure when I'll have time for that myself, it probably won't be...

I sense that it is the data issue. Can you share the bit of data causing a trouble? And the rest of your code including affecting this? In theory there...

Thanks for the report. I see the same behaviour on my side. Not sure what is causing it though, will need to dig.

@adhamenaya I figured out the issue. It is not a bug in momepy or any of the dependencies but in your code above. I didn't notice that you commented out...

I'll keep it open to add those warnings.