django - GeoDjango Converting SRID 4326 to SRID 3857 -


i'm having difficulty converting srid 4326 coordinates geocoder srid 3857 storage within postgres-postgis database. using following code test transforming between srids:

from django.contrib.gis.gdal import spatialreference, coordtransform django.contrib.gis.geos import point gcoord = spatialreference(4326) mycoord = spatialreference(3857) trans = coordtransform(gcoord, mycoord)  pnt = point(47.61, -122.33, srid=4326) print 'x: %s; y: %s; srid: %s' % (pnt.x, pnt.y, pnt.srid)

x: 47.61; y: -122.33; srid: 4326

pnt.transform(trans) print 'x: %s; y: %s; srid: %s' % (pnt.x, pnt.y, pnt.srid)

django.contrib.gis.gdal.error.gdalexception: ogr failure.

within django, more helpful error message:

transform: couldn't project point (47.61 -122.33 0): latitude or longitude exceeded limits (-14)

i've performed rudimentary testing , determined lat/long coordinate outside of 0-90 trigger condition. setting point field in django srid=4326 , migrating database still results in point being converted srid 3857.

i stumbled here. issue that, in calling point constructor, longitude needs come before latitude. (never mind latitude/longitude, in order, may engrained in our minds...) longitude 'x' , latitude 'y'. so, should have:

pnt = point(-122.33, 47.61, srid=4326)

or, better yet, use named arguments clarity:

pnt = point(x=-122.33, y=47.61, srid=4326)

Comments

Post a Comment

Popular posts from this blog

c# - Validate object ID from GET to POST -

i have method allows user access comment have made on site. have post method lets them update comment. my normal solution send entire comment model through, let them update it, update on database when post back. involve sending commentid through in hiddenfor , can manipulated. how can verify commentid sent in get method same i'm getting in post , not able alter comment wish? how can verify commentid sent in method same i'm getting in post? basically have validate following things in post - user logged-in user. authenticated users post comments. commentid in post , should valid commentid , should present in database. userid associated logged-in user should same userid associated comment . comment should contain userid column, can check @ time of update. to make sure update happens comment has been sent in get - hold commentid in session , in post action compare commentid value in session .
Read more

node.js - Custom Model Validator SailsJS -

when using custom model validator checks record within model. return within spread doesn't seem end control flow. //post.js model /** * custom validator **/ types: { isuservalid: function(user_id) { var promise = require('bluebird'); promise.all([ user.findone({id: user_id}) ]) .spread(function(user) { console.log(user); if (user === null || user === undefined) { console.log('failed'); return false; }else{ console.log('passed'); return true; } }); } }, my response standard validation failed response. { "error": "e_validation", "status": 400, "summary": "1 attribute invalid", "model": "post", "invalidattributes": { "owner": [ { "rule": "isuservalid", ...
Read more

php - Find a regex to take part of Email -

i have following emails need extract part from: bestellnummer xxx: 1 von xxx, 1er pack ------------- anfang der nachricht ------------- foo bar baz foo bar baz // <<<<< need text here ------------- ende der nachricht ------------- ------------- anfang der nachricht ------------- foo bar baz foo bar baz ------------- ende der nachricht ------------- there 0 unlimited occurences of ------------- anfang der nachricht ------------- ------------- ende der nachricht ------------- and i'm able extract first part regex: $re = "/------------- .*? -------------.?(.*?).?------------- .*? -------------/s"; but, i'm quite new on learning regex, i'm pretty sure there must better regex extract part (foo bar baz foo bar baz) of text between ------------- anfang der nachricht ------------- ------------- ende der nachricht ------------- as can in different languages, i'm using .? to match between hyphens. i...
Read more