At 2011-02-03 09:17, Steve Coast wrote:
http://www.bing.com/community/site_blogs/b/maps/archive/2011/02/03/automatically-detect-roads-with-bing-aerial-imagery.aspx
This is something that has the potential to greatly increase mapping
productivity!
A couple of things:
1. When I run the sample
http://magicshop.cloudapp.net/DetectRoad.svc/detect/?pt1=47.6274924080735,-122.119339391984&pt2=47.6266897967272,-122.116431877412&bbox=47.628475815791,-122.120927259721,47.6254135470002,-122.114489958085
It produces a road segment that is not very well centered. The imagery for
this area is rather good (~0.06m/pel - zoom 21) and it should be a fairly
easy case. Can someone look at this? Is it being too sensitive, not
sensitive enough, etc.? Can some of the internal parameters be exposed so
we can play with them?
2. When I try
http://magicshop.cloudapp.net/DetectRoad.svc/detect/?pt1=47.6312440,-122.1126077&pt2=47.6263360,-122.1179483&bbox=47.632,-122.119,47.625,-122.109
it complains "Error Status Code: 'BadRequest' Details: The points are too
close together." Even though these points are further apart (~700m) than
the ones in the example.
--
Alan Mintz <[email protected]>
_______________________________________________
talk mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk
