JOSM / areaselector

JOSM Area Selection Plugin
https://github.com/JOSM/JOSM-areaselector/wiki
18 stars 3 forks source link

No matching areas using Bing imagery #24

Closed jasonharrison closed 7 years ago

jasonharrison commented 7 years ago

Hi, I am trying to use this areaselector plugin with Bing aerial imagery and, regardless of what I click on, I get a large square box. It would appear that areaselector is not detecting any imagery or colours at all.

I am using JOSM version 11114 on Mac OS X 10.9 with Bing aerial imagery. I have not been able to test this with other image sources.

Here are some logs:

20:06:15.224 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.AreaSelectorAction - mouse clicked java.awt.event.MouseEvent[MOUSE_CLICKED,(622,335),absolute(670,413),button=1,modifiers=Button1,clickCount=1] on org.openstreetmap.josm.gui.MapView[,0,0,878x845,alignmentX=0.0,alignmentY=0.0,border=,flags=0,maximumSize=,minimumSize=java.awt.Dimension[width=10,height=0],preferredSize=] 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.AreaSelectorAction:129: mouse clicked java.awt.event.MouseEvent[MOUSE_CLICKED,(622,335),absolute(670,413),button=1,modifiers=Button1,clickCount=1] on org.openstreetmap.josm.gui.MapView[,0,0,878x845,alignmentX=0.0,alignmentY=0.0,border=,flags=0,maximumSize=,minimumSize=java.awt.Dimension[width=10,height=0],preferredSize=] [] 20:06:15.314 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - Using following params for algorithm: colorThreshold=14 toleranceDist=4.5 toleranceAngle=0.41887902047863906 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:146: Using following params for algorithm: colorThreshold=14 toleranceDist=4.5 toleranceAngle=0.41887902047863906 [] 20:06:15.560 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - Found 0 matching polygons 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:794: Found 0 matching polygons [] 20:06:15.561 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - Falling back to custom detection 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:161: Falling back to custom detection [] 20:06:15.561 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - point color: java.awt.Color[r=0,g=0,b=0] 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:165: point color: java.awt.Color[r=0,g=0,b=0] [] 20:06:15.562 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - extracting marvin color 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:195: extracting marvin color [] 20:06:15.594 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - Applying gaus filter 2016-10-11 20:06:15 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:207: Applying gaus filter [] 20:06:16.109 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - searching for the correct color 2016-10-11 20:06:16 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:211: searching for the correct color [] 20:06:17.435 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - Found 1 matching polygons 2016-10-11 20:06:17 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:794: Found 1 matching polygons [] 20:06:17.435 [AWT-EventQueue-0] INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer - Best matching polygon is: Polygon (4 points) [ (0,0) (877,0) (877,844) (0,844)] 2016-10-11 20:06:17 INFO org.openstreetmap.josm.plugins.areaselector.ImageAnalyzer:808: Best matching polygon is: Polygon (4 points) [ (0,0) (877,0) (877,844) (0,844)] []

Any ideas? Thanks!

jasonharrison commented 7 years ago

I tried JOSM 10799 as suggested in issue #25. The plugin appears to work as intended in this version. My issue begins with version 10819+.

r00tat commented 7 years ago

@jasonharrison I'll close this issue, because it's clearly the issue described in #25. I'll work with the other JSOM developers to fix JOSM core.