Timeline for How to force ogr to treat JSON mapserver query as "Multiline" instead of "Line" geometry type?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2016 at 20:49 | answer | added | user30184 | timeline score: 1 | |
| Jul 24, 2016 at 13:04 | answer | added | Philip Whitten | timeline score: 1 | |
| Jul 23, 2016 at 7:40 | comment | added | user30184 |
Thanks for showing that the json data has line parts separated with ] ], [ [. Looks like a bug in GDAL.
|
|
| Jul 23, 2016 at 3:38 | history | edited | Philip Whitten | CC BY-SA 3.0 |
Modified post to show evidence for MultiLineString data type
|
| Jul 23, 2016 at 3:20 | comment | added | Philip Whitten | I have changed one of the tags and the question to distinguish the ESRI REST MapServer from the better known open source MapServer. | |
| Jul 23, 2016 at 3:19 | comment | added | Philip Whitten | I believe that they are MultiLineStrings as the data for discrete features consists of lists of many coordinates within a larger list for the feature. This structure is evident by opening the URL in a browser and scrolling down. Furthermore, if you plot the layer obtained by the script with QGIS or ArcGIS you will observe lines that connect non-neighboring sections of the features. In this case the features are roads. | |
| Jul 23, 2016 at 3:14 | history | edited | Philip Whitten | CC BY-SA 3.0 |
Changed 'mapserver' tag to 'arcgis-rest-api' to distinguish from opensource mapserver.
|
| Jul 22, 2016 at 21:09 | comment | added | user30184 | Data from that URL comes from ESRI REST service, not from the open source MapServer server, if your tag refers to that. By looking at the returned data all 371 features are linestrings. What makes you think that they are multilinestrings? | |
| Jul 22, 2016 at 13:32 | history | asked | Philip Whitten | CC BY-SA 3.0 |