Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • startR startR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • startRstartR
  • Issues
  • #39
Closed
Open
Issue created Nov 08, 2019 by aho@ahoMaintainer

Start(): convention for lat/lon range

In Start(), to assign the region you want to load, you put the numbers (lon.min, lon,max, lat.min, and lat.max) in parameters latitude and longitude. For now, the range of the numbers is unclear, and it rarely returns error and warning when strange range is assigned (e.g., lon > 360).

The regulation should be found and written in the document. Also some warnings should be added in the code, so users can have a clear picture that what lat/lon range they actually load.

Assignee
Assign to
Time tracking