-
Right now only supports WKT strings.
-
### Problem
If we provide proj4 or WKT strings as input to domain and other functions that require spatial reference we have to parse these strings and create osr.SpatialReference and then convert it…
-
I am starting a refactoring of DaoSpatialite. I will split it into a few more classes and also document **every** possible piece.
So I will start with questions here. Let's refer with answers to the…
-
WKTShapeParsers should be able to read WKT strings that contain:
- Z and/or M values
- optional Z/M/ZM flags (as defined by the latest OGC Simple Feature Access specification)
At present I have no re…
-
Issue imported from Google Code: https://code.google.com/p/sequel-pro/issues/detail?id=291
Reporter:sgrosm...@gmail.com Date:2009-06-09 14:32:34 Status:Implemented Closed:2011-01-01
feature request:
…
-
There is a lot of repetition in these methods that can be refactored and cleaned up. Get to cleaning.
-
After replacing the WebMap plugin with the BrutileLayer implementation, The OSM (Mapnik) TMS provider is shifted by about 100m south-west if we overlay our application features..
We moved on to the B…
-
Support should be added for the following WKT syntax. I don't think it's defined in any standard, but several existing GIS libraries/systems already support this syntax (including PostGIS and Geotoolk…
-
well known text is being complicated because as far as I can tell the esri wkt and the proj4js strings on spatial reference don't actually match up with each other
-
Currently, Wicket writes WKT strings two different ways, depending on the geometry type. Both are valid, but Wicket ought to do it just one way for consistency. As stated before, I'd like to expose a …