https://forums.manning.com/forums/postgis-in-action-second-edition
JForum - http://www.jforum.netCould be PostGIS + PostgreSQL a good choice to: Appreciate for fast reply :-) ]]>https://forums.manning.com/posts/preList/41081/115170.pagehttps://forums.manning.com/posts/preList/41081/115170.page
GMTHelp required for viewing WFS layer in openlayers 3 I see now :)]]>https://forums.manning.com/posts/preList/40485/115165.pagehttps://forums.manning.com/posts/preList/40485/115165.page
GMTHelp required in listing 7.2 Geometry positioned by cordinates The hard-coded limit is on the WMS level like geoserver or mapserver or your tile server.

For example I think USGS limits you to a zoom level of 15 or 16 if you want to pull their tiles.

If you are using your own GeoServer and have it set to build tiles, you might want to check the max level it is set to build.]]>https://forums.manning.com/posts/preList/39842/112734.pagehttps://forums.manning.com/posts/preList/39842/112734.page
GMTErrata and suggestions, Chp 02https://forums.manning.com/posts/preList/40322/112702.pagehttps://forums.manning.com/posts/preList/40322/112702.page
GMTErrata and suggestions We'll take incorporate these suggestions if we write a 3rd edition. ]]>https://forums.manning.com/posts/preList/40248/112507.pagehttps://forums.manning.com/posts/preList/40248/112507.page
GMTHelp required in understanding the listing 11.1 Now you want to combine into a single record by unioning all the polygons.
When you union them, you will have a single multipolygon consisting of the same number of polygons as you had rows before because none of the polygons touched each other. But you'll have one row.

Now imagine a district (like the figure in 11.1 and 11.2) the boroughs of New York city. You'll start off with 5 rows (one for each borrough).
However since the borroughs touch each other, when you ST_Union them (the union operation will collapse the boundaries of each polygon into the adjacent touching ones) so that you end up with fewer polygons than what you started with.]]>https://forums.manning.com/posts/preList/39910/111645.pagehttps://forums.manning.com/posts/preList/39910/111645.page
GMTerror while inserting the ch11 datahttps://forums.manning.com/posts/preList/39906/111639.pagehttps://forums.manning.com/posts/preList/39906/111639.page
GMTHelp required for osm2pgsql https://forums.manning.com/posts/preList/39706/110972.pagehttps://forums.manning.com/posts/preList/39706/110972.page
GMTPL/R On postgreSQL 9.5 - Windows Looks like you or someone else posted a complaint about this where I would have suggested to and they posted an executable for those who want to try it out.

I'll update the source code to not have that get in the way.]]>https://forums.manning.com/posts/preList/37831/105710.pagehttps://forums.manning.com/posts/preList/37831/105710.page
GMTogr2ogr export usage in ch 4.3.4https://forums.manning.com/posts/preList/37828/105699.pagehttps://forums.manning.com/posts/preList/37828/105699.page
GMTCh.15 Compound Index Error on list page 384 CREATE EXTENSION btree_gist;

Then rerun the index creation.

We may have forgotten to state that in the book since we already had it installed.]]>https://forums.manning.com/posts/preList/37809/105652.pagehttps://forums.manning.com/posts/preList/37809/105652.page
GMTch12 raster questions > What data I see when I load the table in Qgis using dbmanager?
Well when you load the table since each month overlaps another, it's not predictable what you would see since I think QGIS just overlays the data on top as
it queries it and there is no guaranteed default sort.

If you do an ad-hoc query and drag that, then its whatever raster tiles your ad-hoc query returns that are used.
From what I recall, QGIS uses the raster over view tables if they are present. If they are not then it would just load the data in the main table.
Which overview (or if it uses the main table directly) it uses would depend on the extent of your map. This only applies to dragging a raster table.

> (What kind of interpolation Qgis does when I load the 2700 rows raster?) Again no interpolation unless you have over view tables . Which you would have if you loaded data with the -l option with raster2pgsql

> Question 2:

> what is the correct way to handle these 12 raster stored in the same table of postgis?
> Maybe I must create a 12 bands (1 for each month) raster?
I think for most cases its speedier and more practical to keep them as separate rows instead of store as separate bands. I tend to store them all in the same table
though you could opt for storing each month in a separate table. I tend to go with the single table since a spearate table would require 12 joins if you needed to see all bands as a single raster where as a single table you can employ aggregate arraying to add the bands and never have to do a join (just group by rast::geometry) )
This works fine as long as the gridding of each is the same, then you can always make them multi-band if needed with ST_AddBand
for one-off cases such as if you are disseminating the data to another group that would prefer to work with multi-band

You generally want to minimize on the number of bands you have in your raster
a) The more bands you have the fatter each row is which makes network pull slower if you don't need all 12 months viewed at the same time.
b) Updates become much slower too since every update basically requires delete and insert of all bands (an update in PostgreSQL via its MVCC implementation ends up being a delete and insert)

c) If you keep them as bands, you'd have to update more frequently - like as each month comes along instead of just adding new rows. Just adding new rows is less likely to mess up your existing data and also will be much faster since you don't have the delete penalty (required by Update).]]>https://forums.manning.com/posts/preList/37759/105525.pagehttps://forums.manning.com/posts/preList/37759/105525.page
GMTListing 3.2 feature_data Table Missing? I apologize that was not clearly stated.]]>https://forums.manning.com/posts/preList/37087/104267.pagehttps://forums.manning.com/posts/preList/37087/104267.page
GMTtrouble with full intall of PostGIS 2.1.3? What does

SELECT postgis_full_version();

show exactly. The other extensions like postgis_topology won't show unless you also did

( ST_XMax(geom) - ST_XMin(geom) )::integer)
FROM a1;
[/code]]]>https://forums.manning.com/posts/preList/36549/102056.pagehttps://forums.manning.com/posts/preList/36549/102056.page
GMTCardiffhttps://forums.manning.com/posts/preList/35687/100247.pagehttps://forums.manning.com/posts/preList/35687/100247.page
GMTchp 14.1 codehttps://forums.manning.com/posts/preList/35779/100224.pagehttps://forums.manning.com/posts/preList/35779/100224.page
GMTChapter 14 Paris data and code not available in chapter listhttps://forums.manning.com/posts/preList/34125/100223.pagehttps://forums.manning.com/posts/preList/34125/100223.page
GMTRepeated names of sections in Kindle (mobi) version For example the latest sentence in 1.4.1 is "... you set up in section 1.7.3" in PDF, but it is "... you set up in section _the section called "Installing PostGIS"_ ".
While having names of sections (here Installing PostGIS) is better than just numbers (1.7.3) it is slightly annoying to have "section the section" or "in chapter Chapter 14" and so on.

The last sentence in Section 3.3 misses link to the Appendix A - it is just the text, not the link to the chapter.

I also noticed some missing capitalisation in SQL in section 1.4.3, INSERT INTO ch01.restaurants (franchise, geom)
SELECT
franchise,
ST_Transform(ST_SetSRID(ST_Point(lon,lat),4326),2163) As geom
FROM ch01.restaurants_staging;

As - shouldn't it be AS?

Similarly Listing 1.6 - none of As is fully capitalised.

And some style fixes.
Section 4.1, PgAdmin III: Instead of "Via the pgAdmin interface, you can launch ..." I'd use "You can launch psql session via the pgAdmin interface ..."
4.4.1 contains "or you can download extracts of key areas such as those available at http://download.geofabrik.de/" - this sounds a bit strange, maybe "you can download extracts of key areas at various sites, for example at URL".

Listings at section 7.4.2, describing ST_histogram, miss descriptions, so the text is "Listing Listing 7.13 ``'' returned histogram for band 2 (...) As a result, the output in listing ??? returns 6 rows...".

And, the beginning of Chapter 13, about topologies: "I creat another polygon".

I am a newbie in the spatial world but I think pysal distance based weight calculation can be done in postgis using KNN along with ST_Distance and ST_Dwithin functions. Am i right in my assumption?]]>https://forums.manning.com/posts/preList/35233/98526.pagehttps://forums.manning.com/posts/preList/35233/98526.page
GMTSection 2.2.3 Invalid polygons "Fortunately these polygons are difficult to generate
in PostGIS and dont serve any purpose in real world modeling"

It's not clear the distinction between invalid and degenerate, for example the following is invalid but not degenerate and seems to go up into Postgres fine.

INSERT INTO ch02.my_geometries (name, my_polygons)
VALUES (
'InvalidGeo?',
ST_GeomFromText('POLYGON(
(-0.25 -1.25,-0.25 1.25,2.5 1.25,2.5 -1.25,-0.25 -1.25),
(2.55 0,1.25 1,1.25 -1,2.55 0),(1 -1,1 1,0 0,1 -1) )'--fIRST SET IS OUTER rING,2ND & 3RD ARE INNER RINGS. First inner ring is dodgy?.
)
);]]>https://forums.manning.com/posts/preList/34811/93089.pagehttps://forums.manning.com/posts/preList/34811/93089.page
GMTRe: shp2pgsql for Mac I found it.]]>https://forums.manning.com/posts/preList/34716/93086.pagehttps://forums.manning.com/posts/preList/34716/93086.page
GMTRe: Obtuse Softwares zigGIS plug-in (page 6)https://forums.manning.com/posts/preList/34334/93081.pagehttps://forums.manning.com/posts/preList/34334/93081.page
GMTTimestamped GPS waypoints For context, I'm working on a field data collection system where, in theory, users start a patrol, the device collects waypoints and users enter sightings, then users finish the patrol. In theory, we can use the start and finish patrol entries to select the waypoints belonging to a patrol. In practice, it's not rare that users forget to finish the patrol, so the device sits around collecting waypoints for 27 hours until it runs out of battery...

So, on importing the data, what I'd like to do is import the waypoints into a staging table along with their time stamps, and then ask questions (and ideally, get the answers in a visual/ mapping output format for examination...) like:
- When did the device leave/ arrive at the dock/parking lot/ village?
- When did the device lose/ regain GPS signal?
- When did the device start/ stop moving at an appreciable speed?

The first I could probably do by putting the timestamp into the M dimension, merging the waypoints into a linestring, clipping the linestring to polygons defined around the docks/parking lots of interest, and selecting the boundaries of the multilinestrings produced. But is there a better approach?

The second I'd need some way of examining the intervals between successive points and seeing when they exceed either a pre-determined gap length, or ideally, one generated by looking at the usual gap for that track (if the device is collecting points every 10 seconds, then a few minutes of gap would indicate a loss of signal; if it's collecting them every 5 minutes, it wouldn't...)

For the third, I'd need to calculate some kind of moving average speed over a number of adjacent points; I imagine there's enough error in individual points there'd always be a non-zero velocity, but if it's low enough we could consider them stopped...

Any thoughts on how to tackle especially the latter two questions?]]>https://forums.manning.com/posts/preList/34211/93080.pagehttps://forums.manning.com/posts/preList/34211/93080.page
GMTRe: QGIS version in table 5.1 Thanks for the input. It will be updated before next MEAP release. QGIS moves really fast :)]]>https://forums.manning.com/posts/preList/34156/93078.pagehttps://forums.manning.com/posts/preList/34156/93078.page
GMTRe: Creating Web Map Did you take a look at the source code in the download file.

There is an example of building a GeoJSON output in PostgreSQL with a function that you can directly overlay in Leaflet and OpenLayers. Our example was with Leaflet for overlay, but you can use the same for OpenLayers.

Which version of PostgreSQL and PostGIS are you using?
The first edition of the book -- http://www.postgis.us/chapter_11_edition_1 We do have an example of OpenLayers, PHP (using smarty). If you haven't already you can get a free copy of the 1st edition E-book if you purchased the 2nd Edition.]]>https://forums.manning.com/posts/preList/33843/93074.pagehttps://forums.manning.com/posts/preList/33843/93074.page
GMTHow interactive technology is transforming storytelling It is an intensive aerophilic crippled that has some strong anaerophilous tactics mixed into the halting play. If they miss, take out fun 2 degrees. That remembering, Ms. Quade avered, moderately sums up why she changed by reversal her comedic manoeuvres into fund-raisers. 5. Say the following: Wow! amatory handmade Valentine's Day trade projections and thoughts are designed for creating your dear or just a family fellow member happy.

according to a argument on their website, they direct things into their own workforces. I consider I better relocation where is fun she at? I ever chance subject to be a arduous one best diet plans to lose weight fast to understand. After the end of your Mauritius holidays at that place will be numerous experiences for you to divvy up with your friends and congenerics. I see, so by your account, Harold Potter was a absolutely average Englishman, without any tendency towards representing a Scotsman whatsoever?

Until recently your litttle lady but slept together introductory cotton fiber panty briefs for her underwear. Around 1% of the sun's mass is oxygen. This comprises Michelangelo's David, and besides his Prisoners, bare sculptures entraped evermore fun in their city blocks of marble. If he pushes another go up the shop, the doorways will spread out. Be fun nerveless to the driver. on that point is something about holidays that increments fun the appetite. It utilized to be so glad!

Every time someone betrays X-product or fares X-activity, mark it in colour on the map, etc. So at the detail the gentleman requires me What do you same to do for fun? So it's odd that a new study by Forrester boost your bust Cupertino fun is slipping a refer. Helicopter tours are the most popular of all and fun sell out often. In 1991, I gave a workshop for pupils, executives, instructors and profs at the New York Medical College, Valhalla, NY. in that respect are many different types of karaoke simple machines on the market today. Along the logical arguments of inducing invitees seem goofy is a fun eating competition. Some usual venues include the home of the maidservant of honor or, for fun something more than unparalleled, breezes can be only lovely.

3 Don't Drown Her in "Guy Stuff" Free St. Patrick's Day ActivitiesSt. chancing the right-hand residuary income opportunity in network commercialising is something anyone can do.

Pictorial memory is retained improve and is definitely more than worrying. He admits he was but lipsynching on the saxophone, not actually acting it. See if your directors will concord to have got work recoup assorted outcomes. If you could tempt 5 celebrated people to your party, Who would they be]]>https://forums.manning.com/posts/preList/33840/93073.pagehttps://forums.manning.com/posts/preList/33840/93073.page
GMTRe: Data for chapter 3 San Francisco broken linkhttp://www.postgis.us/chapter_03_edition_2]]>https://forums.manning.com/posts/preList/33826/93070.pagehttps://forums.manning.com/posts/preList/33826/93070.page
GMTQuery Update Postgis I need urgent help.
I wish I could make a recursive query to update:

UPDATE table
SET rast = ST_SetValue (rast, 1, x, y, 0)

where x and y are generated automatically.
es: generate_series (1,100) as x, generate_series (1,100) as y.
My problem is that in the many cases that I have tried, it only updates the first row, with x = 1 and y = 1.
help me.]]>https://forums.manning.com/posts/preList/33667/93068.pagehttps://forums.manning.com/posts/preList/33667/93068.page
GMTRe: nationalatlas.gov being decommissioned Thanks for the update. We'll make a note of it in book.]]>https://forums.manning.com/posts/preList/33654/93066.pagehttps://forums.manning.com/posts/preList/33654/93066.page
GMTRe: Installing the TIGER geocoder database (chapter 8)https://forums.manning.com/posts/preList/33513/93064.pagehttps://forums.manning.com/posts/preList/33513/93064.page
GMT2nd Errata on Quantum GIS/QGIS I would like to add that GVSIG is not "the only one of these products that touts a mobile edition".

Regards,
Tudor]]>https://forums.manning.com/posts/preList/33464/93063.pagehttps://forums.manning.com/posts/preList/33464/93063.page
GMTRe: Errata on Quantum GIS/QGIS Thanks for the notice. We'll be sure to update before final release.

Thanks,
Regina]]>https://forums.manning.com/posts/preList/33463/93061.pagehttps://forums.manning.com/posts/preList/33463/93061.page
GMTRe: ogr2ogr error Unfortunately we aren't allowed to put more than 72 characters per line so hard to show things that should be single liners.]]>https://forums.manning.com/posts/preList/33313/93059.pagehttps://forums.manning.com/posts/preList/33313/93059.page
GMTRe: Error inserting restaurant data from staging table IT seems that maybe you mistyped 2163 as 2136 when you were running listing 1.3 (that creates the ch01.restaurants table)]]>https://forums.manning.com/posts/preList/33043/93056.pagehttps://forums.manning.com/posts/preList/33043/93056.page
GMTRe: Listing 2.11 It's possible the user you are logging in as has its own search_path setting which would override the database search_path.

Can you check

SHOW search_path;

to see if topology is in it?]]>https://forums.manning.com/posts/preList/32558/93054.pagehttps://forums.manning.com/posts/preList/32558/93054.page
GMTRe: 2nd ed availability in ex-commie country Thanks,
Regina]]>https://forums.manning.com/posts/preList/32513/93051.pagehttps://forums.manning.com/posts/preList/32513/93051.page
GMTRe: Data for ch 11http://www.postgis.us/chapter_11_edition_2

We have to update the full download link, I think that might be slightly out of date.]]>https://forums.manning.com/posts/preList/32165/93049.pagehttps://forums.manning.com/posts/preList/32165/93049.page
GMTPersonal geodatabase size "The Personal GeoDatabase is nice in the sense that you can hold a number of layers in one file but is limited to 4GB in size."

This is unfortunately incorrect. Personal GeoDatabases are limited to 2GB in size (minus "the space needed for system objects.").]]>https://forums.manning.com/posts/preList/31978/93048.pagehttps://forums.manning.com/posts/preList/31978/93048.page
GMTRe: Why use "alas" in "Alas, were ready to write the query."https://forums.manning.com/posts/preList/31741/93047.pagehttps://forums.manning.com/posts/preList/31741/93047.page
GMTRephrase the load of the fast food example... "We know our projection to be NAD 83 Lon Lat so we indicate this by changing the SRID to 4269. Be careful here! We're simply telling the importer what the SRID is..."

A light rephrase to clarify that we are just *labeling*:

"We know our projection to be "NAD 83 Lon Lat" (1) so we indicate this by setting the SRID to 4269 (which happens to be the code for "NAD 83" (2)).

(1): http://en.wikipedia.org/wiki/North_American_Datum (2): Check it out by running SELECT srid, srtext FROM spatial_ref_sys WHERE srtext ILIKE '%NAD83%' and srid > 4000]]>https://forums.manning.com/posts/preList/31740/93044.pagehttps://forums.manning.com/posts/preList/31740/93044.page
GMTRe: Files for book not explicitly referencedhttps://forums.manning.com/posts/preList/31708/93041.pagehttps://forums.manning.com/posts/preList/31708/93041.page
GMTUnclear Instructions in §1.4.3 Importing Shapefile GUI FIgure 1.4 shows two screen caps, one of the main shp2pgsql-gui interface and one of the options screen. While the screen cap shows the editing of the SRID to 4269, two other things seem to be changed in a way that is not reflected in the text.

FIrst, The Table column appears to have been changed from the default of the shp filename (roadtrl020) to "roads", whereas the text instructs to rename to highways_staging which I believe is the intended name.

Also, in the options menu, it appears that the default check boxes have been altered so that "Create spatial index automatically after load" is no longer checked. The text makes no mention of this change.

The inconsistency of this passage keeps one from being able to follow just the image or just the text. In my opinion all the steps of the GUI process should be laid out step by step, possible in an ordered list.]]>https://forums.manning.com/posts/preList/31707/93040.pagehttps://forums.manning.com/posts/preList/31707/93040.page
GMTPage 123 - Loading data with "shp2pgsql" "/path/to/tl_2012_us_state" used in the the shp2pgsql is a path root, not a file or directory

For example, after unpacking tl_2012_us_state.zip one finds, as indicated by the "file(1)" program:

Here, the path root would be ""/path/to/waterways"]]>https://forums.manning.com/posts/preList/31587/93039.pagehttps://forums.manning.com/posts/preList/31587/93039.page
GMTSidebar on p. 90: Oblate --> Oblong "Spheroids are a subclass of ellipsoids where a = b. A spheroid where c (polar axis) > a (equatorial axis) is called an oblate spheroid."

It would be advantageous to indirectly indicate which "AS" values are relevant and which not. This may be done using "foo1", "foo2", if the significance of that metavariable is clear to the reader (this is not necessarily the case) or by using "anything1", "anything2"....:

IF (ST_Y(geomgeog))>0 THEN[b][/b]]]>https://forums.manning.com/posts/preList/31402/93036.pagehttps://forums.manning.com/posts/preList/31402/93036.page
GMTCH 1, listing 1.3 "idx_code_restaurants_geom ON ch01.restaurants USING gist(geom);"
on page 21 is repeated on page 24, causing an error.

MEAP pdf downloaded 6-22-2013]]>https://forums.manning.com/posts/preList/31216/93035.pagehttps://forums.manning.com/posts/preList/31216/93035.page
GMTChapter 1 Prior to create database command remind reader of syntax such as caps sensitive or not, need for semicolon to execute - or - prior to instructing reader to enter a command, refer reader to appendix where command syntax is provided.

Consider placing the listings for creation of database "postgis_in_action" at the beginning of section 1.4.2 so that it immediately precedes creating the schema "ch01".

Section 1.2.3 does not explicitly instruct creating the database "postgis_in_action".

MEAP downloaded 6-22-13]]>https://forums.manning.com/posts/preList/31213/93034.pagehttps://forums.manning.com/posts/preList/31213/93034.page
GMTRe: Small fixes in Chapter 1 We fixed the other small errors and brought up the issue with kindle to our editor. They are looking into that one to make sure its just a draft issue.

Should see changes in next MEAP release. We just fiinish first draft of chapter 10 so new MEAP release will hopefully be available in next week or so.]]>https://forums.manning.com/posts/preList/31044/93031.pagehttps://forums.manning.com/posts/preList/31044/93031.page
GMTRe: Installation options for MacOSX: no homebrew?https://forums.manning.com/posts/preList/30554/93029.pagehttps://forums.manning.com/posts/preList/30554/93029.page
GMTRe: Missing path separator in section 4.3.2https://forums.manning.com/posts/preList/30521/93027.pagehttps://forums.manning.com/posts/preList/30521/93027.page
GMTRe: Query for SRID in section 3.3.1 returns no rows In PostGIS 1.5, the proj4text for 4269 was:

+proj=longlat +ellps=GRS80 +datum=NAD83 +no_defs

and it was the only one that had datum=NAD83 in it.

In 2.0 as part of resourcing from epsg files, it seems this was updated to not have a datum and is now equivalent in meaning to the other 4 rows you are coming up with.

If you look at the others, you'll see they have exactly the same proj4text which is all PostGIS cares about. I'll ask if this was a mistake in resourcing that the datum was stripped or if it was intentional.

Thanks again for the catch. Much appreciated.]]>https://forums.manning.com/posts/preList/30509/93025.pagehttps://forums.manning.com/posts/preList/30509/93025.page
GMTRe: Broken link to US states datahttps://forums.manning.com/posts/preList/30508/93023.pagehttps://forums.manning.com/posts/preList/30508/93023.page
GMTRe: Dimensions of raster table in listing 2.10https://forums.manning.com/posts/preList/30504/93021.pagehttps://forums.manning.com/posts/preList/30504/93021.page
GMTRe: Duplicate bullet point in section 2.1.5https://forums.manning.com/posts/preList/30503/93019.pagehttps://forums.manning.com/posts/preList/30503/93019.page
GMTRe: Error in list 1.6 franchise_code does not exist Thanks]]>https://forums.manning.com/posts/preList/30502/93017.pagehttps://forums.manning.com/posts/preList/30502/93017.page
GMTRe: shp2pgsql-gui instructions The pgAdmin only install and the pgAdmin that comes with PostgreSQL are slightly different. For PostgreSQL pgAdmin this should point to the bin folder of your PostgreSQL install and you should have plugins.d folder in your /pgAdmin III of (install folder/pgAdmin III)

The plugins.d should have a file called postgis.shp2pgsql-gui.ini]]>https://forums.manning.com/posts/preList/30482/93013.pagehttps://forums.manning.com/posts/preList/30482/93013.page
GMTRe: explain ALTER TABLE details It would make sense to have on one line, except the Manning frameork doesn't allow lines longer than 70 characters for printing reasons, so a lot of stuff we would have like to include as one line, we just broke out rather than having annoying line continuation characters.]]>https://forums.manning.com/posts/preList/30481/93010.pagehttps://forums.manning.com/posts/preList/30481/93010.page
GMTRe: error on CREATE SCHEMA ch01; We thought about that, but decided to partition our book data by chapters. For backup and restore reasons, this translated nicely to using schema for that partitioning. Perhaps we should have explained that better (and we will) that the use of schemas is a logical container based on how you want to manage data (for backup, security, theme). To be honest, partitioning by chapter makes as much sense to me as any other kind of partitioning whether that be geographical (where gasp you have a different restaurants table for each geography), data theme, etc. It's all up to what makes the most sense for the data manager to see as a unit and to manage as a unit.

Others have suggested we should have started out with one grande example and then carried it thru the book building it up. I think if we had done that your suggestion would have fit better. Then again it suffers from the problem of having to read the book in sequence and we didn't want a book that you had to read in sequence since this book is geared for both novices and non-novices. I think the better solution would be to just write a different book more specifically geared for novices. rather than trying to satisfy all audiences with one book. We are thinking about that too.]]>https://forums.manning.com/posts/preList/30459/93007.pagehttps://forums.manning.com/posts/preList/30459/93007.page
GMTRe: Errata Thank you very much for the input. I think we got most of the chapter 1 changes in you have so should be in next release which should be in about a week. Hoping to get the other chapter changes in as well.

As mentioned for explaining the SQL we are planning to do much of that in the Appendix C and Appendix D and just put a refer to etc for explanation. the chapters are already too long and many database folks will be familiar with those so may get distracted if they just came to learn about PostGIS.

We probably need to make a couple more updates to those appendix especially D since PostgreSQL 9.3 added the new LATERAL join construct which is very handy for spatial queries. It's an ANSI-SQL construct (so technically should be in C), but I don't think any other database supports it with that name so we'll probably just demonstrate in D as a PostgreSQLism.

As far as repeating of glossary terms. That's a draft issue. It repeats whenever we tag. Issue will not exist in the production grade PDF/print book.]]>https://forums.manning.com/posts/preList/30458/93003.pagehttps://forums.manning.com/posts/preList/30458/93003.page
GMTRe: Font size in OpenJUMP Finally, there is a workaround of the problem. The issue appears when the locale
is set something different than en-US. So change the setting in Control Panel>Regional and Language Options>Advanced to English(United States) and the text with normal font size will be displayed.

Gyula]]>https://forums.manning.com/posts/preList/30364/93001.pagehttps://forums.manning.com/posts/preList/30364/93001.page
GMTRe: Another error in Ch 1 Thanks for update. I'll check next I have the chance. Which version of PostGIS are you running. I suspect the issue is because we changed the feed a bit since last time around]]>https://forums.manning.com/posts/preList/30279/92997.pagehttps://forums.manning.com/posts/preList/30279/92997.page
GMTA few errata in ch 1 Bottom of p14, 'vanacular' should be 'vernacular'
Bottom of p19, 'through fare' should be 'thoroughfare'
First word in 1.4.4 - 'Alas' injects some black humour, but I suspect it's probably meant to be 'At last'

SQL at bottom of p23 incorrect, if earlier instructions have been followed. I got it to work with a series of queries similar to this, one for each franchise:

Listing 1.6 incorrect, if earlier instructions have been followed. I got it to work as follows:
SELECT f.franchise
, COUNT(DISTINCT r.id) As total --
FROM ch01.restaurants As r
INNER JOIN ch01.lu_franchises As f ON r.franchise = f.id
INNER JOIN ch01.highways As h ON ST_DWithin(r.geom, h.geom, 1609) --
GROUP BY f.franchise
ORDER BY total DESC;

However the code downloads seems a more logical way to name fields than the system used in the pdf.

Also the results of this query at top of p27 seem incomplete - there shd also be results for Hardee (1077), Jack in the Box (509), Carl's Jr (224) and In-N-Out (44).

Hope this helps

Pat Maslen]]>https://forums.manning.com/posts/preList/30278/92996.pagehttps://forums.manning.com/posts/preList/30278/92996.page
GMTRe: Ch 1. Unable to locate restaurants.csv We'll be updating the code download in next MEAP. Unfrotuantely I think we accidentally left it out.

You can download from here:

http://www.postgis.us/chapter_01_edition_2]]>https://forums.manning.com/posts/preList/30077/92994.pagehttps://forums.manning.com/posts/preList/30077/92994.page
GMTRe: SQL syntax error on page 78 You shouldn't have to include topology. in the call. When you install topology it should automatically add the topology schema to your database search path.

Can you confirm it does and that you don't have a user specified search_path.
To confirm connect to your database and run the command

Do a:

show search_path;

You should see topology listed there.]]>https://forums.manning.com/posts/preList/30034/92992.pagehttps://forums.manning.com/posts/preList/30034/92992.page
GMTRe: Possible error in SQL instruction on page 26 Thanks for the correction. We've updated and should be available in next MEAP release.]]>https://forums.manning.com/posts/preList/30024/92990.pagehttps://forums.manning.com/posts/preList/30024/92990.page
GMTRe: Errata page 437 Which edition of the book are you reading? That looks like it's coming from Appendix C of the first edition and I don't think we've released the version of that on MEAP for edition 2 yet though we are planning to.

As far as errata. We are planning to put in corrections to the code as people find them. We can do the same for version 1 as well. Thought aht technically isn't an errata.

I think Manning keeps list of errata on the book page, but interestingly enough we haven't received any errata for Book 1. We'll certainly fix this issue in Appendix C of Edition 2 (and there will be more examples demonstrating newer features of PostgreSQL/PostGIS).]]>https://forums.manning.com/posts/preList/29968/92988.pagehttps://forums.manning.com/posts/preList/29968/92988.page
GMTRe: Errata Sect 1.4.4 Thanks]]>https://forums.manning.com/posts/preList/29933/92986.pagehttps://forums.manning.com/posts/preList/29933/92986.page
GMTRe: cosmetic fixes Thanks for the errata. We'll have fixed in next MEAP release. Hope you enjoy the book.]]>https://forums.manning.com/posts/preList/29902/92983.pagehttps://forums.manning.com/posts/preList/29902/92983.page
GMT