I believe I know what he is talking about. In every GIS software we have features (points, lines, polygons). Each feature has its own non-spatially related properties/attributes. Here is an example of aircraft(point) feature:
<code>
{ "3E198A": {
"course": 139,
"altitude": 25000,
"speed": 251,
"Squawk": "2250",
"Radar": "T-MLAT",
"Type": "C425",
"Registration": "D-IAWG",
"ID": "DIAWG"
}
}
As you can see, this information is always very topic-related. Normally, to put all this additional information into the point I have to put it into HTML and then into CDATA tags, like this:
If Locus will implement its own POI fields, all this data will go to its fields automatically, and be printed in the POI window. Actually this would be really nice feature, and maybe that would be a nice moment to introduce importing of GEOJSON files (http://www.geojson.org/)?
I believe I know what he is talking about. In every GIS software we have features (points, lines, polygons). Each feature has its own non-spatially related properties/attributes. Here is an example of aircraft(point) feature:
<code>
{ "3E198A": {
"course": 139,
"altitude": 25000,
"speed": 251,
"Squawk": "2250",
"Radar": "T-MLAT",
"Type": "C425",
"Registration": "D-IAWG",
"ID": "DIAWG"
}
}
As you can see, this information is always very topic-related. Normally, to put all this additional information into the point I have to put it into HTML and then into CDATA tags, like this:
If Locus will implement its own POI fields, all this data will go to its fields automatically, and be printed in the POI window. Actually this would be really nice feature, and maybe that would be a nice moment to introduce importing of GEOJSON files (http://www.geojson.org/)?
pardon?
Hello Tariro
What means "POI fields"?
pardon?
Hello Tariro
What means "POI fields"?
Could you, please, give an example which fields you would like to add.
Could you, please, give an example which fields you would like to add.
I believe I know what he is talking about. In every GIS software we have features (points, lines, polygons). Each feature has its own non-spatially related properties/attributes. Here is an example of aircraft(point) feature:
<code>
{ "3E198A": {
"course": 139,
"altitude": 25000,
"speed": 251,
"Squawk": "2250",
"Radar": "T-MLAT",
"Type": "C425",
"Registration": "D-IAWG",
"ID": "DIAWG"
}
}
As you can see, this information is always very topic-related. Normally, to put all this additional information into the point I have to put it into HTML and then into CDATA tags, like this:
<code>
<description>
<![CDATA[
<table class="objecttable" style="">
<tbody><tr><th>Name</th><th>Value</th></tr>
<tr><td>course</td><td><span class="number">139</span></td></tr>
<tr><td>altitude</td><td><span class="number">25000</span></td></tr>
<tr><td>speed</td><td><span class="number">251</span></td></tr>
<tr><td>Squawk</td><td><span class="string">2250</span></td></tr>
<tr><td>Radar</td><td><span class="string">T-MLAT</span></td></tr>
<tr><td>Type</td><td><span class="string">C425</span></td></tr>
<tr><td>Registration</td><td><span class="string">D-IAWG</span></td></tr>
<tr><td>ID</td><td><span class="string">DIAWG</span></td></tr>
</tbody></table>
]]>
</description>
If Locus will implement its own POI fields, all this data will go to its fields automatically, and be printed in the POI window. Actually this would be really nice feature, and maybe that would be a nice moment to introduce importing of GEOJSON files (http://www.geojson.org/)?
I believe I know what he is talking about. In every GIS software we have features (points, lines, polygons). Each feature has its own non-spatially related properties/attributes. Here is an example of aircraft(point) feature:
<code>
{ "3E198A": {
"course": 139,
"altitude": 25000,
"speed": 251,
"Squawk": "2250",
"Radar": "T-MLAT",
"Type": "C425",
"Registration": "D-IAWG",
"ID": "DIAWG"
}
}
As you can see, this information is always very topic-related. Normally, to put all this additional information into the point I have to put it into HTML and then into CDATA tags, like this:
<code>
<description>
<![CDATA[
<table class="objecttable" style="">
<tbody><tr><th>Name</th><th>Value</th></tr>
<tr><td>course</td><td><span class="number">139</span></td></tr>
<tr><td>altitude</td><td><span class="number">25000</span></td></tr>
<tr><td>speed</td><td><span class="number">251</span></td></tr>
<tr><td>Squawk</td><td><span class="string">2250</span></td></tr>
<tr><td>Radar</td><td><span class="string">T-MLAT</span></td></tr>
<tr><td>Type</td><td><span class="string">C425</span></td></tr>
<tr><td>Registration</td><td><span class="string">D-IAWG</span></td></tr>
<tr><td>ID</td><td><span class="string">DIAWG</span></td></tr>
</tbody></table>
]]>
</description>
If Locus will implement its own POI fields, all this data will go to its fields automatically, and be printed in the POI window. Actually this would be really nice feature, and maybe that would be a nice moment to introduce importing of GEOJSON files (http://www.geojson.org/)?
Refresh
Refresh
Hi,
unfortunately I have to close this idea. Such feature is currently implemented in Locus GIS, but it's not (and won't) planned for Locus Map. Sorry.
Hi,
unfortunately I have to close this idea. Such feature is currently implemented in Locus GIS, but it's not (and won't) planned for Locus Map. Sorry.
Replies have been locked on this page!