GIS2DJI is a Python 3 program created to exports GIS files to a simple kml compatible with DJI pilot. The software is provided with a GUI. GIS2DJI has been tested with the following file formats: gpkg, shp, mif, tab, geojson, gml, kml and kmz. GIS_2_DJI will scan every file, every layer and every geometry collection (ie: MultiPoints) and create one output kml or kmz for each object found. It will import points, lines and polygons, and converted each object into a compatible DJI kml file. Lines and polygons will be exported as kml files. Points will be converted as PseudoPoints.kml. A PseudoPoints fools DJI to import a point as it thinks it's a line with 0 length. This allows you to import points in mapping missions. Points will also be exported as Point.kmz because PseudoPoints are not visible in a GIS or in Google Earth. The .kmz file format should make points compatible with some DJI mission software.

https://www.openstreetmap.org/images/osm_logo.png" alt="" /> OpenStreetMap (openstreetmap.org) is a global collaborative mapping project, which offers maps and map data released with an open license, encouraging free re-use and re-distribution. The data is created by a large community of volunteers who use a variety of simple on-the-ground surveying techniques, and wiki-syle editing tools to collaborate as they create the maps, in a process which is open to everyone. The project originated in London, and an active community of mappers and developers are based here. Mapping work in London is ongoing (and you can help!) but the coverage is already good enough for many uses.

Browse the map of London on OpenStreetMap.org

Downloads:

The whole of England updated daily:

• england.osm.bz2 ~185M - .osm formatted raw XML data (compressed)
• england.shp.zip ~156M - ESRI shapefiles

For more details of downloads available from OpenStreetMap, including downloading the whole planet, see 'planet.osm' on the wiki.

Data access APIs:

Download small areas of the map by bounding-box. For example this URL requests the data around Trafalgar Square:
http://api.openstreetmap.org/api/0.6/map?bbox=-0.13062,51.5065,-0.12557,51.50969

Data filtered by "tag". For example this URL returns all elements in London tagged shop=supermarket:
http://www.informationfreeway.org/api/0.6/*[shop=supermarket][bbox=-0.48,51.30,0.21,51.70]

The .osm format

The format of the data is a raw XML represention of all the elements making up the map. OpenStreetMap is composed of interconnected "nodes" and "ways" (and sometimes "relations") each with a set of name=value pairs called "tags". These classify and describe properties of the elements, and ultimately influence how they get drawn on the map. To understand more about tags, and different ways of working with this data format refer to the following pages on the OpenStreetMap wiki.

• .osm - About the raw XML data format of OpenStreetMap
• Downloading data - More details of the API and extract download options
• Xapi - The extended api for filtering by tag
• Map Features - A list of tags, and what map features they represent
• Converting map data between formats - catalogue of tools for converting from .osm to other formats

Simple embedded maps

Rather than working with raw map data, you may prefer to embed maps from OpenStreetMap on your website with a simple bit of javascript. You can also present overlays of other data, in a manner very similar to working with google maps. In fact you can even use the google maps API to do this. See OSM on your own website for details and links to various javascript map libraries.

Help build the map!

The OpenStreetMap project aims to attract large numbers of contributors who all chip in a little bit to help build the map. Although the map editing tools take a little while to learn, they are designed to be as simple as possible, so that everyone can get involved. This project offers an exciting means of allowing local London communities to take ownership of their part of the map.

Read about how to Get Involved and see the London page for details of OpenStreetMap community events.

Replication code and data for the paper "Satellite observations reveal inequalities in the progress and effectiveness of recent electrification in sub-Saharan Africa" published in One Earth (DOI: 10.1016/j.oneear.2020.03.007)

This repository hosts:

A JavaScript file to process remotely-sensed data into Google Earth Engine (step 1)

A R script, to be run after the successful completion of the Google Earth Engine processing (step 2)

Supporting files to run the analysis (e.g. a shapefile of provinces, validation data, etc.)

Create a Google account, if you do not have one, and require access to Earth Engine https://signup.earthengine.google.com.

Make sure your Google Drive has enough cloud storage space available.

Clone the repository.

Run the JavaScript file in Google Earth Engine and wait that the data processing is complete (can take >24 hours)

Run the R script, which will reproduce the analysis and the figures contained in the paper.

Open the QGIS project files to replicate maps with the appropriate layout.

Source code-related issues should be opened directly on GitHub. Broader questions of the methods should be addressed to giacomo.falchetta@feem.it

The National Flood Hazard Layer (NFHL) is a geospatial database that contains current effective flood hazard data. FEMA provides the flood hazard data to support the National Flood Insurance Program. You can use the information to better understand your level of flood risk and type of flooding.The NFHL is made from effective flood maps and Letters of Map Change (LOMC) delivered to communities. NFHL digital data covers over 90 percent of the U.S. population. New and revised data is being added continuously. If you need information for areas not covered by the NFHL data, there may be other FEMA products which provide coverage for those areas.In the NFHL Viewer, you can use the address search or map navigation to locate an area of interest and the NFHL Print Tool to download and print a full Flood Insurance Rate Map (FIRM) or FIRMette (a smaller, printable version of a FIRM) where modernized data exists. Technical GIS users can also utilize a series of dedicated GIS web services that allow the NFHL database to be incorporated into websites and GIS applications. For more information on available services, go to the NFHL GIS Services User Guide.You can also use the address search on the FEMA Flood Map Service Center (MSC) to view the NFHL data or download a FIRMette. Using the “Search All Products” on the MSC, you can download the NFHL data for a County or State in a GIS file format. This data can be used in most GIS applications to perform spatial analyses and for integration into custom maps and reports. To do so, you will need GIS or mapping software that can read data in shapefile format.FEMA also offers a download of a KMZ (keyhole markup file zipped) file, which overlays the data in Google Earth™. For more information on using the data in Google Earth™, please see Using the National Flood Hazard Layer Web Map Service (WMS) in Google Earth™.

The GIS Web Mapping Application is design to have the look and feel as Google Earth. The primary functionality is to provide the user information about FRA's rail lines, rail crossings, freight stations, and mileposting.

This dataset represents Exclusive Economic Zones (EEZ) of the world. Up to now, there was no global public domain cover available.
Therefore, the Flanders Marine Institute decided to develop its own database. The database includes two global GIS-layers: one contains polylines that represent the maritime boundaries of the world countries, the other one is a polygon layer representing the Exclusive Economic Zone of countries. The database also contains digital information about treaties. Please note that the EEZ shapefile also includes the internal waters of each country.

Os arquivos aqui disponíveis são suplementos digitais ao artigo "Vegetação, unidades fitoecológicas e diversidade paisagística do estado do Ceará", publicado na revista Rodriguésia, volume 66(3) 1- O primeiro arquivo é o mapa geomorfológico do estado do Ceará apresentado no artigo. 2- O segundo é o mapa de unidades fitoecológicas do Ceará apresentado e discutido em nosso artigo, o qual é uma modificação da proposta cartográfica feita por Figueiredo (1997. Atlas do Ceará. Fortaleza: IPLANCE). 3- Os arquivos 3.1, 3.2 e 3.3 são arquivos para visualizar o mapa fitogeográfico do artigo em sistemas de informações geográficas. O arquivo 3.1 é o mapa apresentado em nosso artigo em formato KML, para baixar e visualizar no Google Earth. O arquivo 3.2. é o mesmo mapa em formato Shapefile para que o leitor possa fazer seus próprios mapas à partir do mapa apresentado no artigo. O arquivo 3.3 é o mapa de unidades fitoecológicas do Ceará como originalmente proposto pelo IPECE no Atlas do Ceará, em formato KML para visualizar no Google Earth. 4- O quarto arquivo é um organograma representando a relação entre as diferentes unidades geomorfológicas e os tipos vegetacionais do estado. 5- O quinto arquivo traz uma listagem de espécies características de cada tipo vegetacional tratado no artigo. Esta lista não é extensiva e apenas mostra um pequeno grupo de espécies típicas das vegetações cearenses. 6 e 7- Por fim, nosso artigo analiza por meio de análises multivariadas a similaridade florística entre as vegetações do estado, segundo dados disponíveis na literatura. A matriz de presença-ausência utilizada nas análises multivariadas e as referências bibliográficas dos trabalhos estão respectivamente no sexto e sétimo arquivos.

Também disponibilizamos como suplemento digital ao artigo um acervo fotográfico dos diferentes tipos vegetacionais e paisagens do estado do Ceará. O acervo fotográfico pode ser acessado em: http://dx.doi.org/10.6084/m9.figshare.1289920.

M.M. Moura-Fé foi responsável pela alaboração do arquivo 1; M.F. Moro foi responsável pela alaboração dos arquivos 2 e 3; M.B. Macêdo foi responsável pelo arquivo 4; A.S.F. Castro foi responsável pelo arquivo 5 e R.C. Costa foi responsável pelos arquivos 6 e 7.