You want urn:ogc:def:crs:EPSG::26912 from the GML link on spatialreference.org. GML uses the URN syntax for describing coordinate systems.
Alternatively, you could specify
Yes, srsName="EPSG:abcd" is GML-3 compliant but only in an application context where EPSG:abcd points to a CRS definition. As of 2013, OGC best practice (documented here) is to use http URIs of the form http://www.opengis.net/def/crs/EPSG/0/4326.
The GML-3.0.0 spec (OCG 02-023r4) section v.2, page xiv states aliasing CRSs is kosher:
in GML we have found ...
The official OGC “Well-known Text Representation of Spatial Reference Systems” for EPSG 4326 (http://spatialreference.org/ref/epsg/4326/ogcwkt/) is (your second projection):
You've caught a lot of the differences. Esri never adopted the WKIDs for the map projection algorithms or parameter names so those are all different. We didn't agree with how carefully defined the parameter definitions are. Ours are more generalized.
We don't support TOWGS84 nor some of the newer keywords.
When we compare strings (names), we ignore the ...
QGIS has a plugin that supports WPS 1.0.0. Just search for "WPS" in the plugin installer.
Open the plugin install, click on the Repositories, click Add 3rd party repositories and then click back on the Plugins tab.
Note: I can't tell you much about it as I have never had a use case for it.
From W3C's Extensible Markup Language (XML) 1.0 (Fifth Edition) recommendation:
[Definition: The XML document type declaration contains or points to markup declarations that provide a grammar for a class of documents. This grammar is known as a document type definition, or DTD. The document type declaration can point to an external subset (a special kind ...
No, GeoJSON is not an OGC standard:
IETF Geographic JSON Working Group
The Internet Engineering Task Force, in conjunction with the original specification authors, has formed the Geographic JSON WG to standardize the format. Work continues on GitHub at https://github.com/geojson/draft-geojson.
Polygons are not simple to handle and there are more than two worlds. I recommend to read this article "About Invalid, Valid and Clean Polygons" http://www.springer.com/%3FSGWID%3D5-102-45-124048-p32597622
The GeoJSON specification https://tools.ietf.org/html/rfc7946 says that "GeoJSON comprises the seven concrete geometry types defined in the OpenGIS ...
Every XML document essentially has some given structure. When the structure is formally specified, we usually talk about a given XML grammar.
The formal specification can take many forms, e. g. DTD (Document Type Definition) or XML Schema Definition (XSD). XSD itself is a XML document and is now being used for GML. There are also other means of specifying ...
I don't have such a list, but going through the GDAL code will guide you:
As @PolyGeo suggested, I am converting my comments into an answer. The answer is split into three parts to broadly reflect the three comments I made.
Roy Fielding's dissertation that described Representational State Transfer (REST) amongst other architectural styles Architectural Styles and
the Design of Network-based Software Architectures was ...
GeoNetwork Opensource and the Esri Geoportal Server are two open source and free technologies that can be used to build Catalog Services for spatial information, and are both a great start.
However, I think both could do with more work on usability.
For example, Catalog Services from the Esri Geoportal Server can be accessed from ArcGIS for Desktop to ...
If you are working with geometry types beyond the usual point/line/polygon/collection or are working with more than 2 dimensions, then yes, get the ISO spec. Otherwise, no. Also get the old OGC guidance on WKB for higher dimensions (or read the PostGIS doc) in case you're worried about maximum interoperability. (For 2d and simple geometries the new ISO stuff ...
Looks like you have a self-intersection, which SQL Server no likey. I'm surprised it even got loaded into the database in the first place. Try running MakeValid() and see what it does to the shape. You don't have to test it on the original data, just make a new one on the fly in Management Studio.
What's interesting is that SQL Server will plot it:
But it ...
When someone designs a class of XML documents for representing information in a particular domain, they will sometimes call this an XML grammar, or a vocabulary, or a schema, or a document type, or even a language. The terminology isn't consistent. There's perhaps a different emphasis: calling it a schema implies that an XML Schema is the primary way in ...
You could try an OGC Web Map Context (WMC) file.
Certainly there is a WMC client extension to add WMC support to ArcGIS Desktop.
The purpose of the WMC file is to bundle together web services (such as, but not limited to, ArcGIS services), such that you can share maps composed of Web Map Services to aware clients...
For example the following WMC of the ...
i think you should use WCS instead of WMS for sharing raster datasets on the Web. AFAIK, wms dont have this capabilities for sharing tiff images.
Unlike OGC Web Map Service (WMS), which portrays spatial data to
return static maps (rendered as pictures by the server), the Web
Coverage Service provides available data together with their ...
Normally on each OS QGIS will install the settings in a different location, however there is a switch you can start QGIS with to redirect these settings.
When you start QGIS you can start it with the --optionspath and --configpath switches which you can point to a different location.
QGIS will now create all the settings in a ini format and move the .qgis2 ...
The QGIS client plugin is a good one - I was able to access the features of WFS without issue.
ArcGIS has an interoperability connections feature that must be enabled by a user with administrator access first however I didn't try to get this working as the license is 2.5K and I don't have that license
OpenLayers supports WFS as does GRASS - I found that ...
The Open Geospatial Consortium (OGC) exists to define interface standards such as the Web Mapping Service (WMS) standard, or Web Feature Service (WFS) standard. These are standards that define how programmers should create software to provide such a service.
So for example, OGC defines the WMS standard, programmers write a piece of software called ...
dimension(): refers to the topological dimension (i.e. point/line/area)
coordinateDimension(): returns the dimension of the tuple as given (as statet in the OP)
spatialDimension(): returns the dimension of the tuple without the measurement part (with "M" being the measurement in a linear reference system)
As it's pretty obvious for a 2D or "4D" literal, you ...
If by OGC services you mean WMS and WFS then you could use GeoServers REST configuration API, which lets you create workspaces, stores, styles, upload shapefiles etc.
You can see a list of operations here:
REST Configuration API Reference
GeoServer have examples of how to do this in cURL:
GeoServer cURL REST examples
I don't know much Java, but I am ...
It's CSW. Look here for more information about it than is healthy for one person to read.
Funnily enough in the spec, the abbreviations section has:
CSW Catalogue Service-Web
So I can see where the hyphenated version comes from, but I've not noticed it in any official documentation.
This question has been converted to Community Wiki and wiki locked
because it is an example of a question that seeks a list of answers
and appears to be popular enough to protect it from closure. It
should be treated as a special case and should not be viewed as the
type of question that is encouraged on this, or any Stack Exchange
site, but if ...
This following one is correct:
as defined by the following portion of the schema definition for version 1.0.0
<xsd:element name="Service" type="wfs:ServiceType"/>
Take a look at 12.3.3 Service section in the Web Feature Service Implementation Specification (OGC 02-058)
WCS is the less-used of the WMS/WFS/WCS triangle so there isn't as much out there as you've probably noticed.
However, making requests is really really easy and you don't really need a special library. Arguably its the easiest of the three from a users perspective because you get a nice simple file back.
A valid request looks something like this:
Really not a definitive answer but an answer to complete more (waiting community :) !
The main ideas why SLD is not used everywhere as a data exchange is history, verbosity, extensibility, output support.
ArcGIS comes before the SLD standard exists.
MapInfo format doesn't separate style from content so you can't separate data from rendering like ...