君，已阅读到文档的结尾了呢~~
使用gpx数据格式实现航点批量导入,gpx格式,gpx格式怎么打开,img批量导入工具,ppt批量导入图片,img批量导入器,excel批量导入图片,飞信批量导入联系人,飞信批量导入好友,excel批量导入word
扫扫二维码，随身浏览文档
手机或平板扫扫即可继续访问
使用gpx数据格式实现航点批量导入
举报该文档为侵权文档。
举报该文档含有违规或不良信息。
反馈该文档无法正常浏览。
举报该文档为重复文档。
推荐理由：
将文档分享至：
分享完整地址
文档地址：
粘贴到BBS或博客
flash地址：
支持嵌入FLASH地址的网站使用
html代码：
&embed src='/DocinViewer-4.swf' width='100%' height='600' type=application/x-shockwave-flash ALLOWFULLSCREEN='true' ALLOWSCRIPTACCESS='always'&&/embed&
450px*300px480px*400px650px*490px
支持嵌入HTML代码的网站使用
您的内容已经提交成功
您所提交的内容需要审核后才能发布，请您等待！
3秒自动关闭窗口实用的60个CSS代码片段
更新日期：
1、垂直对齐
如果你用CSS，则你会有困惑：我该怎么垂直对齐容器中的元素？现在，利用CSS3的Transform，可以很优雅的解决这个困惑：
.verticalcenter{
-webkit-transform: translateY(-50%);
-o-transform: translateY(-50%);
transform: translateY(-50%);
使用这个技巧，从单行文本、段落到box，都会垂直对齐。目前浏览器对Transform的支持是需要关注的，Chrome 4, Opera 10, Safari 3, Firefox 3, and Internet Explorer 9均支持该属性
2、伸展一个元素到窗口高度
在具体场景中，你可能想要将一个元素伸展到窗口高度，基本元素的调整只能调整容器的大小,因此要使一个元素伸展到窗口高度，我们需要伸展顶层元素：html和body:
然后将100%应用到任何元素的高
3、基于文件格式使用不同的样式
为了更容易知道链接的目标，有时你想让一些链接看起来和其它的不同。下面的片段在文本链接前添加一个图标，对不同的资源使用不同的图标或图片：
4、创建跨浏览器的图像灰度
灰度有时看起来简约和优雅，能为网站呈现更深层次的色调。在示例中，我们将对一个SVG图像添加灰度过滤：
为了跨浏览器，会用到filter属性：
5、背景渐变动画
CSS中最具诱惑的一个功能是能添加动画效果，除了渐变，你可以给背景色、透明度、元素大小添加动画。目前，你不能为渐变添加动画，但下面的代码可能有帮助。它通过改变背景位置，让它看起来有动画效果。
6、CSS：表格列宽自适用
对于表格，当谈到调整列宽时，是比较痛苦的。然后，这里有一个可以使用的技巧：给td元素添加white-space:能让文本正确的换行
7、只在一边或两边显示盒子阴影
如果你要一个盒阴影，试试这个技巧，能为任一边添加阴影。为了实现这个，首先定义一个有具体宽高的盒子，然后正确定位:after伪类。实现底边阴影的代码如下
.box-shadow {
background-color: #FF8020;
width: 160
height: 90
margin-top: -45
margin-left: -80
left: 50%;
.box-shadow:after {
content: "";
width: 150
margin-top: 88
margin-left: -75
left: 50%;
z-index: -1;
-webkit-box-shadow: 0px 0px 8px 2px #000000;
-moz-box-shadow: 0px 0px 8px 2px #000000;
box-shadow: 0px 0px 8px 2px #000000;
8、包裹长文本
如果你碰到一个比自身容器长的文本，这个技巧对你很有用。在这个示例中，默认时，不管容器的宽度，文本都将水平填充。
简单的CSS代码就能在容器中调整文本：
效果看起来如下：
9、制造模糊文本
想要让文本模糊？可以使用color透明和text-shadow实现
.blurry-text {
text-shadow: 0 0 5px rgba(0,0,0,0.5);
10、用CSS动画实现省略号动画
这个片段将帮助你制造一个ellipsis的动画，对于简单的加载状态是很有用的，而不用去使用gif图像。
.loading:after {
display: inline-
vertical-align:
animation: ellipsis 2
content: "\2026";
11、样式重置
12、典型的CSS清除浮动
.clearfix:after { content: "."; display: clear: visibility: line-height: 0; height: 0; }
.clearfix { display: inline- }
13、新版清除浮动（2011）
.clearfix:before, .container:after { content: ""; display: }
.clearfix:after { clear: }
14、跨浏览器的透明
.transparent {
filter: alpha(opacity=50);
15、CSS引用模板
16、个性圆角
#container {
-webkit-border-radius: 4px 3px 6px 10
-moz-border-radius: 4px 3px 6px 10
-o-border-radius: 4px 3px 6px 10
border-radius: 4px 3px 6px 10
17、通用媒体查询
18、现代字体栈
19、自定义文本选择
::selection { background: #e2eae2; }
::-moz-selection { background: #e2eae2; }
::-webkit-selection { background: #e2eae2; }
20、为logo隐藏H1
21、图片边框偏光
22、锚链接伪类
a:link { color: }
a:visited { color: }
a:hover { color: }
a:active { color: }
23、奇特的CSS引用
.has-pullquote:before {
24、CSS3：全屏背景
25、内容垂直居中
.container {
min-height: 6.5
display: table-
vertical-align:
26、强制出现垂直滚动条
27、CSS3渐变模板
#colorbox {
background: #629721;
background-image: -webkit-gradient(linear, left top, left bottom, from(#83b842), to(#629721));
background-image: -webkit-linear-gradient(top, #83b842, #629721);
background-image: -moz-linear-gradient(top, #83b842, #629721);
background-image: -ms-linear-gradient(top, #83b842, #629721);
background-image: -o-linear-gradient(top, #83b842, #629721);
background-image: linear-gradient(top, #83b842, #629721);
@font-face {
font-family: 'MyWebFont';
src: url('webfont.eot');
29、缝合CSS3元素
30、CSS3 斑马线
31、有趣的&
font-family: Baskerville, 'Goudy Old Style', Palatino, 'Book Antiqua',
font-style:
font-weight:
32、大字段落
p:first-letter{
margin: 5px 0 0 5
color: #ff3366;
font-size: 5.4
font-family: Georgia, Times New Roman,
33、内部CSS3 盒阴影
-moz-box-shadow: inset 2px 0 4px #000;
-webkit-box-shadow: inset 2px 0 4px #000;
box-shadow: inset 2px 0 4px #000;
34、外部CSS3 盒阴影
-webkit-box-shadow: 0 2px 2px -2px rgba(0, 0, 0, 0.52);
-moz-box-shadow: 0 2px 2px -2px rgba(0, 0, 0, 0.52);
box-shadow: 0 2px 2px -2px rgba(0, 0, 0, 0.52);
35、三角形列表项目符号
36、固定宽度的居中布局
#page-wrap {
width: 800
37、CSS3 列文本
#columns-3 {
text-align:
-moz-column-count: 3;
-moz-column-gap: 12
-moz-column-rule: 1px solid #c4c8
-webkit-column-count: 3;
-webkit-column-gap: 12
-webkit-column-rule: 1px solid #c4c8
38、CSS固定页脚
height: 30
width: 100%;
background: #444;
39、IE6的PNG透明修复
height:100
background: url(/folder/yourimage.png) no-
_background:
_filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='/folder/yourimage.png',sizingMethod='crop');
40、跨浏览器设置最小高度
#container {
min-height: 550
height: auto !
height: 550
41、CSS3 鲜艳的输入
42、基于文件类型的链接样式
43、强制换行
44、在可点击的项目上强制手型
45、网页顶部盒阴影
body:before {
content: "";
width: 100%;
height: 10
-webkit-box-shadow: 0px 0px 10px rgba(0,0,0,.8);
-moz-box-shadow: 0px 0px 10px rgba(0,0,0,.8);
box-shadow: 0px 0px 10px rgba(0,0,0,.8);
z-index: 100;
46、CSS3对话气泡
.chat-bubble {
background-color: #
border: 2px solid #666;
font-size: 35
line-height: 1.3
margin: 10
padding: 10
text-align:
width: 300
-moz-border-radius: 20
-webkit-border-radius: 20
-moz-box-shadow: 0 0 5px #888;
-webkit-box-shadow: 0 0 5px #888;
font-family: 'Bangers', arial,
.chat-bubble-arrow-border {
border-color: #666 transparent tra
border-style:
border-width: 20
height: 0;
bottom: -42
.chat-bubble-arrow {
border-color: #ededed transparent tra
border-style:
border-width: 20
height: 0;
bottom: -39
47、H1-H5默认样式
48、纯CSS背景噪音
49、持久的列表排序
50、CSS悬浮提示文本
51、深灰色的圆形按钮
.graybtn {
-moz-box-shadow:inset 0px 1px 0px 0px #
-webkit-box-shadow:inset 0px 1px 0px 0px #
box-shadow:inset 0px 1px 0px 0px #
background:-webkit-gradient( linear, left top, left bottom, color-stop(0.05, #ffffff), color-stop(1, #d1d1d1) );
background:-moz-linear-gradient( center top, #ffffff 5%, #d1d1d1 100% );
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#ffffff', endColorstr='#d1d1d1');
background-color:#
-moz-border-radius:6
-webkit-border-radius:6
border-radius:6
border:1px solid #
display:inline-
color:#777777;
font-family:
font-size:15
font-weight:
padding:6px 24
text-decoration:
text-shadow:1px 1px 0px #
.graybtn:hover {
background:-webkit-gradient( linear, left top, left bottom, color-stop(0.05, #d1d1d1), color-stop(1, #ffffff) );
background:-moz-linear-gradient( center top, #d1d1d1 5%, #ffffff 100% );
filter:progid:DXImageTransform.Microsoft.gradient(startColorstr='#d1d1d1', endColorstr='#ffffff');
background-color:#d1d1d1;
.graybtn:active {
52、在可打印的网页中显示URLs
@media print
content: " [" attr(href) "] ";
53、禁用移动Webkit的选择高亮
54、CSS3 圆点图案
55、CSS3 方格图案
56、Github的fork色带
background-color: #a00;
57、CSS font属性缩写
58、论文页面的卷曲效果
59、鲜艳的锚链接
60、带CSS3特色的横幅显示
.featureBanner {
margin: 20px
.featureBanner:before {
content: "Featured";
padding-right: 10
color: #232323;
font-weight:
border: 15px solid #ffa200;
border-right-color:
line-height: 0
box-shadow: -0px 5px 5px -5px #000;
z-index: 1;
.featureBanner:after {
content: "";
border: 4px solid #89540c;
border-left-color:
border-bottom-color:
文／poetries（简书作者）原文链接：/p/ea3著作权归作者所有，转载请联系作者获得授权，并标注“简书作者”。
> 本站内容系网友提交或本网编辑转载，其目的在于传递更多信息，并不代表本网赞同其观点和对其真实性负责。如涉及作品内容、版权和其它问题，请及时与本网联系，我们将在第一时间删除内容！
css是不能够定义变量的,也不能嵌套.它没有编程语言的特性.在项目开发中,常常发现有很多css代码是相同的,但我们通常都是复制然后粘贴. 举个例子:假设h5应用里主题色是#FF3A6D,可能用于文字或者背景色.通常开发中,哪里需要这个颜色,我们就复制这个颜色并粘贴.下次要修改就得全部查找批量替换,其实不是很方便. 本文即将介绍的less将让我们更快更方便的编 ...
继续更新有关重构的博客,前三篇是关于类.函数和数据的重构的博客,内容还算比较充实吧.今天继续更新,本篇博客的主题是关于条件表达式的重构规则.有时候在实现比较复杂的业务逻辑时,各种条件各种嵌套.如果处理不好的话,代码看上去会非常的糟糕,而且业务逻辑看上去会非常混乱.今天就通过一些重构规则来对条件表达式进行重构,让业务逻辑更为清晰,代码更以维护和扩展. 今天博客 ...
Markdown的代码样式如何设置? 一.问题描述 由于在WIZ中 写Markdown格式的笔记,然后通用插件上传到博客园,上传之后,markdown的代码样式不见了,那么如何设置呢? 二.设置步骤 1. 进入博客园的后台管理 2. 把下面的CSS代码,复制到这里面 /*markdown 代码样式*/ tt, code, kbd, samp { font-f ...
&S& ::= &V& &S& ::= &E& &E& ::= &V& &V& ::= &V& ::= * x = x = * *x = **x = **x 输出 输出结果是此文法的 (__S)[S][&S& └─(__E)[E][&E&
前言 这是Glen Maddern发布于日的一篇文章,主要是之前翻译的文章&理解CSS模块方法&里提到这篇文章,现在算是顺藤摸瓜跟进来看看. 这里的翻译都是根据我自己的理解进行的,所以不是一句一句的来的,有哪些不对的也在所难免,水平有限,希望大家指出. 正文 如果想在最近CSS开发思想上找到一个转变点,最好去找Christoph ...
网上收集了一些学习AngularJS的常用资源,自己做个备份,另外也希望能给有需要的朋友随时查阅. 书籍 Books AngularJS 立刻快速开发 AngularJS AngularJS 菜单 AngularJS 在行动 AngularJS For .Net 开发员 AngularJS 浏览器应用程序开发 发现自己的 AngularJS 优势 Angul ...建议各位在本站关闭广告屏蔽插件,因为他可能会导致部分功能js无法使用,比如【】的
如下原因会造成JSON校验失败,而且会让你不知道为什么失败
JSON字符串里的非数字型键值没有双引号
JSON中存在\t这样的制表符,看起来和空格一样,但是就是因为它的存在校验不通过。去掉就能过了。
编辑器有bom头也会造成
Copyright (C)
昆山良讯网络科技有限公司 All rights reserved.
本站申明:本网站部分工具是站长整合网上已有工具、开源包等，并全部遵循原有协议发布，著作权归属原作者或是团队。GPX - GPS Exchange Format
GPX - GPS Exchange Format
(Starting with GDAL 1.5.0)
GPX (the GPS Exchange Format) is a light-weight XML data format for the interchange of GPS data (waypoints, routes, and tracks) between applications and Web services on the Internet.
OGR has support for GPX reading (if GDAL is build with expat library support) and writing.
Version supported are GPX 1.0 and 1.1 for reading, GPX 1.1 for writing.
The OGR driver supports reading and writing of all the GPX feature types :
waypoints : layer of features of OGR type wkbPoint
routes : layer of features of OGR type wkbLineString
tracks : layer of features of OGR type wkbMultiLineString
It also supports reading of route points and track points in standalone layers (route_points and track_points), so
that their own attributes can be used by OGR.
In addition to its GPX attributes, each route point of a route has a route_fid
(foreign key to the FID of its belonging route)
and a route_point_id which is its sequence number in the route.
The same applies for track points with track_fid, track_seg_id and track_seg_point_id.
All coordinates are relative to the WGS84 datum (EPSG:4326).
If the environment variable GPX_ELE_AS_25D is set to YES, the elevation element will
be used to set the Z coordinates of waypoints, route points and track points.
The OGR/GPX reads and writes the GPX attributes for the waypoints, routes and tracks.
By default, up to 2 &link& elements can be taken into account by feature.
This default number can be changed with the GPX_N_MAX_LINKS environment variable.
Encoding issues
Expat library supports reading the following built-in encodings :
ISO-8859-1
OGR 1.8.0 adds supports for Windows-1252 encoding (for previous versions, altering the encoding
mentioned in the XML header to ISO-8859-1 might work in some cases).
The content returned by OGR will be encoded in UTF-8, after the conversion from the
encoding mentioned in the file header is.
If your GPX file is not encoded in one of the previous encodings, it will not be parsed by the
GPX driver. You may convert it into one of the supported encoding with the iconv utility
for example and change accordingly the encoding parameter value in the XML header.
When writing a GPX file, the driver expects UTF-8 content to be passed in.
Extensions element reading
If the &extensions& element is detected in a GPX file, OGR will expose the content
of its sub elements as fields. Complex content of sub elements will be exposed as an XML blob.
The following sequence GPX content :
&extensions&
&navaid:name&TOTAL RF&/navaid:name&
&navaid:address&BENSALEM&/navaid:address&
&navaid:state&PA&/navaid:state&
&navaid:country&US&/navaid:country&
&navaid:frequencies&
&navaid:frequency type="CTAF" frequency="122.900" name="CTAF"/&
&/navaid:frequencies&
&navaid:runways&
&navaid:runway designation="H1" length="80" width="80" surface="ASPH-G"&
&/navaid:runway&
&/navaid:runways&
&navaid:magvar&12&/navaid:magvar&
&/extensions&
will be interpreted in the OGR SF model as :
navaid_name (String) = TOTAL RF
navaid_address (String) = BENSALEM
navaid_state (String) = PA
navaid_country (String) = US
navaid_frequencies (String) = &navaid:frequency type="CTAF" frequency="122.900" name="CTAF" &&/navaid:frequency&
navaid_runways (String) = &navaid:runway designation="H1" length="80" width="80" surface="ASPH-G" &&/navaid:runway&
navaid_magvar (Integer) = 12
Note : the GPX driver will output content of the extensions element only if it is found in the first records of the GPX file.
If extensions appear later, you can force an explicit parsing of the whole file with the GPX_USE_EXTENSIONS environment variable.
Creation Issues
On export all layers are written to a single GPX file. Update of existing
files is not currently supported.
If the output file already exits, the writing will not occur. You have to delete the existing file first.
Supported geometries :
Features of type wkbPoint/wkbPoint25D are written in the wpt element.
Features of type wkbLineString/wkbLineString25D are written in the rte element.
Features of type wkbMultiLineString/wkbMultiLineString25D are written in the trk element.
Other type of geometries are not supported.
For route points and tracks points, if there is a Z coordinate, it is used to fill the elevation element
of the corresponding points.
Starting with GDAL/OGR 1.8.0, if a layer is named "track_points" with wkbPoint/wkbPoint25D geometries, the
tracks in the GPX file will be built from the sequence of features in that layer. This is the way of setting GPX attributes
for each track point, in addition to the raw coordinates. Points belonging to the same track are
identified thanks to the same value of the 'track_fid' field (and it will be broken into track segments
according to the value of the 'track_seg_id' field). They must be written in sequence so that track objects
are properly reconstructed. The 'track_name' field can be set on the first track point to fill the &name&
element of the track.
Similarly, if a layer is named "route_points" with wkbPoint/wkbPoint25D geometries, the routes in the GPX file
will be built from the sequence of points with the same value of the 'route_fid' field.
The 'route_name'
field can be set on the first track point to fill the &name& element of the route.
The GPX writer supports the following layer creation options:
FORCE_GPX_TRACK:
By default when writing a layer whose features are of type wkbLineString, the GPX driver
chooses to write them as routes.
If FORCE_GPX_TRACK=YES is specified, they will be written
as tracks.
FORCE_GPX_ROUTE:
By default when writing a layer whose features are of type wkbMultiLineString, the GPX driver
chooses to write them as tracks.
If FORCE_GPX_ROUTE=YES is specified, they will be written
as routes, provided that the multilines are composed of only one single line.
The GPX writer supports the following dataset creation options:
GPX_USE_EXTENSIONS:
By default, the GPX driver will discard attribute fields that do not match the GPX XML definition (name, cmt, etc...).
If GPX_USE_EXTENSIONS=YES is specified, extra fields will be written inside the&extensions& tag.
GPX_EXTENSIONS_NS:
Only used if GPX_USE_EXTENSIONS=YES and GPX_EXTENSIONS_NS_URL is set.
The namespace value used for extension tags. By default, "ogr".
GPX_EXTENSIONS_NS_URL:
Only used if GPX_USE_EXTENSIONS=YES and GPX_EXTENSIONS_NS is set.
The namespace URI. By default, "http://osgeo.org/gdal".
LINEFORMAT: (GDAL/OGR >= 1.8.0)
By default files are created with the line
termination conventions of the local platform (CR/LF on win32 or
LF on all other systems).
This may be overridden through use of the
LINEFORMAT layer creation option which may have a value of CRLF
(DOS format) or LF (Unix format).
Waypoints, routes and tracks must be written into that order to be valid against the XML Schema.
When translating from a source dataset, it may be necessary to rename the field names from the source dataset to the expected GPX attribute names, such as &name&, &desc&, etc...
This can be done with a
dataset, or by using the "-sql" option of the ogr2ogr utility.
Issues when translating to Shapefile
When translating the track_points layer to a Shapefile, the field names "track_seg_id" and "track_seg_point_id" are
truncated to 10 characters in the .DBF file, thus leading to duplicate names.
To avoid this, starting with GDAL 1.6.1,
you can define the GPX_SHORT_NAMES configuration option to TRUE to make them be reported respectively as "trksegid" and "trksegptid",
which will allow them to be unique once translated to DBF. The "route_point_id" field of route_points layer will also be renamed to "rteptid".
But note that no particular processing will be done for any extension field names.
To translate the track_points layer of a GPX file to a set of shapefiles :
ogr2ogr --config GPX_SHORT_NAMES YES out input.gpx track_points
Shapefile does not support fields of type DateTime. It only supports fields of type Date. So by default, you will lose the
hour:minute:second part of the Time elements of a GPX file.
Starting with GDAL 1.6.0, you can use the OGR SQL CAST operator to convert the time field to a string :
ogr2ogr out input.gpx -sql "SELECT ele, CAST(time AS character(32)) FROM waypoints"
Starting with GDAL 1.7.0, there is a more convenient way to select all fields and ask for the conversion of the ones of a given type to strings:
ogr2ogr out input.gpx -fieldTypeToString DateTime
VSI Virtual File System API support
(Some features below might require OGR >= 1.9.0)
The driver supports reading and writing to files managed by VSI Virtual File System API, which include
"regular" files, as well as files in the /vsizip/ (read-write) , /vsigzip/ (read-write) , /vsicurl/ (read-only) domains.
Writing to /dev/stdout or /vsistdout/ is also supported.
The ogrinfo utility can be used to dump the content of a GPX datafile :
ogrinfo -ro -al input.gpx
The ogr2ogr utility can be used to do GPX to GPX translation :
ogr2ogr -f GPX output.gpx input.gpx waypoints routes tracks
Note : in the case of GPX to GPX translation, you need to specify the layer names,
in order to discard the route_points and track_points layers.
Use of the &extensions& tag for output :
ogr2ogr -f GPX
-dsco GPX_USE_EXTENSIONS=YES output.gpx input
which will give an output like the following one :
&?xml version="1.0"?&
&gpx version="1.1" creator="GDAL 1.5dev"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ogr="http://osgeo.org/gdal"
xmlns="/GPX/1/1"
xsi:schemaLocation="/GPX/1/1 /GPX/1/1/gpx.xsd"&
&wpt lat="1" lon="2"&
&extensions&
&ogr:Primary_ID&PID5&/ogr:Primary_ID&
&ogr:Secondary_ID&SID5&/ogr:Secondary_ID&
&/extensions&
&wpt lat="3" lon="4"&
&extensions&
&ogr:Primary_ID&PID4&/ogr:Primary_ID&
&ogr:Secondary_ID&SID4&/ogr:Secondary_ID&
&/extensions&
Use of -sql option to remap field names to the ones allowed by the GPX schema (starting with GDAL 1.6.0):
ogr2ogr -f GPX output.gpx input.shp -sql "SELECT field1 AS name, field2 AS desc FROM input"
How to solve "ERROR 6: Cannot create GPX layer XXXXXX with unknown geometry type" ?
This error happens when the layer to create does not expose a precise geometry type, but just a generic
wkbUnknown type. This is for example the case when using ogr2ogr with a SQL request to a PostgreSQL datasource.
You must then explicitly specify -nlt POINT (or LINESTRING or MULTILINESTRING).