Is that four in total per item ?. Feels like French danger zones where areas are published where cameras may be but not the location.
I suggest you put them in as twice so you get the start and end as a beep although it will beep in either direction you pass. That will be the ASC POI imports else you would have to remanuacture Ov2 or GPX files. ASC would be the best. That is like the example of the ten records in Post 1. The normal coordinate pair is switched as I've mentioned, so x,y is y,x for the ASC import. The third field in that list is the camera name but put in say "Camera" if it doesnt have a name and fill with, A, B, C as example.
If that doesn't work very well then just use one set of coordinates. Depends a lot on whether what you have are actually danger zones or just bracketed cameras where the bracket is 50 metres or so. Less than 50, one may do. You could get programmatic as an added touch once you work out what's going on and compute the distances and write out either two or one on the separation . Pythagoras.
I suggest you put them in as twice so you get the start and end as a beep although it will beep in either direction you pass. That will be the ASC POI imports else you would have to remanuacture Ov2 or GPX files. ASC would be the best. That is like the example of the ten records in Post 1. The normal coordinate pair is switched as I've mentioned, so x,y is y,x for the ASC import. The third field in that list is the camera name but put in say "Camera" if it doesnt have a name and fill with, A, B, C as example.
If that doesn't work very well then just use one set of coordinates. Depends a lot on whether what you have are actually danger zones or just bracketed cameras where the bracket is 50 metres or so. Less than 50, one may do. You could get programmatic as an added touch once you work out what's going on and compute the distances and write out either two or one on the separation . Pythagoras.
Last edited: