search

ioda-net / geo-api3

Backend from geoadmin/mf-chsdi3
Other
2 stars 0 forks source link

height profile should be asked with the right epsg #54

Closed tigerfoot closed 8 years ago

tigerfoot commented 8 years ago

Our demo api is using bt file in epsg:2056 (2M,1M) front is using epsg:21781 and ask wrong coordinates 500K,200K

Expected result, if api is setup with epsg:2056 the front request have to use the same epsg

Jenselme commented 8 years ago

Strange, I have this payload in 2056 (front from https://github.com/ioda-net/mf-geoadmin3/tree/ioda-net):

------WebKitFormBoundarycToDT35WQB6h0eit
Content-Disposition: form-data; name="geom"

{"type":"LineString","coordinates":[[2594410.0,1237500.0],[2595680.0,1236840.0],[2595680.0,1236840.0],[2593970.0,1236170.0]]}
------WebKitFormBoundarycToDT35WQB6h0eit
Content-Disposition: form-data; name="elevation_models"

COMB
------WebKitFormBoundarycToDT35WQB6h0eit--
Jenselme commented 8 years ago

Solved.