Andrew
Andrew
@davidbrochart ok, I'll check out ipywidgets changes. We noticed that when we downgrade from v7 to v6 of the client, the issue goes away. Maybe that downgrade is downgrading ipywidgets.
How do you handle holes?
Thank you, I would appreciate that.
Is there a way to add Spatial References to this information?
you probably can just add another dictionary value: ``` Points = { "size": 3, "dtype": int64, "stride": 2, "sizes": [2, 2, 2], "offsets": [2, 4, 6], "values": [x,y,x,y,x,y], "spatialReference" :...
Sure thing Version information: requests 2.13.0 py35_0 requests-kerberos 0.11.0 py35h2d28538_1 anaconda requests-oauthlib 0.8.0 py35_1 conda-forge requests-toolbelt 0.8.0 py35_0 conda-forge requests_ntlm 1.0.0 py_0 conda-forge
thanks, will do.
Everything could be packaged like the geometry format in geopackage in spec 2.1.3.1.1. BLOB Format. Where the Srid is in the header itself. It could remove the requirement of storing...
@cholmes if you want to parse geojson, you can have mixed types. Feature classes, like shapefiles, only allow single geometries. The geopackage WKB with additional headers is very attractive because...
I think allowing well known Ids and WKT is a benefit. If you are using WGS1984, a very common well known coordinate system, why do I need to enter in:...