Skip to main content
Geographic Information Systems

Return to Answer

replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

I would personally go with features over markers. Point features (and all features) allow for labeling and can be represented in different shapes and colors like circles, x, square and so forth. Not to mention all the additional intrinsic functionality and flexibility features have over markers such as geographical calculations, transformations, click/highlight/select handlers and on and on.

enter image description here

I hate to be pushybe pushy, but it would be beneficial if you used something like GeoServer or MapServer on the back end. You could set a WFS strategy that works on your 5-30 second (or whatever) interval timer and allow it to fetch and render the features automatically. In case you're wondering, it already does this in ajax form. So you don't have to write the code to query the database, parse, convert, etc... on 300 objects on your map. Openlayers will render the latest WFS data on your Geoserver which is pointed to PostGIS. You would save yourself a lot of time and effort reinventing that wheel. Openlayers WFS protocol can be set to query based on your viewport on a temporal filter.

Though features don't perform well when there are a lot of them. 300 might be pushing it. If you see that performance is an issue, you can easily switch to using WMS (only if you have Geoserver or Mapserver). You can also use a cluster strategy to minimize un necessary features on your map.

I would personally go with features over markers. Point features (and all features) allow for labeling and can be represented in different shapes and colors like circles, x, square and so forth. Not to mention all the additional intrinsic functionality and flexibility features have over markers such as geographical calculations, transformations, click/highlight/select handlers and on and on.

enter image description here

I hate to be pushy, but it would be beneficial if you used something like GeoServer or MapServer on the back end. You could set a WFS strategy that works on your 5-30 second (or whatever) interval timer and allow it to fetch and render the features automatically. In case you're wondering, it already does this in ajax form. So you don't have to write the code to query the database, parse, convert, etc... on 300 objects on your map. Openlayers will render the latest WFS data on your Geoserver which is pointed to PostGIS. You would save yourself a lot of time and effort reinventing that wheel. Openlayers WFS protocol can be set to query based on your viewport on a temporal filter.

Though features don't perform well when there are a lot of them. 300 might be pushing it. If you see that performance is an issue, you can easily switch to using WMS (only if you have Geoserver or Mapserver). You can also use a cluster strategy to minimize un necessary features on your map.

I would personally go with features over markers. Point features (and all features) allow for labeling and can be represented in different shapes and colors like circles, x, square and so forth. Not to mention all the additional intrinsic functionality and flexibility features have over markers such as geographical calculations, transformations, click/highlight/select handlers and on and on.

enter image description here

I hate to be pushy, but it would be beneficial if you used something like GeoServer or MapServer on the back end. You could set a WFS strategy that works on your 5-30 second (or whatever) interval timer and allow it to fetch and render the features automatically. In case you're wondering, it already does this in ajax form. So you don't have to write the code to query the database, parse, convert, etc... on 300 objects on your map. Openlayers will render the latest WFS data on your Geoserver which is pointed to PostGIS. You would save yourself a lot of time and effort reinventing that wheel. Openlayers WFS protocol can be set to query based on your viewport on a temporal filter.

Though features don't perform well when there are a lot of them. 300 might be pushing it. If you see that performance is an issue, you can easily switch to using WMS (only if you have Geoserver or Mapserver). You can also use a cluster strategy to minimize un necessary features on your map.

Source Link
CaptDragon
CaptDragon
  • 13.4k
  • 7
  • 55
  • 96

I would personally go with features over markers. Point features (and all features) allow for labeling and can be represented in different shapes and colors like circles, x, square and so forth. Not to mention all the additional intrinsic functionality and flexibility features have over markers such as geographical calculations, transformations, click/highlight/select handlers and on and on.

enter image description here

I hate to be pushy, but it would be beneficial if you used something like GeoServer or MapServer on the back end. You could set a WFS strategy that works on your 5-30 second (or whatever) interval timer and allow it to fetch and render the features automatically. In case you're wondering, it already does this in ajax form. So you don't have to write the code to query the database, parse, convert, etc... on 300 objects on your map. Openlayers will render the latest WFS data on your Geoserver which is pointed to PostGIS. You would save yourself a lot of time and effort reinventing that wheel. Openlayers WFS protocol can be set to query based on your viewport on a temporal filter.

Though features don't perform well when there are a lot of them. 300 might be pushing it. If you see that performance is an issue, you can easily switch to using WMS (only if you have Geoserver or Mapserver). You can also use a cluster strategy to minimize un necessary features on your map.