Git Product home page Git Product logo

nztides's People

Contributors

jevonlongdell avatar poussinou avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

nztides's Issues

Adding Maori names to the existing English names?

Given the recent prominent debates over the language of location names, what do you think about adding Maori names to the existing English names?

e.g.
Tamaki Makaurau/Auckland
Ōtautahi/Christchurch

I don't mind putting the time in to find the Maori names and making sure the macrons are correct.

New release?

It appears the data in the current release will expire at the end of this year.

LINZ copyright

Hi, I see in your source code there is info about the tide data "probably being under Crown Copyright". Under NZ GOAL, most NZ government data is now CC of some variety, mostly CC-BY 3.0 NZ. See here for LINZ data:
http://www.linz.govt.nz/linz-copyright

Oh, great software by the way, I use it all the time around Onehunga.

Cheers,

Robin

add tide data for secondary ports

The linz website provides methods to calculate tides at a number of other harbours, e.g. mahurangi, where I was boating this week. It'd be great to figure out the data and add to this app. I'm willing to assist with the calculations, would appreciate someone helping, by checking them afterwards

Make port easier to select

At the moment, selecting the correct port can be tricky for the following reasons, particularly if you frequently move around and require information at more than one port. We may add data for a lot more ports (see #6), making the problem worse:

  1. the list is long
  2. there are duplicate names in New Zealand (Waitangi in Chathams and Northland, French Bay in Auckland and elsewhere)
  3. it is organised alphabetically, which makes it clumsy if you want to know the tides at the nearest port (say you are at a location which is not listed and want the best guess by referring to the nearest port for which data exist) but are not sure which that is.

The objective of this issue is to list and choose the preferred method(s) for selecting/listing ports. These are some ideas, please add more as you see fit. Please also critique as you go.

  1. List the ports in one list, from North to South rather than alphabetically
  2. Add the latitude and longitude in the port names, e.g. "Auckland, -36.8416, 174.7657"
  3. Add the province to each port name, e.g. "Waitangi, Northland" (or "Northland, Waitangi")
  4. Add an option in the "settings" dialogue to only show either north or south island data
  5. Add an option in the "settings" dialogue to only show one province at a time.
  6. Create some way of interfacing with an internal/external map provider. This could be a plugin/list of favourites for OSMAnd, using webview to plot the ports on a map from OSM/LINZ within NZ Tides.
  7. your suggestion here

Complexity:
1., 2. and 3. are all relatively simple.
4. and 5. require a little more coding but may require combining with 1., 2., or 3
6. requires more coding and possibly requires the user to have another application installed (OSMAnd).

Usefulness:
1., 2., and 3. will mostly solve the problem
4. alone will not improve things dramatically
5. will solve part of the problem, but still requires some of 1., 2., or 3.
6. will assist with spatial recognition of locations (rather than processing somewhat abstract names/latitude and longitude) and is thus desirable for a lot of people

Data for 2017 and onwards?

According to my install, there is only data up to December 2016, which is ~7 weeks away. Could we get an upgrade for new data?

As an aside, I'm keen to include data for secondary ports (see #6) in the new release too, perhaps @jevonlongdell you could take a look at the comments to that issue and let me know what you think?

Cheers,

Robin

Add license information

When migrating from googlecode the license information has been lost. Could you add a note about GPLv3 to the readme and/or provider a COPYING/LICENSE file within the repo?

Update tide data

Perhaps a new release? The tide data is only until December 31st.

As an alternative, would it be useful in future, instead of updating the whole app, to merely download new data as it becomes available? That way we are not reliant on the availability of one person.

December January problems

* What steps will reproduce the problem?

Running NZ Tides in late December 2010

* What is the expected output? What do you see instead?

Tides for December 2010 followed by Jan 2011 is expected, instead Jan 2010 
tides were shown.

This is only an issue in for NZ Tides 0.1 in Decembers, proper operation will 
be restored Jan 1.

This problem is fixed in version 0.2, which can be downloaded from 
code.google.com and is available on the android market.




Original issue reported on code.google.com by [email protected] on 30 Dec 2010 at 7:12

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.