Spatial and temporal filtering on tracks

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Spatial and temporal filtering on tracks

staschc
Hi,

is there any documentation about spatial and temporal filtering of tracks/measurements available beyond the closed GitHub issues for spatial [1] and temporal filtering [2]?

If a bbox filter for tracks is specified, are the full tracks returned that intersect the bounding box, i.e. could start and end points be outside the bbox? Or are the tracks clipped to the bbox? Or are only tracks returned that fall completely within the bbox?

Cheers,

Christoph

[1] https://github.com/enviroCar/enviroCar-server/issues/37
[2] https://github.com/enviroCar/enviroCar-server/issues/94
Reply | Threaded
Open this post in threaded view
|

Re: Spatial and temporal filtering on tracks

Daniel Nüst
Am 04.12.2013 15:04, schrieb staschc:
> is there any documentation about spatial and temporal filtering of
> tracks/measurements available beyond the closed GitHub issues for spatial
> [1] and temporal filtering [2]?

For temporal filtering, the issue you mention is the best available
documentation.

For bbox filtering the documentation is a bit hidden on the page [3].

"In addition to the standard query parameters, tracks can be queried by
a given boundingbox. Therefore you have to add the following get
parameter: bbox=minx,miny,maxx,maxy. (example:
/rest/tracks?bbox=7.0,51.1,7.3,52.0)"

> If a bbox filter for tracks is specified, are the full tracks returned that
> intersect the bounding box, i.e. could start and end points be outside the
> bbox? Or are the tracks clipped to the bbox? Or are only tracks returned
> that fall completely within the bbox?

<Matthes>If (only one) a feature of a track falls within the bounding
box then you get back the full track.</Matthes>

Hope this helps :-)

/Daniel

> [1] https://github.com/enviroCar/enviroCar-server/issues/37
> [2] https://github.com/enviroCar/enviroCar-server/issues/94
[3] http://envirocar.github.io/enviroCar-server/api/tracks

--
Daniel Nüst
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
Fon: +49-(0)-251–396371-36
Fax: +49-(0)-251–396371-11

http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
enviroCar-discuss mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/envirocar-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Spatial and temporal filtering on tracks

staschc
Thanks, Daniel - this helps. One more question:

> <Matthes>If (only one) a feature of a track falls within the bounding box then you get back the full track.</Matthes>

Is this also the default behavior for the temporal filter? While playing around with the server and temporal filters, it seems like, all points in the track have to match the temporal filter.

Cheers,

Christoph

-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Daniel Nüst
Gesendet: Mittwoch, 4. Dezember 2013 15:14
An: [hidden email]
Betreff: Re: [enviroCar-discuss] Spatial and temporal filtering on tracks

Am 04.12.2013 15:04, schrieb staschc:
> is there any documentation about spatial and temporal filtering of
> tracks/measurements available beyond the closed GitHub issues for
> spatial [1] and temporal filtering [2]?

For temporal filtering, the issue you mention is the best available documentation.

For bbox filtering the documentation is a bit hidden on the page [3].

"In addition to the standard query parameters, tracks can be queried by a given boundingbox. Therefore you have to add the following get
parameter: bbox=minx,miny,maxx,maxy. (example:
/rest/tracks?bbox=7.0,51.1,7.3,52.0)"

> If a bbox filter for tracks is specified, are the full tracks returned
> that intersect the bounding box, i.e. could start and end points be
> outside the bbox? Or are the tracks clipped to the bbox? Or are only
> tracks returned that fall completely within the bbox?

<Matthes>If (only one) a feature of a track falls within the bounding box then you get back the full track.</Matthes>

Hope this helps :-)

/Daniel

> [1] https://github.com/enviroCar/enviroCar-server/issues/37
> [2] https://github.com/enviroCar/enviroCar-server/issues/94
[3] http://envirocar.github.io/enviroCar-server/api/tracks

--
Daniel Nüst
52°North Initiative for Geospatial Open Source Software GmbH Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
Fon: +49-(0)-251–396371-36
Fax: +49-(0)-251–396371-11

http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk Local Court Muenster HRB 10849 _______________________________________________
enviroCar-discuss mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/envirocar-discuss
_______________________________________________
enviroCar-discuss mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/envirocar-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Spatial and temporal filtering on tracks

Christian Autermann-2
Hey Christoph,

the temporal filtering behavior is different. The track is treated as
an interval lasting from the first till the last measurement and the
filter is applied to that interval…

--Christian


On Wed, Dec 4, 2013 at 3:32 PM, Stasch, Christoph
<[hidden email]> wrote:

> Thanks, Daniel - this helps. One more question:
>
>> <Matthes>If (only one) a feature of a track falls within the bounding box then you get back the full track.</Matthes>
>
> Is this also the default behavior for the temporal filter? While playing around with the server and temporal filters, it seems like, all points in the track have to match the temporal filter.
>
> Cheers,
>
> Christoph
>
> -----Ursprüngliche Nachricht-----
> Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Daniel Nüst
> Gesendet: Mittwoch, 4. Dezember 2013 15:14
> An: [hidden email]
> Betreff: Re: [enviroCar-discuss] Spatial and temporal filtering on tracks
>
> Am 04.12.2013 15:04, schrieb staschc:
>> is there any documentation about spatial and temporal filtering of
>> tracks/measurements available beyond the closed GitHub issues for
>> spatial [1] and temporal filtering [2]?
>
> For temporal filtering, the issue you mention is the best available documentation.
>
> For bbox filtering the documentation is a bit hidden on the page [3].
>
> "In addition to the standard query parameters, tracks can be queried by a given boundingbox. Therefore you have to add the following get
> parameter: bbox=minx,miny,maxx,maxy. (example:
> /rest/tracks?bbox=7.0,51.1,7.3,52.0)"
>
>> If a bbox filter for tracks is specified, are the full tracks returned
>> that intersect the bounding box, i.e. could start and end points be
>> outside the bbox? Or are the tracks clipped to the bbox? Or are only
>> tracks returned that fall completely within the bbox?
>
> <Matthes>If (only one) a feature of a track falls within the bounding box then you get back the full track.</Matthes>
>
> Hope this helps :-)
>
> /Daniel
>
>> [1] https://github.com/enviroCar/enviroCar-server/issues/37
>> [2] https://github.com/enviroCar/enviroCar-server/issues/94
> [3] http://envirocar.github.io/enviroCar-server/api/tracks
>
> --
> Daniel Nüst
> 52°North Initiative for Geospatial Open Source Software GmbH Martin-Luther-King-Weg 24
> 48155 Münster, Germany
> E-Mail: [hidden email]
> Fon: +49-(0)-251–396371-36
> Fax: +49-(0)-251–396371-11
>
> http://52north.org/
> Twitter: @FiveTwoN
>
> General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk Local Court Muenster HRB 10849 _______________________________________________
> enviroCar-discuss mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/envirocar-discuss
> _______________________________________________
> enviroCar-discuss mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/envirocar-discuss
_______________________________________________
enviroCar-discuss mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/envirocar-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Spatial and temporal filtering on tracks

staschc
OK, thanks, question is answered.

Cheers,

Christoph

-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Christian Autermann
Gesendet: Mittwoch, 4. Dezember 2013 16:20
An: [hidden email]
Betreff: Re: [enviroCar-discuss] Spatial and temporal filtering on tracks

Hey Christoph,

the temporal filtering behavior is different. The track is treated as an interval lasting from the first till the last measurement and the filter is applied to that interval…

--Christian


On Wed, Dec 4, 2013 at 3:32 PM, Stasch, Christoph <[hidden email]> wrote:

> Thanks, Daniel - this helps. One more question:
>
>> <Matthes>If (only one) a feature of a track falls within the bounding
>> box then you get back the full track.</Matthes>
>
> Is this also the default behavior for the temporal filter? While playing around with the server and temporal filters, it seems like, all points in the track have to match the temporal filter.
>
> Cheers,
>
> Christoph
>
> -----Ursprüngliche Nachricht-----
> Von: [hidden email]
> [mailto:[hidden email]] Im Auftrag von Daniel
> Nüst
> Gesendet: Mittwoch, 4. Dezember 2013 15:14
> An: [hidden email]
> Betreff: Re: [enviroCar-discuss] Spatial and temporal filtering on
> tracks
>
> Am 04.12.2013 15:04, schrieb staschc:
>> is there any documentation about spatial and temporal filtering of
>> tracks/measurements available beyond the closed GitHub issues for
>> spatial [1] and temporal filtering [2]?
>
> For temporal filtering, the issue you mention is the best available documentation.
>
> For bbox filtering the documentation is a bit hidden on the page [3].
>
> "In addition to the standard query parameters, tracks can be queried
> by a given boundingbox. Therefore you have to add the following get
> parameter: bbox=minx,miny,maxx,maxy. (example:
> /rest/tracks?bbox=7.0,51.1,7.3,52.0)"
>
>> If a bbox filter for tracks is specified, are the full tracks
>> returned that intersect the bounding box, i.e. could start and end
>> points be outside the bbox? Or are the tracks clipped to the bbox? Or
>> are only tracks returned that fall completely within the bbox?
>
> <Matthes>If (only one) a feature of a track falls within the bounding
> box then you get back the full track.</Matthes>
>
> Hope this helps :-)
>
> /Daniel
>
>> [1] https://github.com/enviroCar/enviroCar-server/issues/37
>> [2] https://github.com/enviroCar/enviroCar-server/issues/94
> [3] http://envirocar.github.io/enviroCar-server/api/tracks
>
> --
> Daniel Nüst
> 52°North Initiative for Geospatial Open Source Software GmbH
> Martin-Luther-King-Weg 24
> 48155 Münster, Germany
> E-Mail: [hidden email]
> Fon: +49-(0)-251–396371-36
> Fax: +49-(0)-251–396371-11
>
> http://52north.org/
> Twitter: @FiveTwoN
>
> General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk Local Court
> Muenster HRB 10849 _______________________________________________
> enviroCar-discuss mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/envirocar-discuss
> _______________________________________________
> enviroCar-discuss mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/envirocar-discuss
_______________________________________________
enviroCar-discuss mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/envirocar-discuss
_______________________________________________
enviroCar-discuss mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/envirocar-discuss