Understand client's views on backlog

[hdrdavies]

Here is the backlog as it stands:

Priority 2

-Convert the application to a native application -User should be able to upload photos [<---- we are able to have them modify the content of the slipway data, maybe this is preferable / more necessary?]

Priority 3

-Offer navigational tools to the user [<--- would this be for driving to the slipway?] -Offer additional search filters [<---- it seems we may have clarified this with the filtering page? Does this render this task unnecessary?]

Priority 4

-Links to useful resources like tide, surf and weather [<--- perhaps you could specify a little more what this would look like?] -Different markers to represent different types of slipway [<--- is this covered by the filtering page above?

Priority 5

-‘Flagging feature' for unavailable slipway [<--- do let us know if you feel this isn't necessary, as it didn't seem like it was something you were too worried about]

[Boatlaunch101]

1. A native application would be excellent. Modify slipway data more important than upload photos but uploading photos would be very cool given that you are standing at the slipway with a GPS enabled camera in your hand.
2. Navigational tools great if you can link into the Google directions. Additional search filter can be dropped
3. A link to the tide would be cool. We have the coordinates for all the UK Hydrographic Office tidal prediction points and we could link them to the PortID numbers, see below. http://www.ukho.gov.uk/easytide/EasyTide/ShowPrediction.aspx?PortID=0005&PredictionLength=7&DaylightSavingOffset=0&PrinterFriendly=True&HeightUnits=0 This would need a second set of pointers for tidal prediction points. Linking to surf etc is too complicated at this stage. Different markers to represent different slipways can be dropped.
4. Unavailable slipways can be dropped.

[hdrdavies]

@Boatlaunch101 Thanks for the feedback.

Would the tidal information pointers warrant a different marker to help differentiate from slipways?

If the tidal information could be displayed below the map along with the slipway, would this be preferable to a second set of markers?

[Boatlaunch101]

The tidal points are at different positions to the slipways so it would need a bit of logic to match them up. And in any case the closest tidal point to the slipway would not necessarily be to most appropriate. I think it would be simpler to programme and easier for the user to keep them separate.

The screen shot shows an example from the current Boatlaunch web site.

[Boatlaunch101]

I have downloaded an xml file with all the lat and long of the tidal points and the Port ID number if that is of any use to you. I don't see how to attach an XML file to the thread.

[hdrdavies]

@Boatlaunch101 try dragging the file into the comment box, sometimes that works.

Or- there is a 'selecting them' link at the bottom of the box

[Boatlaunch101]

This will not accept an xml file.

[hdrdavies]

Perhaps google drive would be the best way to share this

[Boatlaunch101]

I have put the data on Google Drive and sent the link to you Conor and Rory.