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.
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
Update Recline to fix "Negative longitude numbers are parsed incorrectly" #138
Comments
Thanks, is this something that could be fixed upstream with Recline? |
Yes, what's the best way to do that? Just raise the issue on Recline? When do you pull updates to Recline? On 23 May 2014, at 15:49, Aaron Couch notifications@github.com wrote:
|
What version of recline are you currently using? How often do you update? |
Raised on recline here: datopian/datahub#429 |
Fantastic! I've updated the ticket title. Now we need to update Recline to see the fix. We just need to update the commit # we are pegged to: https://github.com/nuams/dkan/blob/7.x-1.x/dkan_dataset_dev.make#L185 . Can you test it locally and do a PR? |
Issue GetDKAN/dkan#138 update recline to fix negative lat/lon
I've created a pull request. |
Issue GetDKAN/dkan#138: Moving dkan_dataset.make modifications to dkan_...
+ changing git urls with https urls in order to travis to not fail during make
When importing a dataset for Lambeth, it was showing as points on the map way to the East. Recline.js was removing the "-" sign from the front of the longitude value, hence flipping the points across the zero dateline :)
Changing line 2463 from:
var dms = coord.split(/[^\.\d\w]+/);
to
var dms = coord.split(/[^-?\.\d\w]+/);
seemed to fix it.
The text was updated successfully, but these errors were encountered: