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.

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

KML Filter - filter reports by location (inefficient method) #97

Open
Nhorning opened this issue Apr 26, 2016 · 0 comments
Open

KML Filter - filter reports by location (inefficient method) #97

Nhorning opened this issue Apr 26, 2016 · 0 comments

Comments

@Nhorning
Copy link

Nhorning commented Apr 26, 2016

Both NepalMonitor.org and Quakemap.org used a plugin from @himalayantechies called KML filter.

This plugin can use a specially modified KML file to filter (and export with the use of it's sister plugin) reports by location. With Large numbers of reports and/or regions this method becomes inefficient, and is not recommended (we needed an emergency upgrade of the server) but I have placed it here for information, and because of it's state of completion, and because it conceivably be modified to do something else useful.

Instead - it is best to create a database of P-codes (DPA codes in Ecuador) for each report using existing GIS classifications. Please see the relevant issue: #87

Original Plugin: https://github.com/HTSolution/Ushahidi-plugin-kmlfilter

Heavily modified to work with p-code modificatoins: https://github.com/himalayantechies/Ushahidi_Web/tree/develop/plugins/kmlfilter

@Nhorning Nhorning changed the title KML Filter - (filter reports be location) KML Filter - filter reports by location (not recommended) Apr 26, 2016
@Nhorning Nhorning changed the title KML Filter - filter reports by location (not recommended) KML Filter - filter reports by location (inefficient method) Apr 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant