You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to provide a redirection mechanism for the different types of geometries that we can find in geospatial applications. So that if an app wants KML we provide it, if they want RDF/XML, we provide taht. I think of something like:
XXX hasgeometry geomIDXXX
And then when you go into geomIDXXX you may ask for mime types RDF/XML and serve the RDF representation, or GML and serve the GML representation, etc. Also taking into account scales, as per my previously submitted issue.
The text was updated successfully, but these errors were encountered:
We need to provide a redirection mechanism for the different types of geometries that we can find in geospatial applications. So that if an app wants KML we provide it, if they want RDF/XML, we provide taht. I think of something like:
XXX hasgeometry geomIDXXX
And then when you go into geomIDXXX you may ask for mime types RDF/XML and serve the RDF representation, or GML and serve the GML representation, etc. Also taking into account scales, as per my previously submitted issue.
The text was updated successfully, but these errors were encountered: