Thursday 19 January 2006 9:14:00 am

The Spatial Datatype should be able to store geometry data (it could alse be named <i>Geometry Datatype</i>):

- Point (coordinates for one place - could be the place where a person lives).
- Line (coordinates that makes up a line - could be a travelling route).
- Polygon (coordinates that makes up a polygon - could be a conflict area).

The type of geometry data to store could be set in the class definition.

In a simple version of the datatype the user could just type the coordinates in text boxes, but this is not very user friendly.

It would be better to present a map where the user can zoom in and click on the point/make a line/polygon - and where the results are stored as coordinates in the spatial database.

Maybe the coordinates should be stored in a separate table so the data are easily accessible in MapServer? One should be able to generate a map where all the points are marked by symbols. The object_id could be stored with the coordinates to make it possible to click on the symbol to get more information about the object.

http://blog.thematicmapping.org
http://www.globalis.no

Thursday 19 January 2006 3:13:54 pm

A spatial datatype is only one part of an eZ publish Spatial Extension. Another possibility is to define a new Mapfile class.

<i>The Mapfile is the heart of MapServer. It defines the relationships between objects, points MapServer to where data are located and defines how things are to be drawn.</i>
http://mapserver.gis.umn.edu/docs/reference/mapfile/referencemanual-all-pages

The Mapfile class should define a standard set of attributes which defines the map (and should be extendable).

When an object is created from the Mapfile class, eZ publish should gather information about all the available map layers from the spatial database. The user could select which layers to show on the map, as well as settings like size, format (PNG, SVG) etc.

When the object is published eZ publish automatically generates the Mapfile. When the user view the node/embedded object the Mapfile is send to MapServer (maybe with some additional parameters) - and the map is shown within the template.

A third solution is to define a custom tag where the user can write the name of a Mapfile.

<custom name="mapfile" mapfile="example.map" [...] ]></custom>

The custom tag template could use an operator to ask for the map from MapServer using the mapfile as a parameter.

I just found this:
http://www.mapserver.ch/en/index.php?menu=Overview

http://blog.thematicmapping.org
http://www.globalis.no

Friday 20 January 2006 2:29:17 am

I agree on the methods. I think we would like to start with only points - because it fulfills our needs at this time. Selecting lines and polygons through a web map interface is more difficult than a single point. Yes, I'm thinking of a point as a longitude/latitude co-ordinate

I think we should use some Ajax based technology to make a GUI map interface. In edit-mode a map is loaded from the MapServer and presented with some basic functionality (zoom in/out etc.). When the user clicks on the map - the position is sent to MapServer, which returns the longitude/latitude co-ordinate. This value pair is stored in the (spatial) database.

I'm thinking of using the upcoming ka-Map (http://ka-map.maptools.org) to achieve this.

http://blog.thematicmapping.org
http://www.globalis.no

Saturday 21 January 2006 9:17:12 am

More about the Spatial Datatype (maybe the name "Location Datatype" is better?):

The values for lonitude and latitude should be supplied in decimal notation (45.5, -122.25) instead of degrees, minutes and seconds (45 degrees 30 minuetes North, 122 degrees 15 minutes West). In the decimal notation Western hemisphere longitudes and Southern hemisphere latitudes are negative.

This datatype could make GeoTagging possible within eZ publish:
http://en.wikipedia.org/wiki/GeoTagging

http://blog.thematicmapping.org
http://www.globalis.no

Monday 23 January 2006 1:31:28 am

I think that's a good idea!

I didn't know about the Google Maps API
http://www.google.com/apis/maps/

http://blog.thematicmapping.org
http://www.globalis.no

Monday 23 January 2006 2:29:12 am

I would say it's a lightweight GIS-application. But it really depends on your needs. Read this article:
http://hobu.biz/index_html/google_phenomenon

As far as I can see, Google Maps API has no support for GIS-standards like Web Feature Service (WFS) and Web Map Service (WMS). You can't add your own map layers, only points and lines.

But you never know what Google has in mind. Today I read on a blog that Google has joined the Open Geospatial Consortium as a principal member. That is good news. Maybe they will support such services in the near future?

http://blog.thematicmapping.org
http://www.globalis.no

Friday 27 January 2006 2:05:45 am

More about Google Maps API:
http://www.pragmaticprogrammer.com/titles/sdgmapi/index.html
http://farm.tucows.com/blog/_archives/2006/1/5/1603306.html

http://blog.thematicmapping.org
http://www.globalis.no

Tuesday 28 March 2006 10:13:36 am

http://ez.no/community/contribs/applications/gis_global_information_systems_extension_pubsvn

Hi we created something for yahoo and google maps

including GEORSS, Yahoo GEOCODER plus mapping over YAHOO or GOOGLE

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Wednesday 05 April 2006 6:17:30 am

Björn, your GIS extension looks interesting.

If you only need a simple Flash map-application you can try DIY Map:
http://backspace.com/mapapp/

It's not open source, but it's free for uncommercial use and it's easy to load your data by XML. I have tried the application within eZ publish on:
http://demo.globalis.no/indikator/fruktbarhetstall/(show)/map

DIY map can also show points and lines using latitude and longitude.

http://blog.thematicmapping.org
http://www.globalis.no