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

Convex poly #17

Merged
merged 48 commits into from
Sep 17, 2021
Merged

Convex poly #17

merged 48 commits into from
Sep 17, 2021

Conversation

LdDl
Copy link
Owner

@LdDl LdDl commented Aug 27, 2021

Start working on #16
Current PR targeted for convex polygon

@LdDl LdDl added the enhancement New feature or request label Aug 27, 2021
@LdDl LdDl self-assigned this Aug 27, 2021
@LdDl
Copy link
Owner Author

LdDl commented Aug 27, 2021

Inital job is done:

  1. Constructor for polygon
  2. Scaling function
  3. Determine if point is inside of polygon of CONVEX type

Next:

  • Choose best place in JSON configuration for user defined polygons
  • Euclidean <-> WGS84 conversion (for speed estimation, but I'm not sure if we need it now)
  • Determine if point has entered polygon
  • Determine if point has left polygon
  • Pick a way to store information about polygons and detected objects relations (which detected objects are inside of certain polygons)
  • Time estimation

@LdDl
Copy link
Owner Author

LdDl commented Aug 28, 2021

20.08.2021 14:35:00+00:00 UTC
Done:

  • Determine if point (detected object) has entered polygon
  • Determine if point (detected object) has left polygon

Next:

  • Choose best place in JSON configuration for user defined polygons
  • Euclidean <-> WGS84 conversion (for speed estimation, but I'm not sure if we need it now)
  • Pick a way to store information about polygons and detected objects relations (which detected objects are inside of certain polygons)
  • Time estimation

@LdDl
Copy link
Owner Author

LdDl commented Aug 28, 2021

Added some test for convex polygons

@LdDl
Copy link
Owner Author

LdDl commented Aug 30, 2021

30.08.2021 17:32:00+00:00 UTC
Done:

  • Choose best place in JSON configuration for user defined polygons
  • Pick a way to store information about polygons and detected objects relations (which detected objects are inside of certain polygons)
  • Drawing polygons (as connected polylines)

Next:

  • Euclidean <-> WGS84 conversion (for speed estimation, but I'm not sure if we need it now)
  • Time estimation
  • Store information about visited polygons in detected object

@LdDl
Copy link
Owner Author

LdDl commented Sep 17, 2021

I think we will make below features not in this pull request but in future ones:

  • Euclidean <-> WGS84 conversion (for speed estimation, but I'm not sure if we need it now)
  • Time estimation
  • Store information about visited polygons in detected object

Also we think it's time to go further and implement event system for both virutal line and virtual polygon.
On top of that it will be good to have Pub/Sub system also.

@LdDl LdDl merged commit 0849577 into master Sep 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant