You can convert OSM XML to GeoJson with ogr2ogr. To convert to GeoJSON without getting the following error:
ERROR 6: GeoJSON driver doesn't support creating more than one layer
You can use one of the following commands or all of them:
ogr2ogr -f GeoJSON points.json data.osm.pbf points
ogr2ogr -f GeoJSON lines.json data.osm.pbf lines
ogr2ogr -f GeoJSON ...
Data needs to located in a geodatabase in order to export to XML. You can do this manually, or use the tool Export XML Workspace Document (Data Management). For the manual approach, simply right-click the featureclass or raster dataset within the file geodatabase > Export > XML Workspace Document.
Which then brings up the following GUI, where you can ...
Are the xml files *.aux.xml?
If so, it's not QGIS creating them, it's the GDAL library which uses them to store metadata, including statistics. You can disable completely by setting the environment variable GDAL_PAM_ENABLED=NO though I don't advise this if you'll be displaying the rasters again as there won't be any statistics cached.
Instead, you can ...
Your best bet is to use InkScape and convert your graphics to SVG. Polygons can be filled with rasters, but points and markers need SVG. If your symbol is available in a font, you can also use Font markers.
It's fairly straightforward:-
Load bitmap (png, jpg etc) into Inkscape with File > Open
File > Save as (use Plain SVG rather than default Inkscape SVG)
If you have ArcGIS and if you have also installed the Data Interoperability Extension (ArcGIS-integrated version of FME by Safe Software), you can read simple GML and WFS data sources without a license for the extension (source).
As long as your GML data sticks to the GML Simple Features profile, you do not need to enable the Data Interoperability Extension,...
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 ...
OSM2GEO - A JS Converter to convert OSM to GeoJSON
* OSM2GEO - OSM to GeoJSON converter
* OSM to GeoJSON converter takes in a .osm XML file as input and produces
* corresponding GeoJSON object.
* AUTHOR: P.Arunmozhi <>
* DATE : 26 / Nov / 2011
* LICENSE : WTFPL - Do What The F##% You Want To Public License
* LICENSE URL: http://sam.zoy.org/wtfpl/
For those who will stumble on this question like me..
It appears that the plugin has been generated (https://github.com/strk/mapnik/tree/2.3.x-pgraster) and has been merged in official Mapnik Repo.
The branch is 2.3.x (https://github.com/mapnik/mapnik/tree/2.3.x)
Now you can build Mapnik from the branch and use PGRaster plugin to use Raster data from ...
Here's what we've been doing to set up THREDDS Data Server (TDS) catalogs for regional oceanographic modeling providers in the US Integrated Ocean Observing System to serve their models results.
There are four basic types of catalogs we have been setting up:
A top level catalog that points to other catalogs that you want exposed
An "all" catalog that ...
Business rules vs data integrity rules
When you model your database, you specify the business logic in two spaces:
a. The data integrity rules. This includes among others having an integer column so users won't be able to enter strings.
b. The business domain rules. This includes having check/unique/foreign key constraints on columns so it won't be ...
The .xml file is the metadata file. An XML/metadata file is not a compulsory file needed to form shapefiles. The minimum files needed are:
.shp — shape format; the feature geometry itself
.shx — shape index format; a positional index of the feature geometry
to allow seeking forwards and backwards quickly
.dbf — attribute format; columnar ...
osmtogeojson is yet another OSM-to-GeoJSON converter, which has a few benefits when compared to this (OSM2GEO) or osm-and-geojson:
and nodejs) library.
proper multipolygon support
sophisticated polygon detection
stable (can cope with incomplete OSM data)
The library ...
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 ...
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 give the GDAL/OGR utility ogr2ogr a try. It has to capability to convert between many formats of vector spatial data.
OGR GML Driver Documentation
Depending on the flavor of your XML/GML it may be able to extract the spatial components straight away, and be as simple as:
ogr2ogr -f "esri shapefile" path\to\...
Before I try to answer, a tip. Your exception handler covers up the nature of the problem. Just let the original exception rise up and you'll have more information to share with people who are interested in helping you.
I like to use feedparser to parse Atom feeds. It does indeed give you dict-like objects. I submitted a patch to feedparser 4.1 to parse the ...
Instead of getting the dataset:
// Retrieve the first feature dataset from the workspace.
IEnumDatasetName enumDatasetName = workspace.get_DatasetNames
You can get the feature class by:
IEnumDatasetName enumDatasetName = workspace.get_DatasetNames(esriDatasetType.esriDTFeatureClass);
See this thread:
I enjoy using ElementTree. It's standardized in Python since 2.5 as xml.etree.ElementTree. Forgive me for being blunt, but you're using it wrong. I suggest trying the find, findtext, and findall methods when you know the structure of the data. Is Order your root element? If so,
>>> geography = rootElement.find('OrderRequest/SiteGeography')
Functions in rgdal read data into sp class objects, which can only contain one type of spatial object - a set of points, or lines, or polygons. The sf package provides classes for geometry vectors that can have different dimensions geometries within.
Using sf::st_read("file.kml") should return an object with a geometry column, and you can filter lines or ...
It looks to me like the server is trying to validate your XML request, and failing to find the XSD that contains the definition of GetRecords.
I think the EPSG sample is outdated for that server, because changing the CSW namespace to http://www.opengis.net/cat/csw/2.0.2 gets me some more errors about the Query element. Annex C of the EPSG API spec tells us ...
Updated: OSM Reader for FME 2013 (Beta)
=========================== BUILD 13082 20120417 ===========================
OSM reader: Updated to support reading very large datasets, for example
~764 million features on a European OSM dataset (PR#37345)
If you load the data into PostGIS, is there a column created for this category you mention? If so, you could use that attribute to specify the output shapefile name by setting the dynamic writer properties to use that attribute as the feature type name.
Another possibility is using something like imposm.parser and Python to parse the XML file and generate ...
If you are at 10.1, try using the Export XML Workspace Document (Data Management) geoprocessing tool.
I'm not sure exactly what it will do if you specify a feature class that participates in a relationship class, but I imagine it will include the relationship class and related object classes as well.
ArcGIS xml is not a valid data source for QGIS and so you can't import or export it. KML, a variety of xml, is. My thought is to use Python to parse your xml into kml(s) files. QGIS GDAL/OGR could convert that to whatever you like, for instance Spatialite or PostGIS.
First off, I have not tried using Config.esriaddinx for this purpose, but I wouldn't recommend it. It is meant for the configuration of the add-in itself, not necessarily user data, and you probably don't want to mix the two.
It has been a while since I've dealt with this myself so I may be a little fuzzy on the details, but there are multiple issues with ...
If you are comfortable with Python, you could use ElementTree to parse the XML and pyshp to create the shapefile.
Here is something you can start with:
from xml.etree import ElementTree
xml_file = 'input.xml'
shape_file = 'output.shp'
projection = 'GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298....