ISSUE-70: Add a requirement for avoiding coordinate transformations?

avoid coordinate transformations

Add a requirement for avoiding coordinate transformations?

State:
CLOSED
Product:
Use Cases and Requirements
Raised by:
Frans Knibbe
Opened on:
2016-07-25
Description:
A requirement that seems to follow from use case http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore is the wish to avoid having to perform coordinate transformation when data from different sources are combined.

This issue is for investigating the desirability of adding a requirement to the UCR document. It could be phrased like this:

"Guidance is needed for avoiding coordinate transformations when spatial data from multiple sources are combined"
Related Actions Items:
No related actions
Related emails:
  1. Re: UCR issue-76: a new requirement for multiple CRSs? (from frans.knibbe@geodan.nl on 2016-09-26)
  2. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-09-26)
  3. [Minutes F2F] 2016-09-19 (from phila@w3.org on 2016-09-20)
  4. Re: UCR issue-76: a new requirement for multiple CRSs? (from eparsons@google.com on 2016-09-14)
  5. RE: UCR issue-76: a new requirement for multiple CRSs? (from bcochrane@linz.govt.nz on 2016-09-14)
  6. Re: UCR issue-76: a new requirement for multiple CRSs? (from rob@metalinkage.com.au on 2016-09-13)
  7. Re: UCR issue-76: a new requirement for multiple CRSs? (from eparsons@google.com on 2016-09-13)
  8. Re: UCR issue-76: a new requirement for multiple CRSs? (from rob@metalinkage.com.au on 2016-09-13)
  9. RE: UCR issue-76: a new requirement for multiple CRSs? (from bcochrane@linz.govt.nz on 2016-09-13)
  10. Re: UCR issue-76: a new requirement for multiple CRSs? (from rob@metalinkage.com.au on 2016-09-12)
  11. Re: UCR issue-76: a new requirement for multiple CRSs? (from frans.knibbe@geodan.nl on 2016-09-12)
  12. Re: UCR issue-76: a new requirement for multiple CRSs? (from frans.knibbe@geodan.nl on 2016-09-12)
  13. Re: UCR issue-76: a new requirement for multiple CRSs? (from jlieberman@tumblingwalls.com on 2016-09-12)
  14. Re: UCR issue-76: a new requirement for multiple CRSs? (from rob@metalinkage.com.au on 2016-09-12)
  15. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from frans.knibbe@geodan.nl on 2016-09-09)
  16. UCR issue-76: a new requirement for multiple CRSs? (from frans.knibbe@geodan.nl on 2016-09-09)
  17. RE: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from bcochrane@linz.govt.nz on 2016-09-06)
  18. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from rob@metalinkage.com.au on 2016-09-05)
  19. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from raphael.troncy@eurecom.fr on 2016-09-05)
  20. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from frans.knibbe@geodan.nl on 2016-09-05)
  21. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from rob@metalinkage.com.au on 2016-09-05)
  22. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from frans.knibbe@geodan.nl on 2016-09-05)
  23. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from frans.knibbe@geodan.nl on 2016-09-05)
  24. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from rob@metalinkage.com.au on 2016-09-04)
  25. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? [SEC=UNCLASSIFIED] (from B.Bannerman@bom.gov.au on 2016-09-04)
  26. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from j.d.blower@reading.ac.uk on 2016-09-02)
  27. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-09-02)
  28. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from j.d.blower@reading.ac.uk on 2016-09-02)
  29. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-09-02)
  30. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-09-02)
  31. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from rob@metalinkage.com.au on 2016-09-01)
  32. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from jeremy.tandy@gmail.com on 2016-09-01)
  33. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from j.d.blower@reading.ac.uk on 2016-09-01)
  34. Re: Request for help: BP 9 "How to describe relative positions" (from j.d.blower@reading.ac.uk on 2016-09-01)
  35. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-08-31)
  36. [Minutes] 2016-08-17 (from phila@w3.org on 2016-08-17)
  37. sdw: agenda for meeting this week (from kerry.taylor@anu.edu.au on 2016-08-16)
  38. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from j.d.blower@reading.ac.uk on 2016-07-31)
  39. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-07-29)
  40. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from j.d.blower@reading.ac.uk on 2016-07-29)
  41. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-07-28)
  42. RE: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from chris.little@metoffice.gov.uk on 2016-07-26)
  43. Re: UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from j.d.blower@reading.ac.uk on 2016-07-25)
  44. UCR ISSUE-70: add a requirement for avoiding coordinate transformations? (from frans.knibbe@geodan.nl on 2016-07-25)
  45. Re: Wanted: feedback on UCR requirements (from frans.knibbe@geodan.nl on 2016-07-25)

Related notes:

No additional notes.

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 70.html,v 1.1 2018/10/09 10:08:16 carine Exp $