Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Search with one result zooms to incorrect area #90

Closed
elil opened this issue Jun 29, 2015 · 2 comments
Closed

Search with one result zooms to incorrect area #90

elil opened this issue Jun 29, 2015 · 2 comments
Assignees
@theduckylittle
Labels
bug review
Milestone
2.8

Comments

@elil
Copy link
Member

elil commented Jun 29, 2015

While looking at #84, I ran into another issue.

Search PIN for 130220003076. You get one results and it zooms to 40.479, 4.343. Search for 130220003 you get two results and there is not a zoom to the wrong location.
@theduckylittle theduckylittle added this to the 2.8 milestone Jul 10, 2015
@theduckylittle theduckylittle self-assigned this Jul 10, 2015
theduckylittle pushed a commit to geomoose/geomoose-services that referenced this issue Jul 10, 2015
Fixed automatic zoom when data coordinates do not match map coordinat…
dacfa7e 
…es. refs: geomoose/geomoose#90

This is a multipart fix:
1. Coordinates were being projected back to the native dataset coordinate system which is not necessarily the mapping coordinates.
   They are now returned in WGS84/LatLon
2. GeoMOOSE was not allowing the user to specify a reprojection of extents in zoomToExtent (fixed in geomoose-js)
theduckylittle pushed a commit to geomoose/geomoose-js that referenced this issue Jul 10, 2015
Added extent reprojection to support query.php updates, refs: geomoos…
f085b87 
…e/geomoose#90
@theduckylittle
Copy link
Member

This was a projections problem. It's odd we only caught it now because the code was quite old. Here's what happened:

  1. When only returning one result we had a feature to zoom directly to that result. However, query.php was returning the coordinates to that result in the dataset's projection. This was causing the map to zoom to an incorrect extent when the mapping projection and the data's projection were different.
  2. GeoMOOSE.zoomToExtent did not support reprojection.

The fix:

  1. That seeded result is now returned in the EPSG:4326.
  2. zoomToExtent was updated to allow for projections to be specified.

theduckylittle pushed a commit that referenced this issue Jul 10, 2015
updated conf to test #90
a4b9d3f
@elil
Copy link
Member Author

elil commented Jul 10, 2015

Works correctly in the demo.

@elil elil closed this as completed Jul 10, 2015
theduckylittle pushed a commit to geomoose/geomoose-js that referenced this issue Dec 21, 2015
Fix for legend styling that was causing undesirale "STYLE=undefined" …
cc79eac 
…behaviour, refs: geomoose/geomoose#90
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@theduckylittle theduckylittle

Labels
bug review
Projects
None yet
Milestone
2.8
Development

No branches or pull requests
2 participants
@theduckylittle @elil