pep8 compliance, implementing raw_query

[mvexel]

This PR:

• changes public function names to lowercase
• adds a raw_query() public function for complete QL queries.
• removes the stub of a search() function (better implemented in the costom queries.)
• raises the OverpassException rather than exiting with a print statement.
• adds some docstrings.

[mharnold]

Never mind! I figured out 'function-names' is the branch.

[mharnold]

What I had in mind was just renaming _GetFromOverpass() to raw_get()

[mvexel]

I think the GeoJSON output is still relevant even if you want to perform a raw query.

[mharnold]

Then the caller would need to know to use a query that uses json response format and sets geom print option to avoid an exception during conversion to geoJSON. It seems simpler to me to have the geoJSON output option only on our higher level get() and leave the raw_get solely to users who want full unadorned access to the overpass API.

But maybe you have a use case in mind for a raw_get() with a geoJSON option?

Cheers, Michael spiderOSM.org

On Tue, Nov 25, 2014 at 8:54 PM, Martijn van Exel notifications@github.com wrote:

I think the GeoJSON output is still relevant even if you want to perform a raw query.

— Reply to this email directly or view it on GitHub https://github.com/mvexel/overpass-api-python-wrapper/pull/24#issuecomment-64514979 .

[mvexel]

Not really - I think you are right, there is no need to have asGeoJSON in the raw query.

BTW here is the script I was talking about, using this wrapper to connect Overpass and MapRoulette.

[mharnold]

Very cool! I have an application in mind but it would require map roulette to serve up challenges near the users currrent location. Not sure this is currently possible in maproulette?

My application: have users resolve name mismatches between OSM and jurisdictional data by survey (checking out street signs at the location.) See: http://names.mhaprojects.com/about.html