Business Requirements for accurate web-mapping
Cameron Shorter <[email protected]>
| Newsgroups | gmane.comp.gis.proj-4.devel |
|---|---|
| Message-ID | <CABqeU+iqxxfCn4tvedQi-PMkVdFD4xoV-uYyiNU5+4wKOORT3Q@mail.gmail.com> |
To help with framing the problems and potential solutions we face with accurate web-mapping, I've endeavoured to capture the business requirements we are trying to solve. (The actual problems and potential solutions I'll be capturing separately). Comments and suggestions welcomed. Geospatial requirements: 1. Support high accuracy mapping. 2. Account for time dependence resulting from tectonic plate movement. 3. Provide accurate map alignment when displaying map layers from disparate sources. 4. Support calculation, publishing and application of accuracy metadata. 5. Datasets must have a nominated datum (reference frame) and epoch (date). Epoch is implicitly defined for a static datum and needs to be explicitly defined in a time-dependent datum. Usability requirements: 6. Datasets must be able to be transformed between datums. 7. Software applications shall continue to be responsive and performant for users, including for low-spec clients, such as browsers and mobile apps. 8. Web-mapping services shall continue to scale efficiently to support multiple users. 9. Users shall continue to be able to save map vector data as static files (such as KML, GML, GeoJSON), and render at a later point in time. 10. Accuracy information should be embedded in decision workflows. 11. Spatial expertise required to be learned by software implementers should be minimised. Software Implementation requirements: 12. Tiled web-mapping shall continue to be supported to address performance and scaling. In practice, this freezes maps in time. Derived CRS requirements: 13. Adopt a CRS, datum and projection for publishing map layers with the following characteristics: a. Defined accurately. b. Receives accurate transformations from key source CRSs (in particular, from national/regional datums). c. Based on a static, not dynamic, datum. d. Aligned with a fixed epoch (date). e. Applicable at global and local scales. f. Near-universally adopted within web-mapping contexts. -- Cameron Shorter Technology Demystifier Open Technologies and Geospatial Consultant M +61 (0) 419 142 254 _______________________________________________ PROJ mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/proj