RE: Focus week: Maps for HTML / MapML

Hi Jeremy,

> On the subject of CRS negotiation, we identified this as a gap in the original best practice document. Have you checked in with @MichaelGordon to see if this gap is getting picked in his work stream?

So as yet, the MapML client doesn't support this concept, but I think it *could*.  Maybe its too early to present MapML as a best practice coverage for this, but I think it would be pretty cool and potentially useful.  These things sometimes seem that they might be simpler than they actually end up being, though.

> Also, it may be worth your while linking in to the W3C DXWG who are (were?) investigating ‘profile-based content negotiation’ - which conceivably could be extended to cover CRS.

I am reading now; if it seems worthwhile I will follow up with the DXWG.

> I recommend that you create an issue covering this particular topic and flag it with both “bp” and “mapml” labels, then put this on the Kanban board for your project https://github.com/w3c/sdw/projects/10


I’ve done that, thank you.

Thanks,
Peter


Peter Rushforth

Technology Advisor
Canada Centre for Mapping and Earth Observation / Earth Sciences Sector
Natural Resources Canada / Government of Canada
mailto:peter.rushforth@canada.ca / Tel: 613-759-7915

Conseiller technique
Centre canadien de cartographie et d’observation de la Terre / Secteur des sciences de la Terre
Ressources naturelles Canada / Gouvernement du Canada
mailto:peter.rushforth@canada.ca / Tél: 613-759-7915

From: Jeremy Tandy <jeremy.tandy@gmail.com> 
Sent: July 9, 2018 9:50 AM
To: Rushforth, Peter (NRCan/RNCan) <peter.rushforth@canada.ca>
Cc: public-maps4html@w3.org; public-sdwig@w3.org; testbed-14-mapml@lists.opengeospatial.org
Subject: Re: Focus week: Maps for HTML / MapML

Hi Peter - did you get any follow up to your request for assistance?

> One issue in particular was brought to my attention by https://github.com/w3c/sdw/issues/757 , which we may be able to collaborate on here, is CRS negotiation. I think the MapML client could readily be extended to find links to alternate CRS which it could automatically follow in the case that the CRS of the resource did not match its needs. https://github.com/w3c/sdw/projects/10#card-11043572


On the subject of CRS negotiation, we identified this as a gap in the original best practice document. Have you checked in with @MichaelGordon to see if this gap is getting picked in his work stream? Also, it may be worth your while linking in to the W3C DXWG who are (were?) investigating ‘profile-based content negotiation’ - which conceivably could be extended to cover CRS.

I recommend that you create an issue covering this particular topic and flag it with both “bp” and “mapml” labels, then put this on the Kanban board for your project https://github.com/w3c/sdw/projects/10


Jeremy 

On Tue, 3 Jul 2018 at 14:29, Rushforth, Peter (NRCan/RNCan) <mailto:peter.rushforth@canada.ca> wrote:
Hello SDWIGers (and others!),
 
Per Linda and Jeremy’s reminder, I would like to direct your attention to the project I created under this group’s project list: https://github.com/w3c/sdw/projects/10 
 
In terms of progress, we continue to work on MapML in Testbed 14, and to that end the OGC kindly accepted to make the MapML Testbed 14 Engineering Report repo public.  
 
Many of the links in the above project refer to issues in the ER repo which are being discussed and worked on in the testbed.
 
The main focus areas of the testbed participants are:
 
•         Developing a Progressive Web App using the Web-Map-Custom-Element and various MapML sources (GMU).
•         Continued discussion of MapML features, with concomitant development of server (CubeWerx, NRCan) and client (NRCAN) .
 
Most (all?) of the features in development are pointed to by the project or the issues in the ER repo.
 
I hope you will have a look and contribute where you can!
 
One issue in particular was brought to my attention by https://github.com/w3c/sdw/issues/757 , which we may be able to collaborate on here, is CRS negotiation.  I think the MapML client could readily be extended to find links to alternate CRS which it could automatically follow in the case that the CRS of the resource did not match its needs. https://github.com/w3c/sdw/projects/10#card-11043572 
 
Finally, please let me know if there are missing touchstones of collaboration / open source-ness for this effort, as sometimes it is easy to overlook something that may be obvious to others.
 
Cheers,
Peter
 
 
Peter Rushforth
 
Technology Advisor
Canada Centre for Mapping and Earth Observation / Earth Sciences Sector
Natural Resources Canada / Government of Canada
mailto:peter.rushforth@canada.ca / Tel: 613-759-7915
 
Conseiller technique
Centre canadien de cartographie et d’observation de la Terre / Secteur des sciences de la Terre
Ressources naturelles Canada / Gouvernement du Canada
mailto:peter.rushforth@canada.ca / Tél: 613-759-7915

Received on Tuesday, 10 July 2018 13:54:12 UTC