jpoeppel / isysur Goto Github PK

Talk About next meeting

Figure out how to import the relevant classes.

these tests cases are currently missing:
two polygons without overlab
two polygons with multiply overlabs

We added a test that shows the problem. Please fix :-)

Determine osmRequest Filter depending on SUR.

Figure out a smart way to choose between multiple nearest Objects (might be obsolete when request is smart enough).

Rule no 49 is really hard:

1. Given coords are far away from supposed polygon (truthKML)
2. There is no polygon in osm where the polygon is supposed to be, just a "gap" in between others, from which the polygon could be computed.

main for command line

Shorter line length!

try to port this function from bigger package

Adapt parsing and tests

Files may be deleted afterwards

Add polygons attribute to relation object. This should be filled whenever polygons are detected within the relation. Contains list of way ids that make up the polygon. Inner/outer does not need to be stored additionally.

Maybe we should change that today to make it more consistent with the other type checks?

The inputdata have to be parsed. The information of the relations of nodes will return a polygon, so it could be a placemark--object.

proposed by Thorsten: Throw exeption when invalid data (data points do not form a polygon)
interpretation: object is not a polygon when first and last nodes coordinates are different

Our program needs a name! It must be nice and fancy and absolut great! You think it's not necessary? Look into the documentation - here a name is necessary to address the program!

In the truth files, there is only one placemark (and the rule is nowhere mentioned in the outputkml)
however I like having the rule in the kml as well, but one could make the name contain all rules.

put your files concerning the gui into playground and make a little documentation how to use

If more than one sur is to be computed, create bounding box for all surs to only perform 1 request.

On that node: Maybe provide functions to create subsets of the osm data similar to osmrequests?

Read up on modules, unittests, osm data types, competition rules
Collect questions that remain uncertain in rules
Think up small building blocks that might be necessary

Rename kml file to kmlData and kml to kmlObject.

So far the name+.jpg is used as the image src. That should always be the case. Truth files use sur ID+.jpg -> change it to be the same.

That will be quite a hassle since we kinda have placemarks and surs seperated.

in OsmData provide these three functions. Optional with tag(s) argument.

For these we would like property "coord" in node, "vertices" in way. Consider how you could do that for the different types relations.

Return object or id

Keep pydocs up to date

Once list of tasks is created, assign responsible people.

Would like help from everyone!

Check what happens when a forest or other stuff is not completely in the bounding box.

Change the parseData test.
No file, just send a string!

Setup Python 2.7
coverage.py (https://pypi.python.org/pypi/coverage)
request.py (http://docs.python-requests.org/en/latest/)

Setuptools and distutils should do the trick, needs testing though, especially with our third party requirements.

What do we actually want to achieve, e.g. GUI yes/no, if yes what kind etc

make a photo and save the gps data
10 SURs are necessary but there is no upper border