Skip to content

Geolife Ingest handling of bad coordinates#411

Merged
chrisbennight merged 1 commit intomasterfrom
GEOWAVE-53
May 30, 2015
Merged

Geolife Ingest handling of bad coordinates#411
chrisbennight merged 1 commit intomasterfrom
GEOWAVE-53

Conversation

@dcy2003
Copy link
Copy Markdown
Contributor

@dcy2003 dcy2003 commented May 28, 2015

Fix for #53

Geolife dataset contains a single coordinate (see below) that was causing wrap-around issues.

Finished analyzing 24876978 coordinates from the Geolife dataset
Total execution time: 29 seconds
Found 1 problematic coordinates:
latitude = 400.166666666667, longitude = 116.21539 (line 6782 of file C:\Users\yeagerdc\Desktop\Geolife Trajectories 1.3\Data\020\Trajectory\20110911000506.plt)

@coveralls
Copy link
Copy Markdown

coveralls commented May 28, 2015

Coverage Status

Coverage decreased (-0.02%) to 62.75% when pulling f033c52 on GEOWAVE-53 into 7d7525a on master.

chrisbennight added a commit that referenced this pull request May 30, 2015
@chrisbennight
Merge pull request #411 from ngageoint/GEOWAVE-53
9aaf541 
Geolife Ingest handling of bad coordinates
@chrisbennight chrisbennight merged commit 9aaf541 into master May 30, 2015
@chrisbennight chrisbennight deleted the GEOWAVE-53 branch May 30, 2015 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dcy2003 @coveralls @chrisbennight